[python-committers] Re: Commits are no longer noted in bro issues

On Thu, May 27, 2021 at 9:50 PM Guido van Rossum wrote: > > Did you check your junk or spam mail folders? The email address from which > bpo is sending email is not super trusted by the spam filters used by large > email providers like GMail and Outlook. Unfortunately, this is not just the

[python-committers] Re: Commits are no longer noted in bro issues

On Thu, May 27, 2021 at 8:46 PM Irit Katriel via python-committers wrote: > > > I'm not getting anything at all from bpo for about a week now. Maybe it had > enough of me. That has nothing to do with the BPO issue we have been talking about. The infra team is the best place to report email

[python-committers] Re: workflow enhancement: a `mark bug as fixed` PR tag [feature request]

On Sun, Oct 11, 2020 at 10:14 PM Gregory P. Smith wrote: > > We've got the automerge tag on GH, it+bot make it awesome. There's one more > thing I'd like to see that could help with bug hygiene: A tag to close the > associated bug as "fixed" after the merge happens. You can already do that by

[python-committers] Re: MSDN Subscription renewals

On Mon, Aug 17, 2020 at 10:59 AM Victor Stinner wrote: > > FYI this MSDN subscription allowed me to debug tons of Windows > specific issues and to enhance Windows support. It's really very > helpful, at least to me :-) Thanks Microsoft! Same here! I was able to fix many issues and implement some

[python-committers] Re: Notification of a three-month ban from Python core development

On Wed, Jul 22, 2020 at 10:31 PM Python Steering Council wrote: > > The following message was sent to a core developer. This message was > thoughtfully and respectfully sent by the Steering Council as a serious > reminder that the privilege to serve as a core developer comes with the >

Re: [python-committers] discussion fragmentation

On Sun, May 19, 2019 at 2:41 PM Stefan Behnel wrote: > > Paul Moore schrieb am 15.05.19 um 17:18: > > > multiple fragmented forums for discussion. It > > feels a lot harder these days to keep track of all the > > discussions/decisions going on. > > +1 True, two years ago I was able to follow

Re: [python-committers] Steering Council Update for April 2019

On Fri, Apr 26, 2019 at 9:50 PM Barry Warsaw wrote: > It would be very helpful if you could add these comments to the PR. Sure, I just left a comment there. > And as a fan of Roundup and its critical importance to the Python development > process, I want to personally thank you for all your

Re: [python-committers] Steering Council Update for April 2019

On Fri, Apr 26, 2019 at 11:37 PM Brett Cannon wrote: > Because that repo is private I will say that the last comment on that issue > was exactly a month ago from someone at GitHub saying that they are looking > into this feature request. Thank you, I forgot those links are private. I'll also

Re: [python-committers] Steering Council Update for April 2019

On Fri, Apr 26, 2019 at 5:55 PM Guido van Rossum wrote: > - **Issue tracker:** We've discussed PEP 581, "Using GitHub Issues for > CPython" by Mariatta Wijaya. We're in favor of this move, and feel > that the transition should be professionally planned and executed. > In collaboration with

Re: [python-committers] Could we focus our discourse, mail list on Python related issues?

On Sun, Apr 7, 2019 at 3:19 PM Xiang Zhang wrote: > https://discuss.python.org/t/can-we-do-something-for-996-programmers-in-china/1119/11 Hi Xiang, Perhaps I'm missing some context here, but Guido's first post in the thread you've linked isn't about politics (nor a discussion about comparing

Re: [python-committers] python-committers is dead, long live discuss.python.org

