Django sets out plans for Python 3 migration - Update
The Django developers have published preliminary plans on how they will be migrating their Python-based web application framework to Python 3. A number of users have cited the lack of a Python-3-supporting Django release as the reason for not migrating to the new version of Python. Working with the Python team, they have opted for a staged migration, using Python 2.6 as a stepping stone.
The developers plan to first deprecate the use of older 2.x versions of Python, until the minimum required version of Python is 2.6 for Django. Python 2.6 is the cornerstone of the transition since it was designed to be a bridge to Python 3, as many major features of the newer Python having been backported to it and it includes tools to assist with migrating code to Python 3.
The upcoming release of Django 1.4 will drop support for Python 2.4, and Django 1.5 will then drop support for Python 2.5 later on. Django 1.5 will also add experimental support for Python 3.x, most likely version 3.3, which is set to be released around the same time. Django 1.5 will therefore be the start of the process of porting the Django code base to Python 3.
Further details on the long-awaited transition are not yet available, with the team still working out finer points such as the exact level of support that Python 3 incompatibilities will receive in Django, but the general direction is clear. In the words of the developers: "Python 3 is the future of the Python language, and in support of that the Django project is and will remain committed to achieving Python 3 compatibility."
Update: The Django developers have released Django 1.4 RC2 – the developers hope this will be "the final pre-release package before Django 1.4". Downloads and release notes are available for the pre-release package, which is aimed at testers.
- Python 3.0 Arrives, a The H report on the introduction of Python 3.0.