[Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement? (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Mon Sep 30 11:01:45 CEST 2013
- Previous message: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?
- Next message: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 25.09.13 23:33, schrieb Donald Stufft:
An early draft of this did not have the backport to 2.7 and when I showed that version around to get feedback people were less enthusiastic about it and generally viewed it as "nice but worthless to me for N years".
I'm leaning towards the people that oppose addition of this feature to older Python releases. In particular, the objection that the new PEP is worthless for a long time to come, is in itself not really relevant:
It is always the case that features proposed by a PEP reach users only years after they have been implemented.
What users want isn't rationale in and of itself but I think it's an important data point, especially given how long 2.7.LASTEVER is going to be relevant to end users.
Well, I really really don't like this idea. 2.7 should not get new features; users who want new features need to switch to 3.x.
Regards, Martin
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJJPfkACgkQavBT8H2dyNL9SQCfceoTqIeCiwq0GMdaWeUSn/nV 6E4AmwRfmjFcSXjdmGLQbewVqxxYwRit =tLof -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?
- Next message: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]