[Python-Dev] Deleting with setting C API functions
Victor Stinner
victor.stinner at gmail.com
Wed Dec 2 09:46:37 EST 2015
More information about the Python-Dev mailing list
Wed Dec 2 09:46:37 EST 2015
- Previous message (by thread): [Python-Dev] Deleting with setting C API functions
- Next message (by thread): [Python-Dev] Deleting with setting C API functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2015-12-02 15:40 GMT+01:00 Random832 <random832 at fastmail.com>: > Are there plans for a Python 4? No. Don't. Don't schedule any "removal" or *any* kind of "break backward compatibility" anymore, or you will definetly kill the Python community. It will probably take 10 years or more to convert *all* Python 2 code around the world to Python 3. I don't want to have to redo the same thing again. Never ever again. To be clear: removing functions is fine, but if and only if you have a smooth transition plan. Sorry, it's unclear to me what is a "smooth transition plan". IMHO the deprecation warnings which are current quiet by default is not a good idea. Everybody ignore them, and then complain when the function is really removed. Maybe I should write an informal PEP to explain my idea. Victor
- Previous message (by thread): [Python-Dev] Deleting with setting C API functions
- Next message (by thread): [Python-Dev] Deleting with setting C API functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list