On Nov 16, 2008, at 2:27 PM, greno wrote:
> > Looks like final release of Python 3.0 will happen in December 2008 so > one month. I was hoping to see projects like SQLAlchemy being almost > ready for 3.0 but it seems people were waiting for final release. I > guess if you have the code running under 2.6 and you have all the Py3k > warnings resolved then you can run the 2to3 tool on it and it should > convert it to 3 syntax. there's little or no DBAPIs available. There won't be widespread use before that happens in any case. If current DBAPIs don't provide for Py3K and new contenders step in, then that complicates things even further as our dialects are somewhat specific to their current DBAPI. While we do have a branch which will resolve this, its still in progress and is associated with the 0.6 SQLA series. Also I'm pretty sure 2to3 is not going to be nearly enough. I'm hoping we'll be able to automate the 2to3 process entirely on our side but it will take some engineering beyond what 2to3 provides. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
