On Thu, May 15, 2008 at 10:57 PM, mardenet <[EMAIL PROTECTED]> wrote: > > Hello, > I am new to Python and Django, I am a ASP.NET C# programmer actually > tired of following Microsoft's unnatural and crazy page model that > tries to hide the page from you as much as possible.. seriously how > did they came up with that?! > > I am very interested in Python and Django for a future project but I > am noticing this is a period of big changes in this community. Python > 3000 and Django 1.0 will really be a major change. > I am not afraid of using Alpha versions, and I want to use latest > technologies and my mind rejects any forced changes in the code due to > new releases. If I do something I don't want to touch it again. > So I want to start straight with Python 3000. > > Would this be compatible with Djanga? If not when do you expect it to > be compatible? > I prefer waiting than recoding, so I wanted an idea on timelines... > any thoughts?
This came up a little while ago (around the time of PyCon 2008), so if you search the archives, you can find a lot more discussion on the topic. However, the short version: * There are currently no formal plans to support Python 3000. Efforts are currently focussed on Django 1.0. * There isn't a huge need to be on the cutting edge here - we still maintain Python 2.3 support because it is used by a few deployment environments that are in common usage. It will be some time before Python3000 is in common usage everywhere. * Exploratory work has been done on porting Django to Python 3000 - initial reports are that there isn't a huge amount of work to be done on our code base. * 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. * If you follow the official Python guidelines for handling the 2->3000 transition, you shouldn't need to do much recoding of your own code. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
