[Python-Dev] Minor change to Enum -- should it go into 3.5.2?
Nick Coghlan
ncoghlan at gmail.com
Mon May 9 06:21:06 EDT 2016
More information about the Python-Dev mailing list
Mon May 9 06:21:06 EDT 2016
- Previous message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Next message (by thread): [Python-Dev] devinabox has moved to GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9 May 2016 at 12:39, Ethan Furman <ethan at stoneleaf.us> wrote: > On 05/08/2016 07:15 PM, Nick Coghlan wrote: >> Needing to use a PyPI alternative to a stdlib module for increased >> cross-version consistency is a pretty common experience these days, so >> I think that's OK - end users can choose for themselves between the >> stability of the stdlib version and the reduced update latency of the >> PyPI version. > > Are you saying I shouldn't bother updating the 3.6 Enum to ignore _order_? I don't have an opinion on the change itself (although keeping PyPI and 3.6-to-be aligned seems reasonable), just that it's OK to suggest folks use a backport module even on earlier 3.x versions if they want the behaviour of the latest (or even the next upcoming) stdlib release, rather than the baseline behaviour of their current runtime. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Next message (by thread): [Python-Dev] devinabox has moved to GitHub
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list