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

[Eric V. Smith via python-committers]

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-committers@python.org/latest), 
this list seems to be used for two things:


 1. Announcing new releases
 2. Announcing new core developers

In both cases the things are announced (at least) at 
discuss.python.org , and so are not 
exclusive to this list.


So, do people find this list useful enough to keep around, or should 
we archive it?


___
python-committers mailing list --python-committers@python.org
To unsubscribe send an email topython-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived 
athttps://mail.python.org/archives/list/python-committers@python.org/message/WAVEXV3FAK6IFMXTVO7PRNYOY66NBP2F/
Code of Conduct:https://www.python.org/psf/codeofconduct/___
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.python.org/archives/list/python-committers@python.org/message/JCYEQRWXWJA6E7DYWB2O5P5CCY2CYLO4/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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'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 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.python.org/archives/list/python-committers@python.org/message/LLXNUWXCPYQLYJTYYENYR3U47CS3DB64/
Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/PBWJEABZVRZCU4AOBV2ELRZ4RGBDTNVC/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 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.python.org/archives/list/python-committers@python.org/message/LLXNUWXCPYQLYJTYYENYR3U47CS3DB64/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

Thanks. I'll continue to ignore them, unless I hear otherwise on this list.

Eric

On 9/4/2021 5:42 PM, Guido van Rossum wrote:
I see this all the time and just ignore it. I have a feeling it's due 
to the miss-islington bot being triggered by some event and checking 
in on the PR while it is still transitioning. Occasionally I see a 
very large string of these and assume she's just having a bad day. 
Also notice that in your PR there are actually two of those failure 
messages, the second one being suppressed by the GitHub UI.


But maybe Mariatta has a more reasoned explanation.

On Sat, Sep 4, 2021 at 1:47 PM Eric V. Smith <mailto:e...@trueblade.com>> 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 check is done,
and it's a failure ❌ .

Followed by the merge messages, followed by:

@ericvsmith <https://github.com/ericvsmith>: Status check is done,
and it's a success ✅ .

What do the failure messages mean? Is it because I didn't wait for
the checks to complete before merging?

(It's a documentation only change that I previously committed to
main without incident, so I didn't feel the need to wait for all
of the checks to run before merging.)

Thanks for any insight.

Eric

___
python-committers mailing list -- python-committers@python.org
<mailto:python-committers@python.org>
To unsubscribe send an email to python-committers-le...@python.org
<mailto:python-committers-le...@python.org>
https://mail.python.org/mailman3/lists/python-committers.python.org/
<https://mail.python.org/mailman3/lists/python-committers.python.org/>
Message archived at

https://mail.python.org/archives/list/python-committers@python.org/message/U7A4R6TUGBD3KNAF3F2JJGNQ6V7B5G4D/

<https://mail.python.org/archives/list/python-committers@python.org/message/U7A4R6TUGBD3KNAF3F2JJGNQ6V7B5G4D/>
Code of Conduct: https://www.python.org/psf/codeofconduct/
<https://www.python.org/psf/codeofconduct/>



--
--Guido van Rossum (python.org/~guido <http://python.org/~guido>)
/Pronouns: he/him //(why is my pronoun here?)/ 
<http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
___
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.python.org/archives/list/python-committers@python.org/message/O3ATC52NVGZJ4VRZG4AVTLXURXWMT3CM/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 ✅ .


What do the failure messages mean? Is it because I didn't wait for the 
checks to complete before merging?


(It's a documentation only change that I previously committed to main 
without incident, so I didn't feel the need to wait for all of the 
checks to run before merging.)


Thanks for any insight.

Eric

___
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.python.org/archives/list/python-committers@python.org/message/U7A4R6TUGBD3KNAF3F2JJGNQ6V7B5G4D/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Eric V. Smith]

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), doesn't « address our evolving needs ».

- Zulip didn't take-off as well as we intended for python (core-dev)
   group. If it had, this discussion wouldn't have been necessary.


I think Zulip didn't catch on because most core devs prefer 
communicating on mailing lists for technical issues.


If the intent of this new core-dev chat is just a social "how are you 
doing" sort of thing, then I think Zulip (or most anything else) would 
work fine.


Eric

___
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.python.org/archives/list/python-committers@python.org/message/SIXFJXPVCYN7TSBIPJH4VXMS7ZQ2QBR4/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

I've noticed this too. I'm pretty sure it predates the master -> main 
change.


Eric

On 5/12/2021 10:22 AM, Guido van Rossum wrote:
Recently it seems that when a PR linked to a bpo issue is merged, no 
note of this event is made in the bpo issue. Look at 
https://bugs.python.org/issue43933 
<https://bugs.python.org/issue43933> for example. There are notes for 
the first two merged PRs (25717 and 25719), at
https://bugs.python.org/issue43933#msg392343 
<https://bugs.python.org/issue43933#msg392343> and the next message. 
But I cannot find a similar note for the third PR, 26054, which is 
also merged.


I recall seeing this for other recent issues as well. Did some piece 
of automation recently break? (Could it have to do with the 
master->main move?)

--
--Guido (mobile)

___
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.python.org/archives/list/python-committers@python.org/message/M2Z3WSJ4SGGH2GQ7D5NELAZSD3PECG7Q/
Code of Conduct: https://www.python.org/psf/codeofconduct/


--
Eric V. Smith

___
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.python.org/archives/list/python-committers@python.org/message/GNVV2ZJM7JLJB4CPUUII7PKU6MWAHVJT/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

At first blush it looks like a normal wheel file:

$ unzip -l pb_tool-3.1.0-py3-none-any.whl
Archive:  pb_tool-3.1.0-py3-none-any.whl
  Length  Date    Time    Name
-  -- -   
    0  12-22-2018 00:17   pb_tool/__init__.py
    42268  11-24-2019 01:50   pb_tool/pb_tool.py
    4  12-21-2018 23:11   pb_tool/templates/basic.tmpl
    4  12-21-2018 23:11   pb_tool/templates/dialog.tmpl
 1034  12-21-2018 23:11   pb_tool/templates/icon.png
 2710  11-22-2019 23:39   pb_tool/templates/pb_tool.tmpl
 1439  11-22-2019 23:39 pb_tool/templates/dialog/__init__.tmpl
 6760  11-22-2019 23:39 pb_tool/templates/dialog/module_name.tmpl
 1765  11-22-2019 23:39 
