> I'd posit with fair confidence that Django 1.0 will come long, long > before Python 3000 reaches a non-alpha state.
Wow that's a strong statement... the "long long" seems a bit exagerated since if Python 3000 sticks to schedule it would release Beta in a month or so. Anyway I like strong statements, you might have insider info. I have looked on the web and I couldn't find any release date for v. 1.0. But I saw they postponed many times before deleting any date from their FAQ. But I believe u, I'll wait for 1.0 (not for Python 3000) and then I'll start, I have enough to do in the mean time :). Thanks! On 15 Mag, 16:41, "Quentin Gallet-Gilles" <[EMAIL PROTECTED]> wrote: > On Thu, May 15, 2008 at 5:16 PM, David Zhou <[EMAIL PROTECTED]> wrote: > > > 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] > > Django'd better hurry, because the first beta release of Python 3000 is due > next month ! And the final release is scheduled for September. > > However, that's just a start. Porting the libraries (batteries excluded, of > course) is the next big step and it is expected that we will have to wait > for 3.1 or 3.2 before the major libraries and frameworks are all ported. > > Anyway, I agree it's silly to wait for Python 3000. The 2.x release is not > that different and everything is done to make adjusting to Python 3000 as > seamless as possible. > > Quentin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
