On May 15, 2008, at 10:57 AM, mardenet wrote: > 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.
They will be big changes, but don't really align in terms of timeline. > 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. Even if you coded in Python 3000, it's not like Django doesn't sometimes introduce backwards incompatible changes. Plus, I highly doubt any serious effort will be made to make sure Django works on Python 3000 until after Django 1.0 and (likely) until after Python 3000 exits alpha state. > 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? I'd posit with fair confidence that Django 1.0 will come long, long before Python 3000 reaches a non-alpha state. If you want to use Django for something, I'd start now -- or with 1.0. Waiting for Python 3000 is a bit silly. --- David Zhou [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
