Michael Bayer wrote:
also i dont understand how sticking a __call__() on SessionContext would have any impact on its existing get/set/del operations.
It's totally unnecessary and it clutters the interface. Unnecessary methods/properties/etc. are confusing because they make people wonder "What's the difference?" or "Why are there two versions?" As strange as it may seem, it is harder to remember how to do something when there are many different possibilities. The main case where you'd see a class with multiple methods that do exactly the same thing is when the interface has changed and old (deprecated) versions are there for backward compatibility. Since this is a brand new class we should decide on the one obvious solution and keep it simple. If you don't think a property is the most obvious way, then let me know and we can discuss changing the interface to be more obvious. I've noticed that you tend to add lots of convenience features to do all sorts of things that you anticipate people will want to do, even when it would be trivial and/or obvious for the user to just do it in their own code. I think this hurts SQLAlchemy because the API is cluttered with lots of stuff that is not strictly necessary for what the library is doing. I know you're a Perl programmer too, so maybe that's where some of that style is coming from. If you're interested, I have lot's of comments like this on various parts of the SQLAlchemy API. ~ Daniel ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
