0.1 used to call __init__, yes. there are many disadvantages to calling __init__ during a load operation, namely that state operations within __init__ can conflict with the state loaded from the database (and we had user issues to that effect), and also it requires that __init__ has only optional keyword arguments (which was a requirement in 0.1). if anything, the current behavior of calling __new__ is much less enforcing of a particular programming style, since theres no limitation on the structure of __init__. not to mention that you can override it anyway.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
