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.
There is some discussion going on in bpo-45155 about what the default value of
the `byteorder` argument should be for int.to_bytes() and int.from_bytes():
https://bugs.python.org/issue45155
I’ve created a short Discourse poll if you’d like to weigh in.
https://discuss.python.org/t/what-should-b
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 Sat, Sep 11, 2021 at 7:08 PM Gregory Szorc
wrote:
> Thanks for all the replies, everyone! I'll reply to a few comments
> individually. But I first wanted to address the common theme around
> zipimport.
>
> First, one idea that nobody mentioned (and came to me after reading the
> replies) was t
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
Thanks for the fix! This could have caused some serious issues, so glad we
were able to address it ahead of time.
On Mon, Sep 13, 2021 at 5:06 AM Victor Stinner wrote:
> Hi,
>
> A bug has been identified and *fixed* in the OAuth-based
> authentication code used on the Python bug tracker bugs.pyt
Hi,
A bug has been identified and *fixed* in the OAuth-based
authentication code used on the Python bug tracker bugs.python.org
(BPO) to log in with GitHub, Launchpad or Google. Under some
conditions, it was possible to be logged as another person account. We
are only aware of a single user affect
