Brad Clements wrote: > > so, maybe offer "close" methods on objects that hold references to other > resources... and have __del__ call those close methods, and make sure > that multiple close calls are ok.. I think thats the most reasonable > thing to do without going crazy, but still leaves open the opportunity > for explicit resource release when needed. > > I think this is a low priority issue.. maybe even just an advisory to > keep in my when developing new code. I don't think it's worth acting on > now to the detriment of more important work. > > thanks >
Ok, im glad youre cool with __del__() for cPython usage....I think its behavior is quite reliable sans circular references and was one of the things I liked about Python compared to Java. I think the issue is somewhat critical because this is the kind of thing that has an impact on the API, some of the internal constructs to the SQLEngine which I am in the middle of reworking, and is also something to keep in mind as we come up with new usage patterns...."dont get too comfortable with the automatic closing of resources". ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
