> At last year's PyCon, it sounded like the move to SQLAlchemy and > Genshi were "weeks" away...
That's largely my fault for not recognizing how intertwined turbogears.config and cherrypy 2.2's config system were -- and how incompatible that was with cherrypy 3. All of this lead us down a path which wasn't very successful. At the same time we had some unforseen changes in project leadership, and and had to readjust. We also had a change in direction after the pygears sprint ended up creating a workable prototype of tg2 in far less time than tg 1.1 had taken up to that point. We've also been hit by some significant backwards incompatible changes in SQLAlchemy for the 0.4 branch. The new API's are great, and I definitely think this is a huge step forward for SQLAlchemy, but we had quite a bit of work to do to to keep up. So, it's been more work than I thought. But I have lots of faith in Florent and the team that 1.1 is really coming soon. But we'll serve no wine before it's time, and open source projects are very difficult to predict accurately. --Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
