Thirded. On Fri, Dec 16, 2011 at 5:55 PM, Ian Clelland <clell...@gmail.com> wrote:
> 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. As I understand it, "untested and isn't used by any part of core" suggests we shouldn't include it in 1.4 at all. Developers that are willing and wanting to test py3 compatibility can pull from the appropriate branch and start working on updating their own code. FWIW, as soon as the issues mentioned by Vinay in this thread get corrected, we can commit the py3 changes to trunk and work from there. Not modifying 1.4 does *not* mean that trunk will not see any python 3 code soon, i.e. we don't have to wait until 1.5 beta. Released versions should be stable and tested, and 1.4 can only be called stable if we don't include py3 support. Cheers, AT -- 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.
