On Fri, Dec 16, 2011 at 8:59 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk>wrote:
> > On Dec 16, 12:45 am, Ian Kelly <ian.g.ke...@gmail.com> wrote: > > > The problem with merging it and labeling the support as "experimental" > > is that the changes are of such a fundamental nature that they could > > easily break things in 2.x, not just in Python 3. > > Agreed, it's too risky to merge in 1.4 this late in the day. As well > as passing the full suite, it would need to be tested in more real- > world scenarios (including with third-party apps) to be sure there > were no regressions in 2.x. > Seconded; although, like Joseph above, I have also thought that it would be helpful for module writers to have access to django.utils.py3, to be able to start writing code that will work on both Django 1.4 and 1.5+. I don't know if it's completely warranted; it would mean putting a piece of code into core that is untested, and isn't used by any part of core, but it would be handy to have. For my pymysql backend, I've just included my own minimal version of the file, just declaring the definitions that are needed for that piece, but I'n not sure how I'll ever be able to remove that, and still keep support for Django 1.4. It's looking right now like I'll have to release a Django 1.5 version of the backend in order to use django.utils.py3, or else just maintain my copy independently forever. > On the bright side, it does allow time for simplifying to allow > "except X as e:", and removal of u() and b() from the port, as well as > more extensive testing on both 2.x and 3.x. > > Regards, > > Vinay Sajip > > -- > 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. > > -- Regards, Ian Clelland <clell...@gmail.com> -- 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.
