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. 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.
