[Python-Dev] Re: Enum -- last call for comments on 3.10 changes

2021-06-30 Thread Nick Coghlan
On Tue, 29 Jun 2021, 12:45 am Ethan Furman, wrote: > On 6/28/21 6:54 AM, Nick Coghlan wrote: > > > * Enum repr() changing back to the historical behaviour, unless you opt > in to the > > new behaviour with the global enum decorator: definite +1 here > > Question for Nick: this behavior is cur

[Python-Dev] Re: Enum -- last call for comments on 3.10 changes

2021-06-28 Thread Jelle Zijlstra
El lun, 28 jun 2021 a las 1:00, Ethan Furman () escribió: > I have spoken with Pablo (3.10 RM), and he agrees that a change to Enum > str() in 3.10 and another in 3.11 is less than > ideal, so this new thread is to collect comments about Enum and it's str() > and repr() and whether the changes tak

[Python-Dev] Re: Enum -- last call for comments on 3.10 changes

2021-06-28 Thread Ethan Furman
On 6/28/21 6:54 AM, Nick Coghlan wrote: > * Enum repr() changing back to the historical behaviour, unless you opt in to the > new behaviour with the global enum decorator: definite +1 here Question for Nick: this behavior is currently in place for stdlib enumerations, and has been since beta

[Python-Dev] Re: Enum -- last call for comments on 3.10 changes

2021-06-28 Thread Nick Coghlan
On Mon, 28 Jun 2021, 11:54 pm Nick Coghlan, wrote: > So my vote would be to revert both the repr() and str() changes on IntEnum > (et al) for 3.10, and then switch to the new str() approach for those > classes in 3.11. > Sorry, I missed including the requested rationale: * if the str() change

[Python-Dev] Re: Enum -- last call for comments on 3.10 changes

2021-06-28 Thread Nick Coghlan
On Mon, 28 Jun 2021, 6:02 pm Ethan Furman, wrote: > I have spoken with Pablo (3.10 RM), and he agrees that a change to Enum > str() in 3.10 and another in 3.11 is less than > ideal, so this new thread is to collect comments about Enum and it's str() > and repr() and whether the changes take > eff