On Wed, Oct 3, 2018 at 1:06 PM Chris Jerdonek wrote: > Hi Łukasz, I tried signing up three days ago, but it doesn't look like I've > been approved yet (e.g. I'm not listed in the members list). I notice some > other people have been approved during this time based on the group count. I > tried

Re: [python-committers] python-committers is dead, long live discuss.python.org

On Sat, Sep 29, 2018 at 1:03 AM Victor Stinner wrote: > Oh, I just saw that Berker sent a message: > "Membership Request for @committers" > https://discuss.python.org/t/membership-request-for-committers/27/2 > > I don't see this message in any category. Is it a private message? If I understood

Re: [python-committers] How to retry backport?

On Sun, Aug 12, 2018 at 4:22 PM, Eric V. Smith wrote: > https://github.com/python/cpython/pull/8745 > > This failed (I think travis, but can't tell now). I thought I could close it > and re-open it to get it to retry, but apparently not. When I closed it, the > backport branch was deleted. At

Re: [python-committers] Transfer of power

On Thu, Jul 12, 2018 at 8:41 PM, Eric Snow wrote: > Thank you for putting so much time, effort, and care into both the > language and its community! We cannot thank you enough. +1 > In the short term we could appoint a *temporary* triumvirate to fill > in as BDFL (with the intent to re-assess

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

On Thu, Jun 14, 2018 at 11:46 AM, Victor Stinner wrote: > 2018-06-14 0:26 GMT+02:00 Berker Peksağ : >> I don't care about total number of commits to be honest. It's not so >> hard to get 50 PRs merged into master in a month or so. > > Wait, what? No developer got more t

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

On Wed, Jun 13, 2018 at 10:38 PM, Serhiy Storchaka wrote: > I think Pablo will be good core developer and agree with the description > given by Victor. But it seems that he still needs to learn something about > what changes are good for Python. I agree with Serhiy. Count me -1 for now. I don't

Re: [python-committers] number of active core devs

On Sun, Jun 3, 2018 at 11:27 AM, Antoine Pitrou wrote: > That said, it is true that core development activity continues to > shrink, at least according to this particular metric: > https://github.com/python/cpython/graphs/contributors I think the pre-GitHub stats includes merge commits too:

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

On Wed, May 2, 2018 at 12:49 PM, Victor Stinner wrote: > Hi, > > I would like to start a poll on Chris Angelico's PEP 572 "Assignment > Expressions", restricted to Python core developers, to prepare the > talk at the Language Summit: > >

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

On Thu, Sep 21, 2017 at 12:27 AM, Victor Stinner wrote: > Hi, > > Before the GitHub era, in the old "Mercurial era", the unwritten rule > was to not merge a patch written by a developer who has the commit > bit, to not "steal" his/her work. The old workflow (patches

Re: [python-committers] PyCharm open source license

On Sat, Sep 2, 2017 at 3:37 AM, Senthil Kumaran wrote: > If you are going to use for CPython development, then reach out to Vinay > Sajip. I have four available licences for CPython development too. --Berker ___ python-committers

Re: [python-committers] Please edit the commit message when merge a PR

On Mon, Jul 10, 2017 at 4:14 PM, Serhiy Storchaka wrote: > When a PR is consistent on several commits, the final commit message > composed by GitHub contains messages of all these commits: "fix typo", > "address yyy comments", "revert zzz". If the initial commit message >

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

On Sat, Apr 1, 2017 at 12:40 AM, Brett Cannon wrote: > In the (long) discussion of > https://github.com/python/core-workflow/issues/6, Wes Turner began to do his > usual posting of lists. People pointed out he was stepping out of line by > being somewhat off-topic and seemingly

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

On Mon, Mar 13, 2017 at 12:11 AM, Brett Cannon wrote: > > > On Sun, 12 Mar 2017 at 06:33 M.-A. Lemburg wrote: >> >> On 10.03.2017 23:13, Brett Cannon wrote: >> > Fifth, anything I missed? :) >> >> My main nit after the move is that messages to the checkin list

Re: [python-committers] No more notifications of commits (merged PR) on bpo?

On Mon, Feb 27, 2017 at 4:45 PM, Victor Stinner wrote: > Hi, > > My PR was merged, but I don't see any notification on bpo: > https://github.com/python/cpython/pull/253 > http://bugs.python.org/issue27840 > > A few weeks ago, we got two notifications per commit (hg,

Re: [python-committers] Disable Codecov on GitHub pull requests?

On Mon, Feb 13, 2017 at 6:25 PM, Victor Stinner wrote: > 2017-02-13 16:04 GMT+01:00 Donald Stufft : >> I’ve also never see the random -0.01% >> coverage of code in another project, and my guess is that there is some sort >> of non-determinism in the

Re: [python-committers] The new github PR messages

On Sun, Feb 12, 2017 at 3:25 PM, Serhiy Storchaka wrote: > неділя, 12 лютого 2017 р. 11:46:08 EET Paul Moore написано: >> ... and just a further note that I'm finding the new github PR >> messages much easier to follow than the old python-checkins traffic. >> That's

Re: [python-committers] Proposed new core developer -- Mariatta Wijaya

On Thu, Jan 26, 2017 at 11:04 AM, Raymond Hettinger wrote: > Hello all, > > Mariatta Wijaya has been working hard to become a Python core developer. At > this point she has worked with several of us and I think she has had two > dozen or more accepted patches. > >

Re: [python-committers] Promote Xiang Zhang as a core developer

On Tue, Nov 15, 2016 at 11:17 AM, Victor Stinner <victor.stin...@gmail.com> wrote: > Hi, > > 2016-11-15 1:10 GMT+01:00 Berker Peksağ <berker.pek...@gmail.com>: >> Xiang tends to fix things that are not broken, > > This sentence sounds strange. What do you mean? :

Re: [python-committers] Promote Xiang Zhang as a core developer

On Mon, Nov 14, 2016 at 3:09 PM, Victor Stinner wrote: > Hi, > > Last months, I noticed that Xiang Zhang is very active on the bug > tracker and propose many enhancements and bug fixes. He contributes to > Python code, but also to the C code (a rare skill nowadays).

Re: [python-committers] commit privileges for INADA Naoki

On Sun, Sep 25, 2016 at 8:52 PM, Raymond Hettinger wrote: > >> On Sep 25, 2016, at 8:38 AM, Yury Selivanov wrote: >> >> I want to propose to give commit privileges to INADA Naoki. He's the guy >> behind compact dict implementation for

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

On Mon, Jun 6, 2016 at 10:00 PM, R. David Murray wrote: > We've talked about having a 'triage capable' symbol to go with our > core dev and contributer agreement symbols, but no one has implemented > it yet. I'm a complete Roundup newbie but I have attached a patch at

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman wrote: > Question: I noticed a couple issues on b.p.o that were being closed by > contributors (not core-devs, not their own issues). > > Should non-core-devs be closing issues that do not belong to them? Yes, but they should

Re: [python-committers] Guidance on merging(?)

On Sun, May 8, 2016 at 4:18 PM, Steven D'Aprano wrote: > Hi, > > My hg skills are still fairly basic, and I'm looking for somebody who > can mentor me (or at least point me in the right direction) with respect > to making the same change across multiple versions of Python. >

Re: [python-committers] The state of our copies of libffi (was: Redoing the C API?)

On Thu, Mar 3, 2016 at 10:58 PM, Zachary Ware wrote: > We actually have four separate copies of libffi: > > Modules/_ctypes/libffi: This is a mostly-vanilla copy of libffi-3.1 > (released 19May2014), lightly patched according to > Modules/_ctypes/libffi.diff. This

Re: [python-committers] Davin Potts as a new committer

On Sat, Mar 5, 2016 at 8:44 AM, Gregory P. Smith wrote: > > On Fri, Mar 4, 2016 at 10:07 PM Raymond Hettinger > wrote: >> >> >> > On Mar 4, 2016, at 4:07 PM, Brett Cannon wrote: >> > >> > I guess I'm just worried about the health

Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 1 will be tagged tomorrow

On Sat, May 23, 2015 at 12:53 AM, Chris Barker chris.bar...@noaa.gov wrote: On Fri, May 22, 2015 at 2:33 PM, Larry Hastings la...@hastings.org wrote: On 05/22/2015 02:29 PM, Chris Barker wrote: Is it too late to get the isclose() code (PEP 485) into 3.5? ... Hopefully you can find a

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

On Sat, Mar 14, 2015 at 10:23 PM, Brett Cannon bcan...@gmail.com wrote: Paul has been participating on python-dev for quite a while, he is a committer on pip, and (co-)author on 5 PEPs. At this point I think it would be prudent for Paul to have commit privileges if for any other reason than to