Perhaps something in the release notes pointing to the branch would be good. Unfortunately there's probably at least a month of code reviews. Not to mention it has been discussed that the port only needs to support 2.6 as support is being dropped, so it'll get much simpler.
That being said, Django still needs the full py3 support module in case someone else's module straddles Django versions. -- Sent from my Palm Pixi On Dec 15, 2011 6:00 PM, Kiril Vladimirov <v.ki...@gmail.com> wrote: While I'm reading all topics, listed below I'm thinking... is it too early to announce *experimental* Python 3.2 support in Django 1.4? Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase Python 3 port - all Oracle tests (bar one) now pass on 2.7.2 and 3.2.2 with the same codebase May be something like a light bulb that should go over the head of all django users(as in web developers using django) and plugin maintainers about python 3 support could facilitate a future 2 to 3 migration. What do you think? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/nQT-3UYcO8IJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en. -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
