Re: [python-committers] Github reviews are cannibalizing BPO

On 5/2/17 10:07 AM, R. David Murray wrote: On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" wrote: On 02.05.2017 04:25, Nick Coghlan wrote: On 2 May 2017 at 08:32, Christian Heimes wrote: This brings me to my questions 1) Should we try to move discussion back to BPO or are we fine with h

Re: [python-committers] Github reviews are cannibalizing BPO

On 5/2/17 2:13 PM, Guido van Rossum wrote: I'm not necessarily disagreeing, I'm just skeptical that we can stop this tide. New contributors are familiar with GitHub and GitHub only, and for them, BPO looks and feels like a legacy system. And honestly, for smaller projects, I've found GitHub a ver

Re: [python-committers] [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On 11/1/2017 5:47 PM, Ned Deily wrote: Happy belated Halloween to those who celebrate it; I hope it wasn't too scary! Also possibly scary: we have just a little over 12 weeks remaining until Python 3.7's feature code cutoff, 2018-01-29. Those 12 weeks include a number of traditional holidays

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

+1, without reservation. He was an immense help to me on PEP 557. -- Eric. > On Dec 5, 2017, at 8:00 PM, Guido van Rossum wrote: > > I'd like to propose Ivan Levkivskyi as a new core committer. He's > (re-)written most of the typing.py module and will do so again for Python > 3.7, he's the s

[python-committers] How to force Travis to re-run?

I'm trying to merge this: https://github.com/python/cpython/pull/5113 Travis failed, but not due to something in this PR (looks like a random networking failure). How do I trigger the Travis check to re-run? Or I guess just skipping it would be okay as a last resort, but I'd really like to try

Re: [python-committers] How to force Travis to re-run?

job on this one. Alex On Sat, Jan 6, 2018 at 11:43 AM, Eric V. Smith <mailto:[email protected]>> wrote: I'm trying to merge this: https://github.com/python/cpython/pull/5113 <https://github.com/python/cpython/pull/5113> Travis failed, but not due to something

Re: [python-committers] Let's give commit privileges to Nathaniel J. Smith

On 1/24/2018 6:23 PM, Yury Selivanov wrote: Hi, I want to propose granting commit privileges to Nathaniel J. Smith. He's interested in the idea of becoming a core developer, and given the quality of his contributionsI think he won't need any extensive mentoring (although I'll be happy to assist

Re: [python-committers] Welcome the 3.8 and 3.9 Release Manager - Łukasz Langa!

That's awesome! A great choice. Congrats, Łukasz. Eric. On 1/27/2018 4:02 PM, Barry Warsaw wrote: As Ned just announced, Python 3.7 is very soon to enter beta 1 and thus feature freeze. I think we can all give Ned a huge round of applause for his amazing work as Release Manager for Python 3.

Re: [python-committers] Proposing Mark Shannon to be a core developer

+1 Eric On 5/14/18 4:41 PM, Larry Hastings wrote: Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation. This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document.

[python-committers] AppVeyor and Travis-CI

I accidentally checked in some test files, and they got backported to 3.7. I pushed a commit to delete them, and it was committed to master. But in the 3.7 backport, something has gone wrong with AppVeyor and Travis-CI. https://github.com/python/cpython/pull/6844 AppVeyor says "Expected — Wa

Re: [python-committers] AppVeyor and Travis-CI

look again. On 5/15/18 11:23 AM, Brett Cannon wrote: You can always close and then open an issue to re-trigger CI. As for Travis specifically, you should have the proper permissions to forcibly re-run the builds. On Mon, 14 May 2018 at 21:50 Eric V. Smith mailto:[email protected]>> wrote:

Re: [python-committers] AppVeyor and Travis-CI

f you're not seeing those it means either a) you're not logged into Travis, b) somehow it's not picking up your permissions correctly. Alex On Tue, May 15, 2018 at 11:36 AM Eric V. Smith <mailto:[email protected]>> wrote: Thanks. You mean close and re-open the bpo is

Re: [python-committers] Missing In Action

On 6/17/2018 9:18 PM, Brett Cannon wrote: We could call them  "dormant". Sounds good. And I obviously support culling our membership list for the exact reasons Victor listed (especially since I was planning to do this at some point anyway :) . My only question is whether we care about leav

[python-committers] If I backport to 3.7, it will not go into 3.7.0, correct?

I have a few things I want to fix in 3.7.1, but don't need to be 3.7.0. I can backport those to the 3.7 branch now, correct? Reading Ned's message I wasn't exactly sure of the timing and don't want to screw things up. I assume he's keeping a private branch for 3.7.0. Eric

Re: [python-committers] If I backport to 3.7, it will not go into 3.7.0, correct?

Thanks, Terry. -- Eric > On Jun 23, 2018, at 10:31 AM, Terry Reedy wrote: > >> On 6/23/2018 8:37 AM, Eric V. Smith wrote: >> I have a few things I want to fix in 3.7.1, but don't need to be 3.7.0. I >> can backport those to the 3.7 branch now, correct

Re: [python-committers] 3.7.0 / 3.6.6 Update: all systems go for final releases!

Congrats, Ned. Thank you for all of your hard work! -- Eric > On Jun 26, 2018, at 2:39 AM, Ned Deily wrote: > > A quick update: after many months we are at the finish line. We are on > track (mixing metaphors) to release 3.7.0 (and 3.6.6) this week on > 2018-06-27. Since 3.7.0rc1 shipped 2 week

Re: [python-committers] An alternative governance model

On 7/17/2018 10:02 PM, Barry Warsaw wrote: I’d like to propose an alternative model, and with it a succession plan, that IMHO hasn’t gotten enough discussion. It’s fairly radical in that it proposes to not actually change that much! TL;DR: I propose keeping a singular BDFL and adding a Counci

Re: [python-committers] List of all core developers

On 8/1/2018 8:32 PM, Mariatta Wijaya wrote: I think it would also be a good idea to include core developers of other Python implementations in such a document, in separate sections, e.g. for Jython, IronPython, PyPy, Stackless, etc Hmm, I don't think it is should be our (CPython

Re: [python-committers] List of all core developers

On 8/2/2018 3:32 AM, M.-A. Lemburg wrote: On 02.08.2018 03:24, Eric V. Smith wrote: On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:     I think it would also be a good idea to include core developers     of other Python implementations in such a document, in     separate sections, e.g. for

Re: [python-committers] List of all core developers

addresses over the years, some of which are non-obviously associated with me, and some of which I no longer have access to. Eric 2018-08-02 10:59 GMT+02:00 Eric V. Smith <mailto:[email protected]>>: On 8/2/2018 3:32 AM, M.-A. Lemburg wrote: On 02.08.2018 03:24, Eric V

[python-committers] How to retry backport?

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 this stage, how do I get the backport to try again? I have spo

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

Ah. Thanks! -- Eric > On Aug 12, 2018, at 8:22 AM, Berker Peksağ wrote: > >> 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 clos

Re: [python-committers] Draft ballot text

On 11/30/2018 3:51 AM, Nathaniel Smith wrote: Oh yeah, one odd thing I noticed: according to PEP 8001, the vote runs from Dec. 1 to Dec. 16, i.e., two weeks + two days. Is this... intentional? Of course 16 is a good round number, but it still seemed strange. Maybe it's supposed to give us a littl

Re: [python-committers] Draft ballot text

> On Nov 30, 2018, at 4:49 AM, Antoine Pitrou wrote: > > >> Le 30/11/2018 à 10:30, Eric V. Smith a écrit : >>> On 11/30/2018 3:51 AM, Nathaniel Smith wrote: >>> Oh yeah, one odd thing I noticed: according to PEP 8001, the vote runs >>> from Dec. 1

Re: [python-committers] *Important*: Python governance vote (December 2018): Ballots Sent

On 12/2/2018 9:46 AM, Chris Withers wrote: In fact, it looks like https://github.com/python/voters is entirely private. How does one get access to it? Are you logged in to github with your python committer id? Eric On 02/12/2018 14:42, Chris Withers wrote: The link you forwarded 404's f

Re: [python-committers] Merge with spurious CI failures?

Surely there must be some way around it. After all, how would you merge a PR to fix this test? -- Eric V. Smith True Blade Systems, Inc (301) 859-4544 > On May 8, 2019, at 11:49 AM, Mariatta wrote: > > If you can't merge from GitHub UI then you won't be able to do it fro

Re: [python-committers] Merge with spurious CI failures?

D’oh! Good point! Eric > On May 8, 2019, at 11:52 AM, Alex Gaynor wrote: > > Tests for that PR would presumably be green :-) > > Alex > >> On Wed, May 8, 2019 at 11:51 AM Eric V. Smith wrote: >> Surely there must be some way around it. After all, how would

