[Python-Dev] Process to remove a Python feature
Victor Stinner
vstinner at redhat.com
Fri May 4 18:18:59 EDT 2018
More information about the Python-Dev mailing list
Fri May 4 18:18:59 EDT 2018
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2018-05-04 23:59 GMT+02:00 Terry Reedy <tjreedy at udel.edu>: > Would it be possible (and sensible) to use the 2to3 machinery to produce > 36to37.py, etc., to do mechanical replacements when possible and flag other > things when necessary? I suggest you to watch Daniele Esposti's talk "Evolution or stagnation programming languages". He explains that Javascript is more successful than Python to introduce *language* evolutions thanks to transpiling (things like babel and polyfill): https://www.pycon.it/conference/talks/evolution-or-stagnation-programming-languages Victor
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list