[Python-Dev] Keyword meanings [was: Accept just PEP-0426]
Terry Reedy
tjreedy at udel.edu
Thu Dec 6 05:44:01 CET 2012
More information about the Python-Dev mailing list
Thu Dec 6 05:44:01 CET 2012
- Previous message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Next message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/5/2012 10:12 PM, Daniel Holth wrote: > Makes sense. How about calling it Replacement. 0 or 1? > > Replacement (optional) > :::::::::::::::::::::: > > Indicates that this project is no longer being developed. The named > project provides a drop-in replacement. > > A version declaration may be supplied and must follow the rules described > in `Version Specifiers`_. > > The most common use of this field will be in case a project name changes. > > Examples:: > > Name: BadName > Replacement: AcceptableName > > Replacement: AcceptableName (>=4.0.0) I like it. 'Replacement' is broader in meaning, more neutral, and less awkward than 'Obsoleted-by'. And I agree that A users have much more need to know about B the vice-versa. It is much the same situation with Py 2 and Py 3 (although the latter is *not* a drop-in replacement). -- Terry Jan Reedy
- Previous message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Next message: [Python-Dev] Keyword meanings [was: Accept just PEP-0426]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list