pb_tool/templates/dialog/module_name_dialog.tmpl
 1518  12-21-2018 23:11 
pb_tool/templates/dialog/module_name_dialog_base.ui.tmpl

  692  11-22-2019 23:39 pb_tool/templates/dialog/readme.tmpl
  117  12-21-2018 23:11 pb_tool/templates/dialog/resources.tmpl
 1733  11-22-2019 23:39 pb_tool/templates/dialog/results.tmpl
 1089  11-22-2019 23:39 pb_tool/templates/minimal/__init__.py
  211  11-22-2019 23:39 pb_tool/templates/minimal/metadata.txt
    18027  11-24-2019 01:51   pb_tool-3.1.0.dist-info/LICENSE
  877  11-24-2019 01:51   pb_tool-3.1.0.dist-info/METADATA
   92  11-24-2019 01:51   pb_tool-3.1.0.dist-info/WHEEL
   99  11-24-2019 01:51 pb_tool-3.1.0.dist-info/entry_points.txt
    8  11-24-2019 01:51 pb_tool-3.1.0.dist-info/top_level.txt
 1844  11-24-2019 01:51   pb_tool-3.1.0.dist-info/RECORD
- ---
    82291 21 files

Unzipped, pb_tool.py starts with:

$head pb_tool.py
"""
/***
    qpbt
 A tool for building and deploying QGIS plugins
  ---
    begin    : 2014-09-24
    copyright    : (C) 2014 by GeoApt LLC
    email    : gsher...@geoapt.com
 ***/

Five seconds worth of looking at it doesn't raise any alarms, although 
I'm not  going to install or execute anything!


I think it was probably uploaded in error, and should just be unlinked 
and marked as spam.


Eric

On 4/29/2021 12:39 AM, Terry Reedy wrote:

https://bugs.python.org/issue41608
Userid ttx11529 uploaded, without posting anything, a file called 
pb_tool-3.1.0-py3-none-any.whl.


As best I understand, if the name is not forged, this is a file that 
pip would use to install pb_tool 3.1.0 to any 3.x python.

https://pypi.org/project/pb-tool/
"pb_tool provides commands to deploy and publish a QGIS Python plugin."

The user list gives the real name as ปพนพัชร์ บรรพจันทร์.
Translate.google.com identifies this as Thai, transliterated to Paphon 
Phatch Banchan.


This user's only other tracker activity so far was adding self as nosy to
https://bugs.python.org/issue43651
45 min before uploading this file.

This could be a clueless newbie, an ordinary spammer, or a malware 
spreader.


Should anything be done other than marking the file as spam and 
unlinking it?


Does anyone know how to safely examine the file, and care to?

Terry

___
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.python.org/archives/list/python-committers@python.org/message/YAJ6LWVRBJHG2RLUMJU5M6KRFFJF5677/

Code of Conduct: https://www.python.org/psf/codeofconduct/


--
Eric V. Smith

___
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.python.org/archives/list/python-committers@python.org/message/36YH6L2UHFUOFSLHNTYGS6BKH6AZBDFR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

Thanks, Mariatta.

I just removed the "skip issue" tag, and presto: "All checks have 
passed". I'm not sure what's up, but at least I can merge this issue now.


Eric

On 12/19/2020 3:24 PM, Mariatta wrote:
I tried removing the labels and adding them back. I didn'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. 19, 2020, 11:50 a.m. Eric V. Smith, <mailto:e...@trueblade.com>> wrote:


I'm trying to merge this:
https://github.com/python/cpython/pull/23855
<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 inspected by bedevere, which
isn't responding.

I've tried opening and closing the issue to re-trigger things, to
no avail.

What can I do to commit this PR? Does bedevere need to be kicked
into life somehow? Is anyone else seeing this problem?

Thanks.

Eric

___
python-committers mailing list -- python-committers@python.org
<mailto:python-committers@python.org>
To unsubscribe send an email to python-committers-le...@python.org
<mailto:python-committers-le...@python.org>
https://mail.python.org/mailman3/lists/python-committers.python.org/
<https://mail.python.org/mailman3/lists/python-committers.python.org/>
Message archived at

https://mail.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/

<https://mail.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/>
Code of Conduct: https://www.python.org/psf/codeofconduct/
<https://www.python.org/psf/codeofconduct/>

___
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.python.org/archives/list/python-committers@python.org/message/L5FSQC4EEQ5LTLAWAZZ62GNT5US62HP3/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 inspected by bedevere, which isn't responding.


I've tried opening and closing the issue to re-trigger things, to no avail.

What can I do to commit this PR? Does bedevere need to be kicked into 
life somehow? Is anyone else seeing this problem?


Thanks.

Eric

___
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.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: cherry_picker problem

[Eric V. Smith]

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 out 
the |3.9| backport branch.
Please backport using cherry_picker 
<https://pypi.org/project/cherry-picker/> on command line.


This particular failure seems to be very low probability random. 
Perhaps a timing issue.  I believe I usually re-add backport label 
(removing first if needed).


Thanks, Terry. That's a better plan than trying cherry_picker manually.

Eric
___
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.python.org/archives/list/python-committers@python.org/message/NAUNYXJABVIIPJMT6NKIJBAHM5J6627K/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: cherry_picker problem

[Eric V. Smith]

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 <https://github.com/eamanu>, I had trouble checking out 
the |3.9| backport branch.
Please backport using cherry_picker 
<https://pypi.org/project/cherry-picker/> on command line.


I don't know if this problem with checking out the 3.9 backport branch 
is part of my problem or not. The backport to 3.8 succeeded.


So, I'm trying to run cherry_picker, as suggested. It's set up locally 
with the most recent version (1.3.2). My local repo has an origin and 
an upstream remote:


[~/local/python/cpython]$ git remote -v
origin g...@github.com:ericvsmith/cpython.git (fetch)
origin g...@github.com:ericvsmith/cpython.git (push)
upstream g...@github.com:python/cpython.git (fetch)
upstream g...@github.com:python/cpython.git (push)

When I run cherry_picker, it says "Failed to push to origin ☹". I 
don't know why that would be, or what the implications are (except the 
backport not succeeding). The full output of running cherry_picker is 
below. As near as I can tell, there are no conflicts.


Any ideas? If I can't figure it out, I'll just leave this minor 
documentation fix in master and 3.8, but not 3.9.


Eric


[~/local/python/cpython]$ cherry_picker 
94bfdee25db31941b187591ae5ae9bf3ed431090 3.9

  ⛏

Now backporting '94bfdee25db31941b187591ae5ae9bf3ed431090' into '3.9'
Switched to a new branch 'backport-94bfdee-3.9'
Branch 'backport-94bfdee-3.9' set up to track remote branch '3.9' from 
'upstream'.


[backport-94bfdee-3.9 37b1f2eaae] bpo-41778: Change a punctuation on 
documentation. (GH-9)

 Author: Emmanuel Arias 
 Date: Sun Sep 13 18:05:44 2020 -0300
 1 file changed, 2 insertions(+), 2 deletions(-)

Failed to push to origin ☹
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

Deleted branch backport-94bfdee-3.9 (was 97bcdc8e9c).

branch backport-94bfdee-3.9 has been deleted.


___
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.python.org/archives/list/python-committers@python.org/message/BHG4HVMBZUT5RHQCEIEKU4QKTBD6FMCF/
Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/GX3ETQ5CSKUGJF72CZX72RAI6ZRIOTSV/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] cherry_picker problem

[Eric V. Smith]

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 
 on command line.


I don't know if this problem with checking out the 3.9 backport branch 
is part of my problem or not. The backport to 3.8 succeeded.


So, I'm trying to run cherry_picker, as suggested. It's set up locally 
with the most recent version (1.3.2). My local repo has an origin and an 
upstream remote:


[~/local/python/cpython]$ git remote -v
origin  g...@github.com:ericvsmith/cpython.git (fetch)
origin  g...@github.com:ericvsmith/cpython.git (push)
upstream    g...@github.com:python/cpython.git (fetch)
upstream    g...@github.com:python/cpython.git (push)

When I run cherry_picker, it says "Failed to push to origin ☹". I don't 
know why that would be, or what the implications are (except the 
backport not succeeding). The full output of running cherry_picker is 
below. As near as I can tell, there are no conflicts.


Any ideas? If I can't figure it out, I'll just leave this minor 
documentation fix in master and 3.8, but not 3.9.


Eric


[~/local/python/cpython]$ cherry_picker 
94bfdee25db31941b187591ae5ae9bf3ed431090 3.9

  ⛏

Now backporting '94bfdee25db31941b187591ae5ae9bf3ed431090' into '3.9'
Switched to a new branch 'backport-94bfdee-3.9'
Branch 'backport-94bfdee-3.9' set up to track remote branch '3.9' from 
'upstream'.


[backport-94bfdee-3.9 37b1f2eaae] bpo-41778: Change a punctuation on 
documentation. (GH-9)

 Author: Emmanuel Arias 
 Date: Sun Sep 13 18:05:44 2020 -0300
 1 file changed, 2 insertions(+), 2 deletions(-)

Failed to push to origin ☹
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

Deleted branch backport-94bfdee-3.9 (was 97bcdc8e9c).

branch backport-94bfdee-3.9 has been deleted.

___
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.python.org/archives/list/python-committers@python.org/message/BHG4HVMBZUT5RHQCEIEKU4QKTBD6FMCF/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: MSDN Subscription renewals

[Eric V. Smith]

You're correct. Thanks for the pointer, Antoine. Not sure why I was 
expecting an email.


Eric

On 8/29/2020 4:26 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.

Regards

Antoine.


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 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 their details last week should have their renewals already, 
and anyone who emailed me since last Friday will get theirs shortly.

Cheers,
Steve


On 8/13/2020 6:29 PM, Steve Dower wrote:

Hi all
It seems like people are due to renew their subscriptions, and after a bit of 
internal-to-Microsoft organisational turmoil, I've found out who can provide 
them.
While most of the tooling necessary for working on CPython is freely available 
(as Visual Studio Community), this will also include OS images and Azure 
credits.
Historically, Brian Curtin has helped out by collating our details and 
submitting the request, but now it's being passed over to me (since I can more 
easily track any internal changes).
If you would like to be signed up for a subscription, or renew your current 
one, please reply to me by Friday August 21st with your full name and email 
address.
(Your email address should be able to log in at https://my.visualstudio.com/ If it can't, 
click "Create one" and you can activate your existing address.)
Thanks,
Steve

___
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.python.org/archives/list/python-committers@python.org/message/MPOCPQTPW4X36KXU2H4DLD52P6BMCZNS/
Code of Conduct: https://www.python.org/psf/codeofconduct/

___
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.python.org/archives/list/python-committers@python.org/message/YIALYZFRAM3LKZHJOVUL5BMGOOJV2QAR/
Code of Conduct: https://www.python.org/psf/codeofconduct/


___
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.python.org/archives/list/python-committers@python.org/message/KJUPK2S5RHKOV5ANG3TRKKN3YHORT3ZC/
Code of Conduct: https://www.python.org/psf/codeofconduct/

___
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.python.org/archives/list/python-committers@python.org/message/76MPNOQISHMADXHORRHCC5N3UXZKZRFV/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: MSDN Subscription renewals

[Eric V. Smith]

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.
> 
> Regards
> 
> Antoine.
> 
> 
>> 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 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 their details last week should have their renewals 
>>>> already, and anyone who emailed me since last Friday will get theirs 
>>>> shortly.
>>>> 
>>>> Cheers,
>>>> Steve
>>>> 
>>>>>> On 8/13/2020 6:29 PM, Steve Dower wrote:
>>>>> Hi all
>>>>> It seems like people are due to renew their subscriptions, and after a 
>>>>> bit of internal-to-Microsoft organisational turmoil, I've found out who 
>>>>> can provide them.
>>>>> While most of the tooling necessary for working on CPython is freely 
>>>>> available (as Visual Studio Community), this will also include OS images 
>>>>> and Azure credits.
>>>>> Historically, Brian Curtin has helped out by collating our details and 
>>>>> submitting the request, but now it's being passed over to me (since I can 
>>>>> more easily track any internal changes).
>>>>> If you would like to be signed up for a subscription, or renew your 
>>>>> current one, please reply to me by Friday August 21st with your full name 
>>>>> and email address.
>>>>> (Your email address should be able to log in at 
>>>>> https://my.visualstudio.com/ If it can't, click "Create one" and you can 
>>>>> activate your existing address.)
>>>>> Thanks,
>>>>> Steve
>>>> ___
>>>> 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.python.org/archives/list/python-committers@python.org/message/MPOCPQTPW4X36KXU2H4DLD52P6BMCZNS/
>>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> ___
>> 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.python.org/archives/list/python-committers@python.org/message/YIALYZFRAM3LKZHJOVUL5BMGOOJV2QAR/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> 
> ___
> 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.python.org/archives/list/python-committers@python.org/message/KJUPK2S5RHKOV5ANG3TRKKN3YHORT3ZC/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/M2AZ62MNYKR2VE4XKPUYPHAEUXK55HR2/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: MSDN Subscription renewals

[Eric V. Smith]

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 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 their details last week should have their renewals 
>> already, and anyone who emailed me since last Friday will get theirs shortly.
>> 
>> Cheers,
>> Steve
>> 
>>>> On 8/13/2020 6:29 PM, Steve Dower wrote:
>>> Hi all
>>> It seems like people are due to renew their subscriptions, and after a bit 
>>> of internal-to-Microsoft organisational turmoil, I've found out who can 
>>> provide them.
>>> While most of the tooling necessary for working on CPython is freely 
>>> available (as Visual Studio Community), this will also include OS images 
>>> and Azure credits.
>>> Historically, Brian Curtin has helped out by collating our details and 
>>> submitting the request, but now it's being passed over to me (since I can 
>>> more easily track any internal changes).
>>> If you would like to be signed up for a subscription, or renew your current 
>>> one, please reply to me by Friday August 21st with your full name and email 
>>> address.
>>> (Your email address should be able to log in at 
>>> https://my.visualstudio.com/ If it can't, click "Create one" and you can 
>>> activate your existing address.)
>>> Thanks,
>>> Steve
>> ___
>> 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.python.org/archives/list/python-committers@python.org/message/MPOCPQTPW4X36KXU2H4DLD52P6BMCZNS/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/YIALYZFRAM3LKZHJOVUL5BMGOOJV2QAR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: MSDN Subscription renewals

[Eric V. Smith]

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 their details last week should have their renewals already, 
> and anyone who emailed me since last Friday will get theirs shortly.
> 
> Cheers,
> Steve
> 
>> On 8/13/2020 6:29 PM, Steve Dower wrote:
>> Hi all
>> It seems like people are due to renew their subscriptions, and after a bit 
>> of internal-to-Microsoft organisational turmoil, I've found out who can 
>> provide them.
>> While most of the tooling necessary for working on CPython is freely 
>> available (as Visual Studio Community), this will also include OS images and 
>> Azure credits.
>> Historically, Brian Curtin has helped out by collating our details and 
>> submitting the request, but now it's being passed over to me (since I can 
>> more easily track any internal changes).
>> If you would like to be signed up for a subscription, or renew your current 
>> one, please reply to me by Friday August 21st with your full name and email 
>> address.
>> (Your email address should be able to log in at https://my.visualstudio.com/ 
>> If it can't, click "Create one" and you can activate your existing address.)
>> Thanks,
>> Steve
> ___
> 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.python.org/archives/list/python-committers@python.org/message/MPOCPQTPW4X36KXU2H4DLD52P6BMCZNS/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/VUYXFX6IC6YGQK5K5R6A4VNRZWCD4K7Z/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: GitHub pull requests

[Eric V. Smith]

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 commit message.



Ah. Thanks!

Eric

___
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.python.org/archives/list/python-committers@python.org/message/PBFHRMR7HBF2HBN6NOVHWG5KFXP4DYXI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: GitHub pull requests

[Eric V. Smith]

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 set? I don't see a way 
to control the commit message in that case, but I could easily be 
missing something.


Eric




If you want the the associated GitHub Issue to be closed, it is 
similar, you have to add to the commit message or the PR description:

"closes "
Documentation: 
https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword




___
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.python.org/archives/list/python-committers@python.org/message/ZQJKTDWXL2SMVVNPIJJN4HX7SG4Q6NPU/
Code of Conduct: https://www.python.org/psf/codeofconduct/
___
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.python.org/archives/list/python-committers@python.org/message/JYE3EBQLYB5J5MKNDMDECGTS5M54IONQ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Language Summit

[Eric V. Smith]

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 feel left out on a recurring basis.  =)



Hi, Greg.

Here are the slides from my talk: 
https://github.com/ericvsmith/f-strings-by-default/raw/master/F-strings%20everywhere!.pdf


I can't decide if it's worth continuing my work on a PEP. I need to 
re-read and consider the various questions and suggestions from today. 
Thanks, everyone, for your input.


Eric


___
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.python.org/archives/list/python-committers@python.org/message/CIT3S7JAZJ4OZ3YD6LO77HZRMPQBRBVU/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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") like them. I don't think we should start 
removing them.


Eric

On 11/18/2019 1:40 PM, Tal Einat wrote:

https://github.com/python/cpython/commit/bcc1cc5cc38b57ac55cbe710849374258d610a08
commit: bcc1cc5cc38b57ac55cbe710849374258d610a08
branch: master
author: Tal Einat 
committer: GitHub 
date: 2019-11-18T20:39:47+02:00
summary:

remove a strange non-ASCII character in _iomodule.c (GH-17239)

files:
M Modules/_io/_iomodule.c

diff --git a/Modules/_io/_iomodule.c b/Modules/_io/_iomodule.c
index 5932363f3af35..778b56d475ee5 100644
--- a/Modules/_io/_iomodule.c
+++ b/Modules/_io/_iomodule.c
@@ -503,7 +503,7 @@ _io_open_code_impl(PyObject *module, PyObject *path)
  {
  return PyFile_OpenCodeObject(path);
  }
-
+
  /*
   * Private helpers for the io module.
   */

___
Python-checkins mailing list
python-check...@python.org
https://mail.python.org/mailman/listinfo/python-checkins

___
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.python.org/archives/list/python-committers@python.org/message/GN5NRNWNPHOSLLQWNRDZGJPPT6KPRMMX/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

> 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 fixing it? Can I just modify that .rst file, or is there some other 
>> process I need to perform?
> 
> The individual blurb files are consolidated into a single release file by 
> release managers during a release's manufacturing steps.  Once the release is 
> out the door and the release's consolidated file appears in the repo (in this 
> case, 3.8.0b1.rst), you can merge changes to it.  Prior to the release 
> cutoff, you can modify the individual file in Misc/NEWS.d/next.  Don't forget 
> to make similar changes as necessary to any backported PRs!

That’s what I thought. Thanks for confirming, Ned. 

Eric

___
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.python.org/archives/list/python-committers@python.org/message/SYFNOPSEAALUKQYH3VNCMMA4X7OI564Q/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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
___
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.python.org/archives/list/python-committers@python.org/message/CZ3D2BZVI367V67WTWJDQ2QFLF67I6SG/
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 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 from 
>>> GitHub command line (it respects the same branch protection policy)
>>> 
>>> I don't think we should merge if tests are still failing. Perhaps the test 
>>> should be adjusted to handle this spurious errors? Can it be marked as 
>>> "allowed failure" or something like that?
>>> 
>>> 
>>>> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:
>>>> 
>>>> Hello,
>>>> 
>>>> There are spurious CI failures (SSL certificate issue in test_httplib).
>>>> Therefore the "Squash and merge" button is greyed out.
>>>> 
>>>> How should I merge? Using the command-line instructions from Github?
>>>> 
>>>> Regards
>>>> 
>>>> Antoine.
>>>> ___
>>>> python-committers mailing list
>>>> python-committers@python.org
>>>> https://mail.python.org/mailman/listinfo/python-committers
>>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>> ___
>>> python-committers mailing list
>>> python-committers@python.org
>>> https://mail.python.org/mailman/listinfo/python-committers
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
> 
> -- 
> All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 from GitHub 
> command line (it respects the same branch protection policy)
> 
> I don't think we should merge if tests are still failing. Perhaps the test 
> should be adjusted to handle this spurious errors? Can it be marked as 
> "allowed failure" or something like that?
> 
> 
>> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:
>> 
>> Hello,
>> 
>> There are spurious CI failures (SSL certificate issue in test_httplib).
>> Therefore the "Squash and merge" button is greyed out.
>> 
>> How should I merge? Using the command-line instructions from Github?
>> 
>> Regards
>> 
>> Antoine.
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 for me. I can't see a "reply" button on 
https://discuss.python.org/t/python-governance-vote-december-2018-ballots-sent/496


On 01/12/2018 17:59, Antoine Pitrou wrote:

Hello,

I'm forwarding this for the benefit of all who don't follow Discourse
actively.

Regards

Antoine.

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct:https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct:https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Draft ballot text

[Eric V. Smith]

> 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 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 little wiggle room in case
>>> the vote doesn't get sent out right at midnight on the 1st, while
>>> still keeping the two week period?
>> 
>> I assumed it was so the vote would include 2 weekends. Makes sense to me.
> 
> Three weekends (if by weekend you mean Saturday + Sunday).

Right. I meant the two weekends at the ends of the range.

Eric

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Draft ballot text

[Eric V. Smith]

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 little wiggle room in case
the vote doesn't get sent out right at midnight on the 1st, while
still keeping the two week period?


I assumed it was so the vote would include 2 weekends. Makes sense to me.

Eric



-n
On Thu, Nov 29, 2018 at 8:03 PM Nathaniel Smith  wrote:


Hi all,

Since the vote's supposed to be starting in a few days, I figured it
would be good to finish up the fiddly details and avoid any
last-minute editing. So here's a draft proposal for the ballot
instructions and options: https://github.com/python/peps/pull/844

I also set up a test vote on CIVS, so you can see how it will actually
look: 
https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_f3dd3ec110515d32=add219018ca56843

Please post any feedback on the PR or here.

-n

--
Nathaniel J. Smith -- https://vorpus.org





___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 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've just reapplied the "needs backport to 3.7" label and the bot
> opened https://github.com/python/cpython/pull/8746
> 
> --Berker
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] How to retry backport?

[Eric V. Smith]

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 spotty internet access, so it might take me a while to try this 
again.


Thanks.

Eric

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

On 8/2/2018 7:53 AM, Stefan Richthofer wrote:

Again, this was in the (poorly conveyed) context of getting email
addresses for them, or at least being able to contact them.


I always thought there were already at least three places containing the 
necessary email addresses.


* python-committers should be exactly this mailing list.
* according to https://devguide.python.org/coredev/#issue-tracker it is 
mandatory for core developers to subscribe to the issue tracker which 
AFAIK requires a confirmed email address.
* Every committer clearly must have signed the contributor agreement 
https://www.python.org/psf/contrib/contrib-form/ wich also contains a 
mandatory email field


So why is it still necessary to get email addresses at all?


I don't recall, exactly. It was at an early Language Summit, and we were 
looking for ways to contact everyone and to associate people with email 
addresses. It might have involved the mercurial migration. Maybe it's 
not still required. My point is that it's hard to come up with a list of 
core devs and match them with email addresses. If that's not the 
requirement here, then great!


I know I've had several 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:e...@trueblade.com>>:


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 Jython, IronPython, PyPy,
  Stackless, etc


Hmm, I don't think it is should be our (CPython)
responsibility to
keep track and maintain the list of the core devs of
alternate Python
implementations. Don't they have their own community /
website? They
have their own repo, bug tracker, governance model, and
everything,
right?


Agreed. We have a hard enough time keeping track of our own core
developers.


I don't really think we have a hard time doing this. The only
problem is that we never sat down and actually properly recorded
this in one place.


I was specifically thinking of a way to stay in touch with core
devs, or more specifically a way to send them email. In the past,
before we moved to github, I took it upon myself to find email
addresses (current or not) for all core devs, and I gave up without
much success.

I agree that we could probably come up with a list of names for
people who have been given the "core dev" status.

For our core devs, can't we just say that the CPython core
devs are
those with commit bits on the CPython repo? I realize that will
eliminate some people who have been core developers and
never moved to
github, but if they bring it to our attention, we can add
them easily
enough.

As discussed before, being a core developer is a status you
gain and never lose. There is a clear difference between have
commit rights to the (current) repo and this status.


Agreed. Again, this was in the (poorly conveyed) context of getting
email addresses for them, or at least being able to contact them.

Eric

___
python-committers mailing list
python-committers@python.org <mailto:python-committers@python.org>
https://mail.python.org/mailman/listinfo/python-committers
<https://mail.python.org/mailman/listinfo/python-committers>
Code of Conduct: https://www.python.org/psf/codeofconduct/
<https://www.python.org/psf/codeofconduct/>



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 Jython, IronPython, PyPy,
     Stackless, etc


Hmm, I don't think it is should be our (CPython) responsibility to
keep track and maintain the list of the core devs of alternate Python
implementations. Don't they have their own community / website? They
have their own repo, bug tracker, governance model, and everything,
right?


Agreed. We have a hard enough time keeping track of our own core
developers.


I don't really think we have a hard time doing this. The only
problem is that we never sat down and actually properly recorded
this in one place.


I was specifically thinking of a way to stay in touch with core devs, or 
more specifically a way to send them email. In the past, before we moved 
to github, I took it upon myself to find email addresses (current or 
not) for all core devs, and I gave up without much success.


I agree that we could probably come up with a list of names for people 
who have been given the "core dev" status.



For our core devs, can't we just say that the CPython core devs are
those with commit bits on the CPython repo? I realize that will
eliminate some people who have been core developers and never moved to
github, but if they bring it to our attention, we can add them easily
enough.

As discussed before, being a core developer is a status you
gain and never lose. There is a clear difference between have
commit rights to the (current) repo and this status.


Agreed. Again, this was in the (poorly conveyed) context of getting 
email addresses for them, or at least being able to contact them.


Eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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) responsibility to keep 
track and maintain the list of the core devs of alternate Python 
implementations. Don't they have their own community / website? They 
have their own repo, bug tracker, governance model, and everything, right?


Agreed. We have a hard enough time keeping track of our own core developers.

For our core devs, can't we just say that the CPython core devs are 
those with commit bits on the CPython repo? I realize that will 
eliminate some people who have been core developers and never moved to 
github, but if they bring it to our attention, we can add them easily 
enough.


Eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] An alternative governance model

[Eric V. Smith]

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 Council of Advisors that 
helps the BDFL in various capacities, with additional responsibilities.  I also 
have someone specific in mind for the NBDFL, but you’ll have to read on for the 
big reveal.


I've come to this same conclusion. I think Brett would be a good choice, 
and I'd support him, but I think the more important part is that it be a 
single person.


And I think the succession plan is important, too. I think Łukasz was 
alluding to this earlier (or maybe I'm projecting): who's to say that 
the next BDFL is legitimate? If we put together a plan, and Guido 
blesses it, that makes the plan legitimate, and then the plan gets 
executed and makes NBDFL legitimate.


Eric



Why keep a singular BDFL?  I think it’s clear that no one can completely 
replace Guido, and neither should we try, nor do we need to.  The discussion to 
date has explored refactoring many of the roles that the BDFL has, and that’s 
all excellent, especially to reduce the burden and burnout factor of the NBDFL. 
 But I think having a singular BDFL making the tough decisions, with the 
support and help of the community, is in the best interests of Python over the 
long term.

A singular BDFL provides clear leadership.  With a council of elders, it will 
be more difficult to communicate both to the Python community, and to the 
larger, more peripheral user base, that any particular individual has the 
authority to make decisions.  Regardless of size, there would ultimately be 
some one person communicating any council decision.  There will inevitably be 
ambiguity as to the authority of said decision.  How will folks, especially on 
the periphery, know that Alice Jones or Bob Smith are members of the council 
and can speak authoritatively on decisions for the language?  “Bob Smith, on 
Behalf of the GUIDO” is IMHO less obviously and unquestionably authoritative 
than “Alice Jones, BDFL”.

This also comes into play for shutting down discussions early.  With a 
committee, it’s possible that you’ll have some disagreement among the members 
as to whether a discussion is fruitful or not, whether it rehashes settled 
questions, or whether the change fits into the overall direction for Python’s 
evolution.  Alice Jones may say “No, that’s not gonna happen” only to be 
overruled or undermined by Bob Smith’s “That’s a good idea”.

Taken together, these fall under the umbrella of having one voice for the 
decision making process.  It may be possible for consensus within the council 
to come across as a single voice, but I think it will generally be harder.  A 
council also opens the door for more back-channel lobbying of a sympathetic 
member.  Yes, such lobbying is possible with a BDFL, but at least there should 
be less contention.

I also think a council will be much more risk adverse than a singular BDFL, and 
that’s not necessarily a good thing.  While moratoriums and a more conservative 
approach to change may be appropriate at times, I would prefer those to be 
deliberate decisions for a specific purpose, rather than the unintended outcome 
of groupthink or lack of consensus.  A singular BDFL with support from the 
community will have more authority to make decisions which probably will never 
be universally accepted, and much less prone to vapor lock due to lack of 
consensus or internal bickering.

I hope Guido won’t mind me relating a comment of his that has really resonated 
with me over the last few days, and for which I think a singular BDFL will be 
much more adept at communicating and shepherding.  The question for any new 
leader is:

What is your vision for Python?

This question keeps coming to mind as I think about how the evolution of the 
language will be governed over the next few years or decades.  Yes, Python is a 
mature language, but it’s far from stagnant.  Guido always had a very clear 
vision of what Python should be, where it should go, and how new proposed 
features (or other changes to the Python ecosystem) fit into that vision, even 
if he didn’t or couldn’t always clearly articulate them.  The NBDFL will 
necessarily have a different vision than Guido, and I think even he would agree 
that that’s okay!  A strong vision is better than no vision.  Python must 
continue to grow and evolve if it is to stay relevant in a rapidly change 
technology environment.  As an almost 30 year old language, Python is already 
facing challenges; how will that vision address those challenges, even if to 
explicitly choose the status quo?

Will a council be able to articular, express, communicate, adapt, and follow 
through on that vision?  Will a council be able to evaluate a proposed change 
as it supports or detracts from that vision? 

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

[Eric V. Smith]

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 weeks ago, I am aware of only two
> noteworthy regressions that have been identified and now fixed. Since
> the issues for both have the potential to impact some (but small)
> subsets of 3.7.0 users and the fixes for both are straightforward and
> appear to be low-risk, I am planning to cherry-pick the fixes for them
> into 3.7.0 final without either another release candidate cycle or
> waiting for 3.7.1. There may be some doc fixes that get cherry-picked
> as well. At the moment, there are no plans for any bug cherry-picks for
> 3.6.6 final.
> 
> As you know, a new feature release is a big deal and something for all
> of us to be proud of.  A new feature release also has various, mostly
> minor, impacts to lots of different parts of our development
> infrastructure: to multiple branches of the cpython repo, to
> documentation builds, to different parts of the python.org web site,
> etc. You will start to see some of the changes roll out over the next 24
> to 36 hours and it may take some time until everything is in place.
> So please be patient until the official release announcement goes out
> before reporting release-related issues. Also be advised that over the
> same period, there may be a few brief periods where commit access to
> various cpython branches is blocked in order to do the necessary
> release engineering. If you run into this, for example when trying to
> merge a PR, please try again in a few hours.
> 
> Thanks and more later!
> 
> https://bugs.python.org/issue33851
> https://bugs.python.org/issue33932
> 
> --
>  Ned Deily
>  n...@python.org -- []
> 
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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?
> 
> Correct. 'backport 3.7' == backport into 3.7.1.  I have done this several 
> times already.
> 
>> 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.
> 
> We no longer embargo an x.y branch during the release process, which is much 
> nicer.  If you wanted something in 3.7.0 you would have to mark as release 
> blocker and be very persuasive that he should cherry-pick into the 3.7.0 
> release branch.
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Missing In Action

[Eric V. Smith]

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 leaving people on b.p.o who 
have gone dormant with triage privileges as well? It's much less 
important, but if they haven't contributed in a while they probably are 
not up to sped with triage practices and thus might do something wrong 
by accident.


I think disabling their access is a good idea from an infosec 
perspective. It's not like it's onerous to re-enable them if they 
express any renewed interest.


Eric



On Sun, 17 Jun 2018 at 14:38 Jack Jansen > wrote:


I think I am one of those core developers who hasn’t committed
anything in ages (even though I do have a git account and am
somewhat following what goes on), but the term missing in action may
be a bit too loaded….

How about “missing in inaction”?

:-)

Jack



On  16-Jun-2018, at 02:03 , Victor Stinner mailto:vstin...@redhat.com>> wrote:

"Missing In Action"

Oh. After I sent my email, I checked the translation of "Missing In
Action". It means more or less "lost", but it seems to be commonly
associated to war:

https://en.wikipedia.org/wiki/Missing_in_action
"a casualty classification assigned to combatants, military chaplains,
combat medics, and prisoners of war who are reported missing during
wartime or ceasefire"

I don't recall where I heard the expression, but I didn't mean that
inactive developers are dead :-) I'm quite sure that there is life
after Python. Right?

Victor
___
python-committers mailing list
python-committers@python.org 
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


--

Jack Jansen, mailto:jack.jan...@cwi.nl>>,
http://www.cwi.nl/~jack 

If I can't dance I don't want to be part of your revolution -- Emma
Goldman




___
python-committers mailing list
python-committers@python.org 
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

That's very helpful, thanks. The issue was that I wasn't logged on to 
Travis. I didn't know that was a thing.


I'll check and see if this info is in the devguide.

Eric


On 5/15/18 12:20 PM, Alex Gaynor wrote:
FWIW, attached is an image pointing out the re-run button. If 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 <e...@trueblade.com 
<mailto:e...@trueblade.com>> wrote:


Thanks. You mean close and re-open the bpo issue?

In the past I saw a Travis "re-run" button, but now I don't. I
expected
to see it on the Travis page, but last night I only saw a "More
options"
menu and no "re-run". The next time something fails I'll 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 <e...@trueblade.com
<mailto:e...@trueblade.com>
> <mailto:e...@trueblade.com <mailto:e...@trueblade.com>>> wrote:
>
> 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 — Waiting for status to be reported".
> There's no
> obvious way to get it to actually report the status, or to
restart.
> There is no "Details" button listed on the PR page.
>
> For Travis-CI, Miss Isslington sent me an email that says
"Backport
> status check is done, and it's a failure ❌ ." The Travis-CI
log file
> ends with a timeout:
>
>
 ==
> FAIL: test_stdin_broken_pipe
>  (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
>
 --
> Traceback (most recent call last):
>File
>
 
"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",
>
> line 214, in test_stdin_broken_pipe
>  self.loop.run_until_complete, coro)
> AssertionError: (,  'ConnectionResetError'>) not raised by run_until_complete
>
 --
>
> I'm sure this is all due to the heavy load the systems are
under. I
> can't find a way to kick both of these off again. I couldn't
find
> anything in the devguide, but if I missed it please let me know.
>
> Thanks.
> Eric
> ___
> python-committers mailing list
> python-committers@python.org
<mailto:python-committers@python.org>
<mailto:python-committers@python.org
<mailto:python-committers@python.org>>
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org <mailto:python-committers@python.org>
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/



--
"I disapprove of what you say, but I will defend to the death your 
right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)

"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

Thanks. You mean close and re-open the bpo issue?

In the past I saw a Travis "re-run" button, but now I don't. I expected 
to see it on the Travis page, but last night I only saw a "More options" 
menu and no "re-run". The next time something fails I'll 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 <e...@trueblade.com
<mailto:e...@trueblade.com>> wrote:

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 — Waiting for status to be reported".
There's no
obvious way to get it to actually report the status, or to restart.
There is no "Details" button listed on the PR page.

For Travis-CI, Miss Isslington sent me an email that says "Backport
status check is done, and it's a failure ❌ ." The Travis-CI log file
ends with a timeout:

==
FAIL: test_stdin_broken_pipe
(test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
--
Traceback (most recent call last):
   File

"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",

line 214, in test_stdin_broken_pipe
 self.loop.run_until_complete, coro)
AssertionError: (, ) not raised by run_until_complete
--

I'm sure this is all due to the heavy load the systems are under. I
can't find a way to kick both of these off again. I couldn't find
anything in the devguide, but if I missed it please let me know.

Thanks.
Eric
___
python-committers mailing list
python-committers@python.org <mailto:python-committers@python.org>
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] AppVeyor and Travis-CI

[Eric V. Smith]

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 — Waiting for status to be reported". There's no 
obvious way to get it to actually report the status, or to restart. 
There is no "Details" button listed on the PR page.


For Travis-CI, Miss Isslington sent me an email that says "Backport 
status check is done, and it's a failure ❌ ." The Travis-CI log file 
ends with a timeout:


==
FAIL: test_stdin_broken_pipe 
(test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)

--
Traceback (most recent call last):
  File 
"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py", 
line 214, in test_stdin_broken_pipe

self.loop.run_until_complete, coro)
AssertionError: (, 'ConnectionResetError'>) not raised by run_until_complete

--

I'm sure this is all due to the heavy load the systems are under. I 
can't find a way to kick both of these off again. I couldn't find 
anything in the devguide, but if I missed it please let me know.


Thanks.
Eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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.6 and 3.7.  Let’s also give him all the 
support he needs to make 3.7 the best version yet.

As is tradition, Python release managers serve for two consecutive releases, 
and so with the 3.7 release branch about to be made, it’s time to announce our 
release manager for Python 3.8 and 3.9.

By unanimous and enthusiastic consent from the Python Secret Underground (PSU, 
which emphatically does not exist), the Python Cabal of Former and Current 
Release Managers, Cardinal Ximénez, and of course the BDFL, please welcome your 
next release manager…

Łukasz Langa!

And also, happy 24th anniversary to Guido’s Python 1.0.0 announcement[1].  It’s 
been a fun and incredible ride, and I firmly believe that Python’s best days 
are ahead of us.

Enjoy,
-Barry

[1] 
https://groups.google.com/forum/?hl=en#!original/comp.lang.misc/_QUzdEGFwCo/KIFdu0-Dv7sJ



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. 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 Nathaniel in the
beginning).


+1. I actually thought he was a committer already.

Eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

Thanks, Alex. I'll check that next time. And thanks for kicking it off 
for me.


Eric.

On 1/6/2018 11:45 AM, Alex Gaynor wrote:
If you look at the travis-ui, do you see little "restart" arrows 
(example attached)? Those are what do it -- I went ahead and restarted 
the failed job on this one.


Alex

On Sat, Jan 6, 2018 at 11:43 AM, Eric V. Smith <e...@trueblade.com 
<mailto:e...@trueblade.com>> 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 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-running it first.

Thanks.
Eric.
___
python-committers mailing list
python-committers@python.org <mailto:python-committers@python.org>
https://mail.python.org/mailman/listinfo/python-committers
<https://mail.python.org/mailman/listinfo/python-committers>
Code of Conduct: https://www.python.org/psf/codeofconduct/
<https://www.python.org/psf/codeofconduct/>




--
"I disapprove of what you say, but I will defend to the death your right 
to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)

"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

+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 sole or primary author on several PEPs (526, 544, 560, 562), is 
> co-author on several more (483, 561) and has been acknowledged in yet others 
> (557, 563).
> 
> He is responsible for at least 16 commits in master.
> 
> I have worked with him for a long time on typing.py and on mypy (where he is 
> a core dev) and I can vouch for him completely.
> 
> -- 
> --Guido van Rossum (python.org/~guido)
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 very effective place to have
discussions (e.g. most mypy design work is done there). Though I agree
that GitHub currently doesn't scale to the size of CPython unless you
work hard on setting up filtering (which *is* possible, just done very
differently).


I grant that it's an uphill battle. But even github has a separate issue 
tracker, we're just not using it. So even github black belts should be 
familiar with the concept of an issue tracker being used for a different 
purpose than code reviews are.


Eric.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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
having major decisions just in Github PRs?

2) How can we retain enough information on BPO to keep it useful as
research database for past decisions?


It's OK to have the discussions on GitHub, but one of the
responsibilities of reviewers is to ensure that significant design
decisions are summarised on the related tracker issue for future
reference.


I don't think that's a good idea, since the core devs then
have to check what's good discussion to have on Github PRs
and what not.

IMO, it's much easier for everyone to just always point people
to BPO for discussions and keep PRs reserved for code reviews.


I agree with Mark-Andre here.  It will take effort on our part to
make our culture be "discuss on BPO", but it will produce a much
superior history to what github PRs produce, so I think it is worth it.


I agree with David and MAL. github PR's should replace Rietveld for code 
reviews, and should not replace BPO for discussions.


Eric.

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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
release (which is the whole point).  If we're talking something past the
2 years timerange, you can't just impose that on all core developers, so
you need a subgroup of maintainers dedicated to that LTS release.


Channeling Nick, I'd say that LTS support should come from commercial 
third parties, such as OS vendors. I agree with Antoine: it's not 
something we want to impose on the core devs. How much fun is 2.7 
maintenance?


Eric.


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] autoconf 2.70

[Eric V. Smith]

> 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 that policy even if we sometimes screw up.

Agreed. 

> (I thought we had actually introduced a check for it in the Makefile, but
> I guess not...that would make it inconvenient for someone to intentionally
> use a different version for a custom build.)

Would it be possible to add a commit hook? It seems like that would be the 
correct place to catch it. 

Eric. 
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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
angwe...@126.com


I didn't see a request, so I just subscribed him.


Welcome aboard Xiang!


Yes, welcome!

Eric.

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[Eric V. Smith]

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 when I get back. 

--
Eric.

Begin forwarded message:

 From: Vinay Sajip vinay_sa...@yahoo.co.uk
 Date: April 15, 2014 at 6:29:11 AM EDT
 To: Eric Smith e...@trueblade.com
 Subject: CPython repository - changeset not merged into default from 3.4?
 Reply-To: Vinay Sajip vinay_sa...@yahoo.co.uk
 
 Hi Eric,
 
 I made some changes in the Python 3.4 branch which I want to merge into 
 default. I noticed that you made some changes in 3.4 in changeset 
 16efa8d27e4c which don't appear in default - is this intentional? Your 
 changes are lumped in with mine when I try to merge :-(
 
 Regards,
 
 Vinay Sajip
 
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers

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

[Eric V. Smith]

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
 hgaccou...@python.org.

I've added him to python-committers. Welcome, Yury!

Eric.


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

Re: [python-committers] SSH fingerprint

[Eric V. Smith]

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 execution on the buildbots)


 Sure, but it would be better to actually have the fingerprints to avoid
 the MITM attack altogether.

I completely agree. We'll notice the damage is not a great reason to
avoid publishing the fingerprints.

 Can someone log into hg.python.org and get the public keys for the server?

Not me. But from my hosts, I get:
RSA key fingerprint is ec:98:fe:7b:e1:0f:88:c5:93:37:83:64:a4:cc:aa:01.

-- 
Eric.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

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

[Eric V. Smith]

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 g.bra...@gmx.net wrote:
 The SSH key is added; tracker privileges were already given.

 Welcome Serhiy!

 Yes, welcome!

 Serhiy, if you haven't already done so, please subscribe to
 python-committers.
 
 Thanks. My request has been forwarded to the list moderator for approval.

And I approved it. Welcome, Serhiy!

-- 
Eric.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

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

[Eric V. Smith]

+1

--
Eric.

On Dec 24, 2012, at 12:07 PM, Trent Nelson tr...@snakebite.org 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-committers mailing list
 python-committers@python.org
 http://mail.python.org/mailman/listinfo/python-committers
 
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers