durusmail: quixote-users: Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
2005-03-17
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
2005-03-18
Why class 'Session' has no method get_user() ?
"Template" components. Was: Why class 'Session' has no method get_user()?
2005-03-19
"Template" components. Was: Why class 'Session' has no method get_user()?
2005-03-19
Why class 'Session' has no method get_user() ?
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
2005-03-17
Why class 'Session' has no method get_user() ?
David Binger
2005-03-17
On Mar 17, 2005, at 1:46 PM, Graham Fawcett wrote:
>
> 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.

I guess I'm the crab today. ;|

I like to know that attribute assignment will not raise an exception,
and that the name *will* be a key in the __dict__ after the assignment,
and that the assigned value will not be wrapped or mangled.


reply