On 10/24/06, iGL <[EMAIL PROTECTED]> wrote: > Of course, all this is pretty rudimental and less helpful. However, > IMHO, adopting novelties of Py2.5 seems really promising. > Is this particluar direction of SA extensions worthy? Any criticism is > welcome.
My first reaction was that Python 2.5 isn't easily available everywhere yet -- many distros will continue to ship 2.4 for a while, for example. So we don't want to make SQLAlchemy depend on the user having 2.5. Then I realized that your suggestion would still eb possible: just wrap the contextmanager stuff in a try/except ImportError, and the special create_table() and other features just don't exist if the user has 2.4 or below. So yeah, it's worth playing with. I especially like the potential for "with transaction() as t:" or "with transaction(my_engine) as t:" (or passing any Connectable to the transaction() contextmanager...). "with pool.get_connection() as conn:" might be cool too. -- Robin Munn [EMAIL PROTECTED] GPG key 0xD6497014 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