[python-committers] Blurb question: error in Misc/NEWS.d/3.8.0b1.rst

I made a typo in a blurb file that's been incorporated into Misc/NEWS.d/3.8.0b1.rst. I referenced an incorrect bpo number. How do I go about fixing it? Can I just modify that .rst file, or is there some other process I need to perform? Eric ___ pytho

[python-committers] Re: Blurb question: error in Misc/NEWS.d/3.8.0b1.rst

> On Jun 19, 2019, at 11:11 PM, Ned Deily wrote: > >> On Jun 19, 2019, at 21:00, Eric V. Smith wrote: >> I made a typo in a blurb file that's been incorporated into >> Misc/NEWS.d/3.8.0b1.rst. I referenced an incorrect bpo number. How do I go >> about fix

[python-committers] Re: [Python-checkins] remove a strange non-ASCII character in _iomodule.c (GH-17239)

Replying to python-committers for visibility, although maybe python-dev would be better. That's not a "strange non-ASCII character"! That's a form feed (control-L), definitely defined by ASCII. There are plenty of these in the code. Some people (who won't be named, but match the regex "Barry

[python-committers] Re: Language Summit

I am reliant on summaries and anyone attending posting details.  Everyone please share your slides if you have any that are meaningful without a talk to go with them. At least to this committers list or discourse forum.  I expect I feel just like all of our non-travel-enabled colleagues who f

[python-committers] Re: GitHub pull requests

On 7/9/2020 3:29 PM, Mariatta wrote: If you want the associated bpo ticket to be closed when the PR is merged, you have to add the commit message saying "closes " (Note that we should document this: https://github.com/python/devguide/issues/502) Is there a way to do this if you have automerge

[python-committers] Re: GitHub pull requests

On 7/9/2020 4:01 PM, Mariatta wrote: Is there a way to do this if you have automerge set? I don't see a way to control the commit message in that case, but I could easily be missing something. Yes, you need to edit the PR description. Automerge will take the PR description as the

[python-committers] Re: MSDN Subscription renewals

Hi, Steve. I’ve checked my spam folders and settings, but I don’t see an MSDN email. Could you double check that I was included? Thanks. -- Eric V. Smith (301) 502-0945 cell > On Aug 21, 2020, at 3:22 PM, Steve Dower wrote: > > Thanks everyone. > > Those who sent me the

[python-committers] Re: MSDN Subscription renewals

And of course I sent this to everyone by mistake. Sorry about that. That will teach me to do things from my phone. -- Eric V. Smith (301) 502-0945 cell > On Aug 29, 2020, at 4:25 PM, Eric V. Smith wrote: > > Hi, Steve. > > I’ve checked my spam folders and settings, but I do

[python-committers] Re: MSDN Subscription renewals

Ah. Thanks, Antoine. I’ll check. -- Eric V. Smith (301) 502-0945 cell > On Aug 29, 2020, at 4:27 PM, Antoine Pitrou wrote: > >  > I don't think you receive an e-mail. You should just log in to your > account and check your subscription's expiration date.

[python-committers] Re: MSDN Subscription renewals

ine. Le 29/08/2020 à 22:25, Eric V. Smith a écrit : And of course I sent this to everyone by mistake. Sorry about that. That will teach me to do things from my phone. -- Eric V. Smith (301) 502-0945 cell On Aug 29, 2020, at 4:25 PM, Eric V. Smith wrote: Hi, Steve. I’ve checked my spam folde

[python-committers] cherry_picker problem

For reasons I don't understand, https://github.com/python/cpython/pull/9 failed to backport to 3.9. The message says: Sorry @eamanu , I had trouble checking out the |3.9| backport branch. Please backport using cherry_picker

[python-committers] Re: cherry_picker problem

Although maybe it did succeed? https://github.com/python/cpython/pull/22232 was created. Eric On 9/13/2020 5:32 PM, Eric V. Smith wrote: For reasons I don't understand, https://github.com/python/cpython/pull/9 failed to backport to 3.9. The message says: Sorry @eamanu &

[python-committers] Re: cherry_picker problem

On 9/13/2020 7:42 PM, Terry Reedy wrote: On 9/13/2020 5:32 PM, Eric V. Smith wrote: For reasons I don't understand, https://github.com/python/cpython/pull/9 failed to backport to 3.9. The message says: Sorry @eamanu <https://github.com/eamanu>, I had trouble checking ou

[python-committers] bedevere/issue-number and bedevere/news: waiting for status to be reported

I'm trying to merge this: https://github.com/python/cpython/pull/23855 It says that it's waiting on bedevere/issue-number and bedevere/news, with status "Waiting for status to be reported". The PR is tagged with "skip issue" and "skip news" (even though it has an issue). So I guess these are i

[python-committers] Re: bedevere/issue-number and bedevere/news: waiting for status to be reported

7;t see any error logged in heroku. The app is running, yet the webhooks appeared to be delivered successfully, returning 200 status. Perhaps there's a problem from GitHub side. I'm on my phone right now and not able to further investigate until later this evening. On Sat., Dec.

[python-committers] Re: Irrelevant .whl attachment to tracker issue

s.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/YAJ6LWVRBJHG2RLUMJU5M6KRFFJF5677/ Code of Conduct: https://www.python.org/psf/codeofconduct/ -- Eric V. Smith ___ python-committers mailing list -- python-comm

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

CG7Q/ Code of Conduct: https://www.python.org/psf/codeofconduct/ -- Eric V. Smith ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-co

[python-committers] Re: core-dev chat

On 5/15/2021 11:57 AM, Senthil Kumaran wrote: On Sat, May 15, 2021 at 04:16:20PM +0200, Antoine Pitrou wrote: You still haven't explained why e.g. Zulip (which has a modern Web UI, a very well-thought threading mechanism, several clients, many integrations, is widely used, and is open source), d

[python-committers] What is github trying to tell me?

https://github.com/python/cpython/pull/28163 has two messages of: @ericvsmith : Status check is done, and it's a failure ❌ . Followed by the merge messages, followed by: @ericvsmith : Status check is done, and it's a success ✅ .

[python-committers] Re: What is github trying to tell me?

nation. On Sat, Sep 4, 2021 at 1:47 PM Eric V. Smith <mailto:[email protected]>> wrote: https://github.com/python/cpython/pull/28163 <https://github.com/python/cpython/pull/28163> has two messages of: @ericvsmith <https://github.com/ericvsmith>: Status che

[python-committers] What's the schedule for the core sprint?

I'm traveling and I don't know when I'll be free. If there's a schedule of any events, I'll try and make some of those. Also, any instructions for Discord (URL, how to get to the core sprint channel(s)) would be appreciated. I don't know much about Discord. Thanks.

[python-committers] Re: What's the schedule for the core sprint?

Got it. Thanks, Dong-hee! Eric On 10/17/2021 10:08 PM, Dong-hee Na wrote: Hi, Eric I sent you a direct mail about the Discord server :) Regards, Dong-hee 2021년 10월 18일 (월) 오전 10:48, Eric V. Smith 님이 작성: I'm traveling and I don't know when I'll be free. If there&#

Re: [python-committers] Commit privs for Serhiy Storchaka?

+1 -- Eric. On Dec 24, 2012, at 12:07 PM, Trent Nelson wrote: >He's pretty active on IRC and the tracker. I haven't dealt with any >of his patches personally, but I know lots of others have. Thoughts? > >Trent. > ___ > python-commit

Re: [python-committers] Commit privs for Serhiy Storchaka?

On 12/26/2012 1:00 PM, Serhiy Storchaka wrote: > середа 26 грудень 2012 19:44:34 Eli Bendersky ви написали: >> On Wed, Dec 26, 2012 at 9:38 AM, Georg Brandl wrote: >>> The SSH key is added; tracker privileges were already given. >>> >>> Welcome Serhiy! >> >> Yes, welcome! >> >> Serhiy, if you have

Re: [python-committers] Commit privileges for Roger Serwy for IDLE

On 3/20/2013 11:26 PM, Ned Deily wrote: > In article > , > Nick Coghlan wrote: >> +lots, let's make it happen. > > Thanks everyone for your positive feedback. Roger has indicated he's > still interested. I've pointed him at the developer's guide section for > new committers, in particular,

Re: [python-committers] SSH fingerprint

On 3/26/2013 8:39 AM, Roger Serwy wrote: > >> Well if a MITM attacker tries to use your ssh access to do anything >> nasty, >> another developer will probably notice quite quickly. >> (the only "nasty thing" the ssh access allows you to do is "hg push", >> IIRC; still, that can trigger code execut

Re: [python-committers] clinic churn after beta2

On 1/7/2014 7:33 PM, Benjamin Peterson wrote: > A PyPI module is not so great because you'll have to change every > formatting operation to use a function from a module rather than the % > operator or the format method. I think this is the crux of the issue. Are we trying to say "porting your exis

Re: [python-committers] Commit access for Yury Selivanov?

On 1/22/2014 10:05 PM, Benjamin Peterson wrote: > I don't see anyone complaining too loudly, so have him send his key to > [email protected]. I've added him to python-committers. Welcome, Yury! Eric. ___ python-committers mailing list python-commi

[python-committers] Fwd: CPython repository - changeset not merged into default from 3.4?

I responded to Vinay, but I haven't heard back. I'm forwarding here in case someone else is impacted. I meant to make this change on the default branch only, but I accidentally made it on 3.4. If someone could revert it for me, I'd appreciate it. I'm away from a computer all day. I'll fix it w

Re: [python-committers] New core developer: Xiang Zhang

On 11/22/16 9:21 AM, Victor Stinner wrote: * python-committers: he subscribed to python-committers. Can someone check if you got it (and approve it)? His email adddress is [email protected] I didn't see a request, so I just subscribed him. Welcome aboard Xiang! Yes, welcome! Eric.

Re: [python-committers] autoconf 2.70

> On Nov 24, 2016, at 10:00 AM, R. David Murray wrote: > Right, tracking those artifacts is a long standing policy and exists > for good reasons. Our policy is that the committed changes should > be done with the "right" version of the tool to minimize churn, and > I think we should maintain th

Re: [python-committers] Pace of change for Python 3.x

On 1/25/2017 7:30 AM, Antoine Pitrou wrote: We'd just say: this is our new LTS release (e.g. Python 3.7) and then move on until we're confident again that the feature set has stabilized enough to create a new LTS release. In practice you wouldn't just "move on" but have to maintain that LTS rel

[python-committers] Re: Do people still find this mailing list useful?

I think it should be retired. I also think the same for python-ideas. Eric On 7/3/2023 3:15 PM, Brett Cannon wrote: The question has come up as to whether people still find this mailing list useful enough to keep around. Looking at the archive (https://mail.python.org/archives/list/python-comm