On Thu, 17 Mar 2005 12:53:14 -0500, David Binger
 wrote:
>
> Wait a minute.  It is reasonable to thing that code accessing sessions,
> say to list them all, might want to access the user (in a way that could
> be specialized if necessary, by a subclass).  quixote.get_user() doesn't
> do that.
>
> And while properties are helpful in cases where you have no alternative,
> they seem to me to be gratuitous alternative syntax for method calls.

I'm -0 on the specific issue; but I'd rather have gratuitous code in
the framework than extra keystrokes in my application code ;-). Adding
    user = property(get_user, set_user)
might make everyone happy.

Gentle-two-cents-ly, yours,
-- Graham