On Wed, Sep 14, 2011 at 8:42 PM, Jannis Leidel <lei...@gmail.com> wrote:
> > > Anybody knows somebody who started a django/py3 port already? We should > unify our efforts. > > As I said earlier in this thread, there is now a Python 3 branch in the > Django SVN. > Thank you! Really good to see that. > > > If core team doesn't like the py3 idea, we should start with a patch > which follows always the latest devel version. I strongly anticipate a > project fork (see what happened with the plone & blue bream). > > The core team likes the idea, there is no fork required. > Thank you! Really good to see that. > > > 2to3 (3to2), etc are good start for an initial port, but I think they > aren't enough to do this on day-to-day base. Their conversion algo isn't > enough, some handwork is needed. > > Could you be a bit more specific about what the algorithm can't do? From > what I saw in Martin von Löwis' patch (which is now in the Python 3 branch) > we haven't hit any problem with 2to3. That said, it's of course a long way > to go. > As I remember, it maked errors in the unicode handling of some *lazy* decorators in the django core. It isn't a wonder, because the functionality of these decorators contain a sophisticated functionality for the generalized unicode / ascii handling which in py3 is not needed. I think, the good fix is trivial for the core team and possibly it is done already in the official py3 branch (if not, I feel some urge to do this :-) ) bye, MaXX -- 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.
