On 2/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Let's stop going down this path. This isn't a thread about whether to > switch to SQLAlchemy. If you want to work on that, there is a branch > already created and a maintainer appointed for that branch. I've got > nothing against it, but it's not an area I'm working on at the moment.
Agreed. Having SQLAlchemy as an option is something we might have for 1.0, but I highly doubt it'll be done in time given the work that needs to be done in that branch. Switching Django to SQLAlchemy is something we cannot do right now because we have stated that the Django database-access API will not break backwards-compatibility before 1.0, and switching to SQLAlchemy would require us to break that compatibility in major ways. And if you want Django/SQLAlchemy integration, the thing to do is get in touch with us about contributing code to the SQLAlchemy branch. I know we have a lot of people out there who say they want this feature, and the only way it's going to happen is if some motivated folks write the code :) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
