> * The bigger problem you will encounter isn't Django - it's the chain > of support libraries. At the very least, you will need Python3000 > versions of mod_python and a database backend. To the best of my > knowledge, these tools aren't available in Python3000 versions - until > they are, there isn't much point having a Python3000 version of > Django.
As was already pointed out in that discussion, mod_wsgi in subversion trunk already supports Python 3.0. Thus there already is a Python 3.0 capable solution for Apache hosting. Personally I can't see mod_python getting ported to Python 3.0 as the effort would just be too much and anything using the mod_python specific APIs directly, rather than through a constrained interface such as WSGI, would also require a lot of rework because it is such a broad API. In other words, although Django may use only a subset of mod_python API, the work in porting all the parts of mod_python it doesn't use and the impact those changes will have on mod_python specific frameworks, would most likely deter anyone doing it. Add on top of this the large list of outstanding issues and problems with mod_python, which really would want to be addressed at the same time, and you would have quite a big project that isn't going to get done very quickly, if at all. The Django folks would be better off focusing on making Django a well behaved WSGI citizen, moving away from use of global settings and instead use a model which would allow multiple Django instances to operate within the same process, based on per request WSGI configuration parameters, and thus cut down on memory usage through sharing of common code modules. They should also address problems with WSGI SCRIPT_NAME configuration being ignored and look any multithreading issues to give more certainty that Django will work on the range of WSGI hosting solutions available. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
