[Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again? (original) (raw)
Antoine Pitrou antoine at python.org
Mon Aug 18 19:49:06 CEST 2014
- Previous message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
- Next message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 18/08/2014 13:22, Mark Dickinson a écrit :
[Moderately off-topic]
On Sun, Aug 17, 2014 at 3:39 AM, Steven D'Aprano <steve at pearwood.info_ _<mailto:steve at pearwood.info>> wrote: I used to refer to Python 4000 as the hypothetical compatibility break version. Now I refer to Python 5000.
I personally think it should be Python 5000000, or Py5M. When we come to create the mercurial branch, that should of course, following tradition, be called p5ym.
I would suggest "NaV", for "not-a-version". It would compare greater than all other version numbers (in the spirit of Numpy's "not-a-time", slightly tweaked).
Regards
Antoine.
- Previous message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
- Next message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]