The two main issues with this are DBAPI availability, and code migration. I have been waiting for Py3K to be generally stable before even attempting to migrate the code, its going to be a huge job. We're still settling into Python 2.6 compatibility to even get on board there.
sqlite3 seems to be present in Py3K so that would allow some testing to occur. I dont see anything for psycopg2 nor anything for MySQLdb (and I'm assuming that explicit conversions would be needed for those). So as of yet the impetus to push for 3K compatibility doesn't seem to be there yet. Of course we'd be thrilled for volunteers to take on this task and begin identifying issues. We've already seen issues such as Py3K's inconvenient treatment of __hash__() may make it fairly complicated. On Nov 16, 2008, at 1:37 PM, greno wrote: > > Can SQLAlchemy be used in a Python 3.0 environment? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
