[Python-Dev] PEP 413: Faster evolution of the Python Standard Library (original) (raw)
Eric V. Smith eric at trueblade.com
Sat Feb 25 17:24:47 CET 2012
- Previous message: [Python-Dev] PEP 413: Faster evolution of the Python Standard Library
- Next message: [Python-Dev] PEP 413: Faster evolution of the Python Standard Library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2/25/2012 11:18 AM, Zachary Ware wrote:
Anyhow; I have to say I like Nick's idea put forth in PEP 413, but I agree that the extra versioning info could get pretty awkward. Therefore, why not just make stdlib upgrades part of the regular maintenance releases? As long as there is absolutely no change in usage from (for example) 3.3.0 to 3.3.1, what's wrong with adding new (stdlib) features in 3.3.1?
The problem is that you can't say "my code works on Python 3.3". You now have to specify the micro version number as well: "my code works on Python 3.3.1+". We've made this mistake before; I can't see it happening again.
Eric.
- Previous message: [Python-Dev] PEP 413: Faster evolution of the Python Standard Library
- Next message: [Python-Dev] PEP 413: Faster evolution of the Python Standard Library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]