[Python-Dev] Re: Enum and the Standard Library

2020-09-18 Thread Guido van Rossum
On Fri, Sep 18, 2020 at 6:19 PM Ethan Furman wrote: > On 9/18/20 3:12 PM, Guido van Rossum wrote: > > On 9/18/20 2:44 PM, Ethan Furman wrote: > > >> I'm looking for arguments relating to: > >> > >> - should _convert_ make the default __repr__ be > >> module_name.member_name? > > > > I ac

[Python-Dev] Re: Enum and the Standard Library

2020-09-18 Thread Ethan Furman
On 9/18/20 3:12 PM, Guido van Rossum wrote: > On 9/18/20 2:44 PM, Ethan Furman wrote: >> I'm looking for arguments relating to: >> >> - should _convert_ make the default __repr__ be >> module_name.member_name? > > I actually like the status quo for regular enums, when repr() shows > the type, n

[Python-Dev] Re: Enum and the Standard Library

2020-09-18 Thread Guido van Rossum
Okay, let me take a shot at this. I actually like the status quo for regular enums, when repr() shows the type, name and value, and str() shows "classname.flagname", so I'd stick to that for converted flags. Even though this violates the rule of thumb that repr() should look like a valid expressio

[Python-Dev] Enum and the Standard Library

2020-09-18 Thread Ethan Furman
As you may have noticed, Enums are starting to pop up all over the stdlib [1]. To facilitate transforming existing module constants to IntEnums there is `IntEnum._convert_`. In Issue36548 [2] Serhiy modified the __repr__ of RegexFlag: >>> import re >>> re.I re.IGNORECASE I think for

[Python-Dev] Summary of Python tracker Issues

2020-09-18 Thread Python tracker
ACTIVITY SUMMARY (2020-09-11 - 2020-09-18) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7675 (-22) closed 45870 (+67) total 53545 (+45) Open issues wi

[Python-Dev] Re: The Python documentation is now compatible with Sphinx 3.2 and newer

2020-09-18 Thread Guido van Rossum
Thanks Victor! This is a great improvement. On Fri, Sep 18, 2020 at 8:50 AM Victor Stinner wrote: > Hi, > > The Python 3.8, 3.9 and 3.10 documentation can now be built with > Sphinx 3.2+, and Sphinx 2 is still supported. Sphinx 3.0 and 3.1 are > not supported. > > On our continuous integration (

[Python-Dev] The Python documentation is now compatible with Sphinx 3.2 and newer

2020-09-18 Thread Victor Stinner
Hi, The Python 3.8, 3.9 and 3.10 documentation can now be built with Sphinx 3.2+, and Sphinx 2 is still supported. Sphinx 3.0 and 3.1 are not supported. On our continuous integration (CI), the Python 3.10 documentation is now built with Sphinx 3 (version 3.2.1), whereas the Python 3.8 and Python