On 9/13/2021 8:12 PM, Ethan Furman wrote:
On 9/13/21 9:03 AM, Steve Dower wrote:
> You *are* allowed to put some (brief) details in the abstract. No
need to avoid spoilers ;)
>
> As it stands, "it is time" on its own is a really bad reason to
change anything. So you're
> preemptively mak
On 9/13/21 9:55 AM, Jelle Zijlstra wrote:
> This table doesn't render properly in
https://www.python.org/dev/peps/pep-0663/#specification.
> - There are some extra blank lines
> - Many cells are blank
> - There are two "user mixed" rows and it's not clear how those relate to the mention of
"thr
On 9/13/21 9:03 AM, Steve Dower wrote:
> You *are* allowed to put some (brief) details in the abstract. No need to
avoid spoilers ;)
>
> As it stands, "it is time" on its own is a really bad reason to change
anything. So you're
> preemptively making it sound like the PEP has no solid backing.
El vie, 10 sept 2021 a las 22:56, Ethan Furman ()
escribió:
>
>
> Specification
> =
>
> There a three broad categories of enum usage:
>
> - standard: Enum or Flag
>a new enum class is created, and the members are used as
> ``class.member_name``
>
> - drop-in replacement: IntEnum,
On 9/11/2021 6:53 AM, Ethan Furman wrote:
Abstract
Now that we have a few years experience with Enum usage it is time to
update
the ``repr()``, ``str()``, and ``format()`` of the various enumerations
by their
intended purpose.
You *are* allowed to put some (brief) details in the ab
> On 11 Sep 2021, at 06:57, Ethan Furman wrote:
>
> If the previous output needs to be maintained, for example to ensure
> compatibily between different Python versions, software projects will need to
> create their own enum base class with the appropriate methods overridden.
Perhaps you could
