On Wed, Dec 15, 2010 at 12:45 AM, sirex <[email protected]> wrote: > On 15 Gruo, 01:51, Russell Keith-Magee <[email protected]> > wrote: >> but we're not planning to actively support Python 3 any time soon. > > Why?
Dependencies, for one. Psycopg2 and MySQLdb do not officially support Python 3 yet, so the only backends available out of the box would be oracle and sqlite3. Also PIL has not been ported, so ImageFields would be unusable. More importantly, the core devs don't want to have to support Python 2.4/2.5 and Python 3 simultaneously. Hence the suggested plan to begin officially supporting Python 3 once support for 2.5 has been deprecated. > Maybe there should be two versions of Django, one that supports Python > 3 and other that supports Python 2? No. -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
