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