[Python-Dev] backported Enum
Nick Coghlan
ncoghlan at gmail.com
Sun Jun 16 09:31:29 CEST 2013
More information about the Python-Dev mailing list
Sun Jun 16 09:31:29 CEST 2013
- Previous message: [Python-Dev] backported Enum
- Next message: [Python-Dev] backported Enum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16 June 2013 15:58, Donald Stufft <donald at stufft.io> wrote: > > On Jun 16, 2013, at 1:52 AM, Ben Finney <ben+python at benfinney.id.au> wrote: > > Donald Stufft <donald at stufft.io> writes: > > On Jun 15, 2013, at 10:45 PM, Ben Finney <ben+python at benfinney.id.au> wrote: > > Is there anything I can do to keep the ‘enum’ package online for > continuity but make it clear, to automated tools, that this is > end-of-life and obsoleted by another package? > > > Right now the best you can do is make a note of it. Pep 426 let's you > do what you want. > > > Thanks. What specifically in PEP 426 do you mean; how would I make a > note of “this package is end-of-life as is, please migrate to > ‘flufl.enum’ instead” using PEP 426 metadata? > > > http://www.python.org/dev/peps/pep-0426/#obsoleted-by > > Note PEP426 isn't completed and isn't implemented :) That specific bit is stable, though :) Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] backported Enum
- Next message: [Python-Dev] backported Enum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list