Yes, indeed immutability is one thing PyRecord is missing. I have had needed it at least twice since I created the library. I’m hoping to work on it after the Christmas break.

I too dislike having to repeat the name of the record type. I spent a long time researching and prototyping alternatives, but came to the conclusion that namedtuple’s approach (repeating the type name) was the best compromise.

One of the options I considered was very similar to what you’re proposing, but I found two problems with it: It wouldn’t be correct to imply that PyRecord has a class named “Point” and it would not be good for static code analysis (inc. code completion in IDEs).

I also considered exposing a second way to create record types, but then I remembered one point in the Zen of Python: “There should be one– and preferably only one –obvious way to do it”.

I like `collections.namedtuple` a lot for their immutability and `_replace` method =) Very often redefine `__new__` in them to make some fields optional, with default value.

Regarding passing name of the record type explicitly, have you considered to make a sugar for that ?

For instance, `pyrecord.new.Point(“x”, “y”)` or `pyrecord.type.Point`.
Also you can check `sh` library they make a wrapper for the module so you can do something like this


from pyrecord import PointDef
 
Point = PointDef('x', 'y')
# or
Point = pyrecord.Point('x', 'y')


I tried this approach.


class RecordNameProxy:
def __getattr__(self, name):
return lambda *args, **kwargs: Record.create_type(name, *args, **kwargs)
 
type = RecordNameProxy()


In the EUROMICRO paper I mentioned above, the authors point out that late binding is also possible in CBSE and cite COM as an example. They cover other differences which, in my opinion, are not as significant as binding time.

Looked from another perspective, services in SOSE are black boxes for their clients, while CBSE allows components to be used as white, gray or black boxes. I’d imagine this distinction can be useful in areas like critical systems development, where redundancy and diversity strategies like NVP are used and SOSE could potentially be deemed the only acceptable paradigm.

I have developed an application with TG2. And now I need users to
authenticate with PAM. How I can do? I have been testing “repoze” with
SQLAlchemy and I like it but use it with PAM. Any ideas?

Thanks

It’s hosted at Linode, which, by the way, I would highly recommend to anyone.

HTH.

– Gustavo.

Asking you a question about hosting, as read your past post about webfaction.com
Your website is pretty fast do you still host it with webfaction.com?

if not where?

Kudos.

I found your demo and plugin for LDAP with repoze. I’ve downloaded the demo and am running.

I can easily get to http://localhost:8080/, but when I go to http://localhost:8080/about, I get an WebError Traceback.

⇝ HTTPUnauthorized: 401 Unauthorized This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.

Any tips?