4 ms·
Yes, but 1.5 claimed only "experimental support", adding that they thought it probably would work all right but didn't want to recommend Python 3 for production
by SiVal 13y ago
Yes, but 1.5 claimed only "experimental support", adding that they thought it probably would work all right but didn't want to recommend Python 3 for production yet. The unqualified "yes, we now consider it ready and can recommend Python 3 for production," was promised for Django 1.6. They probably have achieved that goal, but the fact that there is no mention of it anywhere in a document that mentions so many other things suggests that "for the first time, we can now recommend the use of Python 3 for production" isn't something they think their target market cares about as much as the several dozen other "issues" they DID mention.
- jacobian 13y agoAgain, see my comment up-thread. Your assumptions are rather incorrect.
- coldtea 13y agoYes, but his complaint is rather valid. Those that prepared the release notes made a mistake in not mentioning Python 3 related improvements / status.
- JshWright 13y agojacobian acknowledged that oversight hours ago... >Fact is, we just forgot to mention it. Django's working so well on Py3 that it kinda seems like no big deal any more, so we forgot to mention it in the release notes. I'll fix that once I get a chance.
- jacobian 13y agoYup, we made a mistake. You could help by submitting a patch to fix it, or you could just choose to be a jerk and give some random person shit for making a mistake. Your choice.
- huxley 13y agoWell, this is just the alpha release of the Django 1.6 so production recommendations (other than "don't use this for production yet") are probably a bit premature. If you are very concerned about this, you should bring it up on the django-dev list: https://groups.google.com/forum/?fromgroups#!forum/django-developers https://groups.google.com/forum/?fromgroups#!forum/django-de...
- sdfjkl 13y agoIt works fine. I'm working on my 2nd Django project using Python 3.3. The only missing component is South, and that isn't part of Django (although it'd be nice if it were).
- JshWright 13y agoIt will be.. http://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django http://www.kickstarter.com/projects/andrewgodwin/schema-migr...
- natrius 13y agoSouth supports Python 3 as of a couple of days ago. http://www.aeracode.org/2013/5/22/south-08-migrations-and-djangocon/ http://www.aeracode.org/2013/5/22/south-08-migrations-and-dj...