Thanks! I've written a longer response on the voting thread:
https://discuss.python.org/t/vote-to-promote-brandt-bucher/5135/10
Brandt
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-commi
Mariatta wrote:
> Will you be joining the core sprint next month?
I certainly hope to join! I'll register as soon as I can confirm my
availability.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python
Brett Cannon wrote:
> Our lesson from our "innocuous" addition of booleans makes me leery of
> anything that tweaks the API such that it isn't compatible in the same
> feature release.
Agreed. I'm not 100% sure of the context, but were a few typing module
additions a while back that made CI a b
I saw a (seemingly) related issue with the bots not creating 3.8 and 3.9
backports for this PR:
https://github.com/python/cpython/pull/22736
No failure message or anything. Just saying they’re “working to backport” the
changes and never doing it.
___
Thanks Mariatta!
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.p
As I understand it, we’re the next PEP “in line” for a ruling. I imagine it
could happen soon (but I know the SC has been quite busy).
If anybody is interested in getting this (huge) feature into the hands of alpha
testers as quickly as possible once they *do* make their decision, the
implement
Paul Moore wrote:
> In case it's not clear, I'd *like* a chat-style community, but I'd prefer it
> to be a little more "social". We have plenty of "work-related" communication
> channels, but IMO we don't really have anywhere that's the online equivalent
> of the workplace "hanging out around th
I’ve had some pretty weird interactions with that bot too:
https://github.com/python/cpython/pull/27397
I’ve found in general that these messages are pretty noisy, and not very
helpful. For example, backporting a PR to another branch usually results in me
receiving around a dozen different emai
Is there a possible middle ground here? Rather than a required PR check (or a
full buildbot run), maybe we could just add a new “magic” label that runs a
single refleak job using the GitHub actions runners.
___
python-committers mailing list -- python-c
