On Thu, Mar 8, 2012 at 8:48 AM, Carl Meyer <c...@oddbird.net> wrote:
> Hi Ian,
>
> On 03/08/2012 08:40 AM, Ian Clelland wrote:
> > On Thursday, March 8, 2012, Aymeric Augustin
> > <aymeric.augus...@polytechnique.org
> > <mailto: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"
>
> Let's please not rehash this discussion here, it was already beaten to
> death on the python-dev mailing list.
I have no doubt that it was; I'm afraid I haven't been following that list
very closely recently.
(And you're right, it's way-OT for django-dev)
> >> 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.
>
> Note that the current version of Vinay's port (since it was updated to
> account for dropping Python 2.5 support post-1.4) does not use u() and
> b() functions, it uses "from __future__ import unicode_literals". This
> means that the only place string wrappers are needed is in the few
> places where a "native string" is needed ("str" on both Python 2 and 3).
> Vinay posted numbers to python-dev indicating that there is no
> measurable performance overhead in the current port.
That's great -- That was from the post that came in over the holidays; I'll
definitely have to get back on testing that.
--
Regards,
Ian Clelland
<clell...@gmail.com>
--
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.
