Hi Armin. I have worked with Django's ORM without the rest of Django. There is no reason you cannot use it this way, particularly with magic removal without the need to bundle as a separate product. I had also once thought of a simple repackaging prior magic removal. Fact is, you can just import what you want. That is the great thing about python. SQLObject and SQLAlchemy are excellent ORMs. I disagree with the SQLAlchemy being hard to learn and it strives to be a comprehensive solution and is maturing nicely. Personally, I believe it is really great that there are choices between some very excellent open source initiatives.
Regards, David Armin Ronacher wrote: > The django ORM is the best out there. The only problem is that it's > only working from inside django. > > There is a ticket for that: http://code.djangoproject.com/ticket/1321 > and a discussion here: > http://groups.google.com/group/django-developers/browse_thread/thread/5b590b5487e500c1/c0f0d30cec89b107?q=orm&rnum=5#c0f0d30cec89b107 > > Currently there are only two usable ORMs out there. SQLObject which > isn't pep8 compatible and isn't so nice to work with as the django one > and SQLAlchemy which is very complicated. > > For my current non django project i would like to use the django > magic-removed ORM because it's great to use. The only problem is that > using it require a complete django installation which isn't that good. > > So... Are there any plans to completly unbudle the ORM from django? > > > Regards, > Armin > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
