Hi Gerhard, First of all, my apologies to folks for not keeping you all more in touch with what's going on here at PyCon. It's been a great conference thus far, and we've got quite a crew together for the sprint.
I want to clarify what's going on here at PyCon and what the deal is with the SQLAlchemy stuff that Jeff has committed... Regarding SQLAlchemy: the officially supported ORM remains SQLObject. Mike Bayer doesn't believe that SQLAlchemy is fully ready for prime time, but for a number of people it has already proven to be quite useful and to handle a number of problems that SQLObject does not handle gracefully. For that reason, TurboGears has experimental support for SQLAlchemy for people who are running into issues and want to give SQLAlchemy a try. I have no intention of doing pluggable ORMs, and if SQLAlchemy matures fully and appears to be the best-of-breed choice down the line, there will be an easy migration path for people with existing TurboGears apps. As for the things we're doing at PyCon: we've got three tracks going right now: Kid, Docudo and experimentation with Paste/WSGI/RhubarbTart. The things we're working on are the kinds of things that really benefit from being in the same room together. The Kid and Docudo work will hopefully bear visible results very soon. The WSGI experimentation we're doing is not likely to land very soon. I can say for certain that we're getting a lot more traction with our experiments by being together here than we would working independently... so, it's the right time for us to work on it from that standpoint, but it's not the right time for it to roll into the trunk. So, rest assured: 0.9/1.0 is not going to look significantly different than it does now. And, we're definitely keeping an eye on backwards compatibility as we do our work. As soon as there's something cool to show off from here, I'll let you all know! Kevin p.s. I've done a screencast of my "Effective Ajax with TurboGears" talk. I'll try to get that online sometime soon. The internet access here hasn't been the best, which is part of the reason that I haven't been doing much emailing/blogging. On 2/27/06, Gerhard Häring <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Lately I'm seeing checkins with comments like > > - - Added SQLAlchemy support > - - Added RhubarbTart? to install_requires > > Ok, the RhubarbTart thing is going on in the pycon2006 branch. > > But I'm concerned that TurboGears will be a construction site for quite > some time unless a feature freeze of some sort is pronounced to get to > 0.9 and 1.0 in the next months. > > And I thought that was the plan here. > > It's not that I dislike those things, but IMO RhubarbTart (or CherryPy3) > and SQLAlchemy (or SQLObject2, or whatever will be the best ORM *then*) > should be targets for TurboGears 2.0, not 1.0. > > There's always a next major release where new shiny things can be added :-) > > Cheers, > > - -- Gerhard > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFEA5S/dIO4ozGCH14RAmTaAKDAheqLC6RrKwC3NnuRtRmvkh9A4gCgsrHM > Dkp2H0WRP25+3NIBre3e4OI= > =mhom > -----END PGP SIGNATURE----- > > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
