[python-committers] Re: Requiring PEPs to add/remove modules in the stdlib (and dropping the concept of "provisional")

Sgtm Sent from my comm On Mar 22, 2022, at 21:31, Gregory P. Smith wrote:  On Tue, Mar 22, 2022 at 4:36 PM Barry Warsaw mailto:ba...@python.org>> wrote: PEP 2 will have to be “un-superseded”, and presumably the devguide (which PEP 2 points to) will also need to be updated. we discussed tha

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

I use a mobile device to store TOTP tokens (one time use passcodes), but as I also wish to use my workstation device to generate these tokens, I’ve historically used a tool called oathtool to generate these one time tokens (from a stored secret), but due to

[python-committers] Re: core-dev chat

For CPython, I’ve been present on IRC and Zulip and Slack and Discord (and would prefer them in the reverse of that order). I’ve used Gitter for CherryPy and Setuptools and Xonsh, but found the interface kinda meh compared to Slack and Discord. Would be delighted if there was a preferred platfo

[python-committers] Re: CI tests are broken

One of the reasons I might be tempted to merge a pull request before the tests is completed is because there’s no mechanism to merge a pull request after the tests have completed (when there’s no reviewer). I imagine it’s allowed because there still is the case where tests can fail for some rea

[python-committers] Re: Cannot release 3.9.0a4

The Fedora failures in shutil and zipfile are "no space left on device". Seems like an environment/infrastructure issue. The failures in the Windows build also seem to implicate importlib (though with an obscure error). I looked into those and they don't appear to relate to anything I've worked

[python-committers] Re: [RELEASE] Python 3.8.1rc1 is now available for testing

I think I missed the announcement of the cutoff date for 3.8.1; I was hoping to get some bug fixes in for importlib.metadata. These aren’t crucial bugfixes, but it would be nice not to have them linger for months. Would you consider including these,

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

+1 On 2 May, 2018, at 10:49, Victor Stinner mailto:vstin...@redhat.com>> wrote: * +1: you like the PEP * -1: you dislike the PEP * 0: you are not sure if you like it or not, or you have no opinon * don't reply to this poll :-) ___ python-committers ma

Re: [python-committers] IPv6 issues on *.python.org

It’s working for me. https://gist.github.com/51689c789a21edc1f9f9cf32fa17431f On 16 Nov, 2017, at 09:07, Antoine Pitrou mailto:anto...@python.org>> wrote: Hello, I'm having IPv6 issues on *.python.org. Is anyone having the same issues or is it just me? Who should I repor

Re: [python-committers] MSDN Subscriptions — First timers, renewals

Brian, Jason R. Coombs jar...@jaraco.com 2301 Champlain St NW Apt 305 Washington, DC 20009-8703 It seems my subscription did lapse in August. Thanks for the help on this. > On 27 Sep, 2017, at 14:52, Brian Curtin wrote: > > Hey everyone, > > If you've been waiting on a

Re: [python-committers] Proposing Carol Willing to become a core developer

I was impressed with Carol’s leadership at HackIllinois +1 > On 23 May, 2017, at 14:15, Brett Cannon wrote: > > As usual, if you support/object to this idea, please say so. :) > ___ > python-committers mailing list > python-committers@python.org > ht

Re: [python-committers] Can we delete https://hg.python.org/coding/cpython/?

Seems that way. It doesn’t have any change sets not in the canonical repo. $ hg incoming https://hg.python.org/coding/cpython comparing with https://hg.python.org/coding/cpython searching for changes no changes found > On 19 Dec, 2016, at 17:23, Brett Cannon wrote: > > It's erroneously labeled

Re: [python-committers] "Gratuitous"? incompatibilities in the "fix only" releases

For reference, a similar bug fix also introduced incompatibilities with the Chishop service: http://bugs.python.org/issue23899 On Jul 29, 2015, at 12:06, Jesus Cea mailto:j...@jcea.es>> wrote: Yesterday I upgraded one of my computer to 2.7.10 and a program working for years failed. The problem

Re: [python-committers] Do people prefer pushing feature repos or one massive patch?

I'm in the other camp. The way I see it, a squash of history or massive patch file loses history. It loses details about the thought process of the implementer. It masks mistakes and obscures motivations. It also masks decisions made in the merge operation, further hiding potential problems. O

Re: [python-committers] Proposing Paul Moore for commit privileges

+1 ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] I would suggest not pushing or pulling from the repo

The other option is you could 'close' the unwanted head and create a new head at the point before the unwanted merge. > -Original Message- > From: python-committers [mailto:python-committers- > bounces+jaraco=jaraco@python.org] On Behalf Of Benjamin Peterson > Sent: Monday, 15 July, 20