Python 3

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barry Warsaw wrote:
> On Jun 23, 2010, at 09:47 AM, Robert Collins wrote:
> 
>> I've done a couple of trivial patches moving in the direction of being
>> able to play with Python 3 and bzr.
> 
> \o/
> 
> (quoting out of order...)
> 
>> If the consensus from this thread is that this is ok, I'll update
>> HACKING docs appropriately.
> 
> HACKING.txt doesn't describe the minimum Python version for which
> compatibility must be maintained.  Perhaps it should?  Maybe it's described in
> a different document?  It does *imply* in a few places that Python 2.4 is the
> minimum version.  Understandable of course, but darn.
> 
>> which on 2 is a no-op, and on 3 reencodes using latin-1 (so everything
>> works). Or we could split out separate files to import on 2 and 3, but
>> I think the extra seek would make it a wash perf wise.
> 
> Or split it out for Python 2.4/2.6+ compatibility?  At least you can write
> idioms for the latter that 2to3 can more easily transform.  E.g...

So we discussed moving to even 2.5 a while back, and basically Redhat's
latest Enterprise versus (RHEL5) is supporting python2.4 until 2014 or so...

http://www.redhat.com/docs/manuals/enterprise/
and
http://www.redhat.com/security/updates/errata/

And RHEL6 isn't even out yet (and will move to python2.6, IIRC).

Down at the bottom it shows that RHEL5 is in primary support until March
2011, and secondary/tertiary support until 2014. And if you track it
through, RHEL5 only has 2.4 available.

Being tied to 2.4 for at least 1 more year, if not 4 more years, is
really going to hurt switching to python3. As having 2.4+3 compatibility
is just hard.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwhP3wACgkQJdeBCYSNAAOOLQCfRO/X277LcXP9c6tAaU575l5y
taUAn0T1SFBJV87wMIQ6L3b9RBpX42fG
=gAB4
-----END PGP SIGNATURE-----