Back in March in the thread: http://groups.google.com/group/django-developers/browse_frm/thread/d0922f1d56b09a4c
Martin v. Löwis indicated he had made an attempt at getting 2to3 to work on Django to see how it would work under Python 3.0. From that various bits of code were identified in Django which could be changed to make the 2to3 process work more cleanly. My question is, was any of that acted upon and Django tweaked to make it more friendly to use of 2to3, or are we still at square one as far as being able to move forward on getting Django working on Python 3.0? Also, was the converted code from what Martin did even captured anywhere so that people could look/play with it? My reason for asking is that now that patches are available for Python 3.0 (albeit not in Python subversion repository yet), that fix problems which were stopping mod_wsgi working entirely properly under Python 3.0, it would be nice to have access to a sizeable Python web application to try on top of mod_wsgi with Python 3.0 to make sure it is doing the correct thing. It works fine with basic WSGI applications, but until one tries a more sizeable application one will not know for sure. Part of what needs to be done is validate that the proposed changes to WSGI specification for Python 3.0 are even reasonable or need more work. At the moment, Django is the only large framework I know of where any decent attempt has been made to get it to work with Python 3.0. Am sure that some here would also like to have crowing rights on being able to say that Django is first large Python framework to Python 3.0. :-) Graham --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
