<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<p dir="auto" style="text-align:left; margin-top:25px; margin-bottom:25px; font-family:sans-serif; font-size:11pt; color:black; background-color:white">
help<br>
</p>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Python-Dev <python-dev-bounces+www.2849007069=outlook.com@python.org> on behalf of python-dev-request@python.org <python-dev-request@python.org><br>
<b>Sent:</b> Wednesday, February 15, 2017 1:00:05 AM<br>
<b>To:</b> python-dev@python.org<br>
<b>Subject:</b> Python-Dev Digest, Vol 163, Issue 20</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send Python-Dev mailing list submissions to<br>
python-dev@python.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
python-dev-request@python.org<br>
<br>
You can reach the person managing the list at<br>
python-dev-owner@python.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Python-Dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [Python-checkins] [python/cpython] 4538dd: Fix bpo-29528<br>
Use a secure variable to stop spam (... (Brett Cannon)<br>
2. Re: [Python-checkins] [python/cpython] 4538dd: Fix bpo-29528<br>
Use a secure variable to stop spam (... (Berker Peksa?)<br>
3. Heads-up, I've rejoined (Eric S. Raymond)<br>
4. Update on labels to be used on GitHub (Brett Cannon)<br>
5. Re: Update on labels to be used on GitHub (Victor Stinner)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 13 Feb 2017 17:54:51 +0000<br>
From: Brett Cannon <brett@snarky.ca><br>
To: python-dev@python.org, python-checkins@python.org<br>
Cc: amk@amk.ca<br>
Subject: Re: [Python-Dev] [Python-checkins] [python/cpython] 4538dd:<br>
Fix bpo-29528 Use a secure variable to stop spam (...<br>
Message-ID:<br>
<CAP1=2W5ijfhoYPk7JdVKdyDBfEzQWK09rMw-FRPd+pm0yr0LiQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Mon, 13 Feb 2017 at 07:10 Barry Warsaw <barry@python.org> wrote:<br>
<br>
> On Feb 11, 2017, at 08:11 PM, Andrew M. Kuchling wrote:<br>
><br>
> >Are we planning to include the diffs in python-checkins e-mail, or are<br>
> >they gone for good?<br>
> ><br>
> >(While they made the list's messages and digests larger, I liked<br>
> >having the diffs because you could page through them to see what<br>
> >changes were made without having to go through to another site.)<br>
><br>
> Yep, this was recently discussed and I think the plan is to bring them back<br>
> for python-checkins, but that it's not possible to enable them on PRs due<br>
> to<br>
> GH limitations.<br>
><br>
<br>
Serhiy asked about it and I said that the email integration we are using<br>
from GitHub doesn't allow for customizing the email it sends out beyond how<br>
is listed in the From line. If people find a different integration that<br>
they want to use for sending email then that can be set up.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.python.org/pipermail/python-dev/attachments/20170213/cc0a0a6f/attachment-0001.html">http://mail.python.org/pipermail/python-dev/attachments/20170213/cc0a0a6f/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 13 Feb 2017 21:25:34 +0300<br>
From: Berker Peksa? <berker.peksag@gmail.com><br>
To: Python Dev <python-dev@python.org>, python-checkins@python.org<br>
Subject: Re: [Python-Dev] [Python-checkins] [python/cpython] 4538dd:<br>
Fix bpo-29528 Use a secure variable to stop spam (...<br>
Message-ID:<br>
<CAF4280K=N__3jNAjeBDNO5F8pYkkcg6DeOFSkGy0iKZg01JOsg@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
--Berker<br>
<br>
<br>
On Mon, Feb 13, 2017 at 8:54 PM, Brett Cannon <brett@snarky.ca> wrote:<br>
><br>
><br>
> On Mon, 13 Feb 2017 at 07:10 Barry Warsaw <barry@python.org> wrote:<br>
>><br>
>> On Feb 11, 2017, at 08:11 PM, Andrew M. Kuchling wrote:<br>
>><br>
>> >Are we planning to include the diffs in python-checkins e-mail, or are<br>
>> >they gone for good?<br>
>> ><br>
>> >(While they made the list's messages and digests larger, I liked<br>
>> >having the diffs because you could page through them to see what<br>
>> >changes were made without having to go through to another site.)<br>
>><br>
>> Yep, this was recently discussed and I think the plan is to bring them<br>
>> back<br>
>> for python-checkins, but that it's not possible to enable them on PRs due<br>
>> to<br>
>> GH limitations.<br>
><br>
><br>
> Serhiy asked about it and I said that the email integration we are using<br>
> from GitHub doesn't allow for customizing the email it sends out beyond how<br>
> is listed in the From line. If people find a different integration that they<br>
> want to use for sending email then that can be set up.<br>
<br>
I wrote a webhook that includes diffs: An example output can be seen<br>
at <a href="https://github.com/python/core-workflow/issues/24#issuecomment-279162079">
https://github.com/python/core-workflow/issues/24#issuecomment-279162079</a><br>
Since it listens all 'push' events, it's possible to catch all commits<br>
and send them to python-checkins.<br>
<br>
--Berker<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 13 Feb 2017 14:05:55 -0500 (EST)<br>
From: esr@thyrsus.com (Eric S. Raymond)<br>
To: python-dev@python.org<br>
Subject: [Python-Dev] Heads-up, I've rejoined<br>
Message-ID: <20170213190555.7073113A019A@snark.thyrsus.com><br>
<br>
Some of the older Pythonistas will remember my previous time on this<br>
list, and possibly that I faded away quietly under time pressure from<br>
other projects and the whole being-famous nonsense.<br>
<br>
I'm back, for now primarily to listen. I have some questions about the<br>
future direction of Python which I'll bring up when I have time for<br>
the vigorous discussion that will certainly ensue.<br>
--<br>
>>esr>><br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 13 Feb 2017 20:08:55 +0000<br>
From: Brett Cannon <brett@python.org><br>
To: python-dev <python-dev@python.org><br>
Subject: [Python-Dev] Update on labels to be used on GitHub<br>
Message-ID:<br>
<CAP1=2W7WO5LXrE+V9tkxQPFo99fryV6+2U8SK=5by529kaLa6Q@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
We now have two sets of labels for representing cherry-picking statuses:<br>
"backport to N.M" and "cherry-pick for N.M". The former are to help keep<br>
track of what branches a PR should be cherry-picked *to* and can be removed<br>
once the PR for a cherry-pick has been created (you can add a comment like<br>
"cherry-picked from GH-NN" to make the link between the PRs)*.* The latter<br>
labels are to signify that the PR is a cherry-pick *itself*.<br>
<br>
As with all aspects of the new GitHub workflow, we will give this a solid<br>
try for about a month and then we can re-evaluate whether we like this<br>
approach or want a more traditional prefix format in the title to represent<br>
the same thing.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.python.org/pipermail/python-dev/attachments/20170213/225558f5/attachment-0001.html">http://mail.python.org/pipermail/python-dev/attachments/20170213/225558f5/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 13 Feb 2017 23:35:58 +0100<br>
From: Victor Stinner <victor.stinner@gmail.com><br>
To: Brett Cannon <brett@python.org><br>
Cc: python-dev <python-dev@python.org><br>
Subject: Re: [Python-Dev] Update on labels to be used on GitHub<br>
Message-ID:<br>
<CAMpsgwY6d8MfauH7-SgwmGFQXEfuS5kVa0aE4BuSxRLsdcQEBQ@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
2017-02-13 21:08 GMT+01:00 Brett Cannon <brett@python.org>:<br>
> We now have two sets of labels for representing cherry-picking statuses:<br>
> "backport to N.M" and "cherry-pick for N.M". The former are to help keep<br>
> track of what branches a PR should be cherry-picked to and can be removed<br>
> once the PR for a cherry-pick has been created (you can add a comment like<br>
> "cherry-picked from GH-NN" to make the link between the PRs).<br>
<br>
The first time I looked at the "backport to 3.6" flag, I understood<br>
that the change was written on the 3.6 branch and asked to rebase the<br>
change on 3.6. If I was confused, I'm sure that someone else will be<br>
confused as well :-)<br>
<br>
What do you think of renaming the label to "need 3.6 backport" (or<br>
"need backport to 3.6")?<br>
<br>
Victor<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
Python-Dev@python.org<br>
<a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Python-Dev Digest, Vol 163, Issue 20<br>
*******************************************<br>
</div>
</span></font>
</body>
</html>