[Python-Dev] Minor change to Enum -- should it go into 3.5.2? (original) (raw)
Ethan Furman ethan at stoneleaf.us
Sun May 8 18:43:38 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] Minor change to Enum -- should it go into 3.5.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/08/2016 03:29 PM, Guido van Rossum wrote:
If enum were provisional it would be okay, but since it isn't, I think this change can't go into 3.5.2. Think if this: could any code that works in 3.5.1 be broken by the change?
No, but with the change code that works in 3.5.2 could break in 3.5.1 or 3.5.0.
It's a 2/3 compatibility issue with enum34 and aenum which support order, and Python3.4+ which does not. The work-around is to use order instead (or use enum34 or aenum instead ;) .
Either way, it's only similarity to a bug is I should have named it order in the beginning, and put the compatibility shim into the stdlib version at the same time.
--
Ethan
- Previous message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Next message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]