On Thursday, March 8, 2012, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> PEP 414 was accepted a few days ago. It's designed to make it easier to
support 2.6, 2.7, 3.3+ on the same codebase.

(finishes reading)
Ugh. I'm starting to expect "PEP 499: In a last-ditch effort to encourage
developers to adopt Python 3, it is declared that Python 3.9 will be
exactly identical, in syntax and semantics, to Python 2.6.7"

> I hope we'll take advantage of this new feature in Django; however, that
means a large update (if not a reboot) of the py3k branch.

Sarcasm aside, the only thing that this PEP does is force us to consider
the minimum "starting version" of Python 3 that we want to support. If we
declare that Django 1.5 will run on Python 3.2+, then we can ignore this
PEP, and continue to use the u() and b() functions in the py3k branch,
until 3.2 support is one day deprecated.

On the other hand, if we can say that Django 1.5 will only support Python
3.3+, then there will never be a version of Django that needs to run on
3.2, and we can remove those functions from the py3k branch. Not really a
reboot, just one transformation that can now be removed. (probably giving
us a few % speed improvement)

I don't think we should base the decision on this PEP, though. More
important factors are probably the release schedule for 3.3 (August?) and
how that meshes with the 1.5 development cycle, as well as vendor support
for, and availability of, Python 3.3. Right now, there are a lot of people
with access to long-term vendor-supported Python 3 environments, but nobody
has 3.3. If we say that you can't upgrade to Python 3 until you can get a
full 3.3 environment, how will that affect the usefulness of support in
Django 1.5?

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to