[Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)

Tres Seaver tseaver at palladion.com
Tue Apr 15 17:46:56 CEST 2014


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

On 04/15/2014 11:34 AM, Skip Montanaro wrote:
> I find it hard to believe that freezing the stdlib is going to lower
> the barrier enough for the Mercurial folks, if, in fact, import
> slowness is their main reason for not moving to 3.x.

My understanding of what Matt said at the language summit is that the
need to support really old versions of Python 2.x (back to 2.4) is a big
part of the holdup ("straddling" is *much* more painful without
constraining to
Python2 >= 2.6).

As I heard it, the real reason for the inertia is that the Python3 port
is a lot of effort / pain for zero perceived gain outside of "because it
is the Right Thing(TM)."  After my porting experience, I can sympathize
with that sensibility, and my stuff gets an advantage (frameworks /
libraries marketing to Python3 devs) that Hg doesn't (most users don't
really care which Python is used to drive the standalone tool).


Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNNVHAACgkQ+gerLs4ltQ4lpwCeJTYvfBBlE3cS+eq+kA4/zEi3
R+8AnRy4HYLRZ4DHhHDop/8A86MJt5Ei
=fORL
-----END PGP SIGNATURE-----



More information about the Python-Dev mailing list