Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Nick Coghlan
On 25 June 2017 at 16:31, Terry Reedy wrote: >> 25.06.17 06:04, Nick Coghlan пише: >>> All the PRs share an issue number in that case, so Bedevere should be >>> able to pick up that there's a pre-existing NEWS entry (even if it >>> isn't being added by that particular PR). > > You seem to be sugge

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/25/2017 12:30 AM, Serhiy Storchaka wrote: 25.06.17 06:04, Nick Coghlan пише: On 25 June 2017 at 11:56, Terry Reedy wrote: On 6/24/2017 7:48 PM, Brett Cannon wrote: I should also mention that after Larry blows up Misc/NEWS into individual files in about a week I will add a check to Bedeve

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/25/2017 12:19 AM, Serhiy Storchaka wrote: 25.06.17 04:51, Nick Coghlan пише: So count me in as a +1 for standardising on a model where: - client-side core-workflow tools are free to use features from the latest released version of Python - we expect core devs to set up a venv or conda env

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/24/2017 09:14 PM, Serhiy Storchaka wrote: Not only core developers make PRs for CPython. Since all non-trivial changes need to be mentioned in Misc/NEWS, blurb becomes a required tool for all committers. Well, no. *Writing blurb-compatible files* becomes a required step for all committ

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Serhiy Storchaka
25.06.17 06:04, Nick Coghlan пише: On 25 June 2017 at 11:56, Terry Reedy wrote: On 6/24/2017 7:48 PM, Brett Cannon wrote: I should also mention that after Larry blows up Misc/NEWS into individual files in about a week I will add a check to Bedevere for a news file unless the PR is labeled as t

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Serhiy Storchaka
25.06.17 04:51, Nick Coghlan пише: So count me in as a +1 for standardising on a model where: - client-side core-workflow tools are free to use features from the latest released version of Python - we expect core devs to set up a venv or conda env to run those tools if their system Python is too

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Serhiy Storchaka
24.06.17 18:57, Larry Hastings пише: On 06/24/2017 01:53 AM, Antoine Pitrou wrote: Would you like to make it 3.5-compatible? 3.6 is quite young and not all systems have it (e.g. Ubuntu 16.04, which many people use, has 3.5). Well, tbh I think that's a bit silly. First of all, it shouldn't be

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Nick Coghlan
On 25 June 2017 at 11:56, Terry Reedy wrote: > On 6/24/2017 7:48 PM, Brett Cannon wrote: > >> I should also mention that after Larry blows up Misc/NEWS into individual >> files in about a week I will add a check to Bedevere for a news file unless >> the PR is labeled as trivial. > > > And what if

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/24/2017 06:56 PM, Terry Reedy wrote: And what if there isn't? There are sometimes good reasons to have multiple patches on an issue, whereas an issue usually gets only one news item. There's nothing about blurb--or anything else in the workflow IIUC--that says you can't have multiple

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/24/2017 7:48 PM, Brett Cannon wrote: I should also mention that after Larry blows up Misc/NEWS into individual files in about a week I will add a check to Bedevere for a news file unless the PR is labeled as trivial. And what if there isn't? There are sometimes good reasons to have mul

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Nick Coghlan
On 25 June 2017 at 02:10, Antoine Pitrou wrote: > On Sat, 24 Jun 2017 08:57:24 -0700 > Larry Hastings wrote: >> On 06/24/2017 01:53 AM, Antoine Pitrou wrote: >> > Would you like to make it 3.5-compatible? 3.6 is quite young and not >> > all systems have it (e.g. Ubuntu 16.04, which many people u

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Antoine Pitrou
On Sat, 24 Jun 2017 23:48:03 + Brett Cannon wrote: > On Sat, 24 Jun 2017 at 10:07 Antoine Pitrou wrote: > > > > > Larry, > > > > I have just used blurb on https://github.com/python/cpython/pull/2010 > > and it was absolutely painless. Thank you! > > > > One minor thing: `make patchcheck` do

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Brett Cannon
On Sat, 24 Jun 2017 at 10:07 Antoine Pitrou wrote: > > Larry, > > I have just used blurb on https://github.com/python/cpython/pull/2010 > and it was absolutely painless. Thank you! > > One minor thing: `make patchcheck` doesn't know to examine the NEWS.d > directory when checking for NEWS entrie

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/24/2017 10:30 AM, Terry Reedy wrote: Solution: name the file blurb.py and put it in site-packages. This is standard and what is done by all other pip-installs that I have run. Put a copy in /Scripts if you want, but that is really optional and only sometimes effective. Brett redid th

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/24/2017 12:45 PM, Larry Hastings wrote: On 06/24/2017 09:40 AM, Terry Reedy wrote: On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collec

Re: [Python-Dev] For all branches? [was Re: New workflow change: Welcome to blurb]

2017-06-24 Thread Larry Hastings
On 06/24/2017 10:21 AM, Antoine Pitrou wrote: One thing you didn't mention: is the switch on all branches or only master? All active branches: 2.7 3.3 3.4 3.5 3.6 master You should see a Misc/NEWS.d directory on each of those with an up-to-date clone. //arry/ __

[Python-Dev] For all branches? [was Re: New workflow change: Welcome to blurb]

2017-06-24 Thread Antoine Pitrou
One thing you didn't mention: is the switch on all branches or only master? Regards Antoine. On Fri, 23 Jun 2017 20:24:05 -0700 Larry Hastings wrote: > One minor but ongoing problem we've had in CPython core development has > been the mess of updating Misc/NEWS. Day-to-day developers may h

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Brett Cannon
I just pushed blurb 1.0.0.post1 which re-packages everything using flit so there's a blurb.py and an entry point for the `blurb` command. That should meet everyone's needs for launching the tool. On Sat, 24 Jun 2017 at 09:54 Brett Cannon wrote: > On Sat, 24 Jun 2017 at 09:46 Larry Hastings wrot

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Antoine Pitrou
Larry, I have just used blurb on https://github.com/python/cpython/pull/2010 and it was absolutely painless. Thank you! One minor thing: `make patchcheck` doesn't know to examine the NEWS.d directory when checking for NEWS entries. Regards Antoine. On Fri, 23 Jun 2017 20:24:05 -0700 Larry

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Brett Cannon
On Sat, 24 Jun 2017 at 09:46 Larry Hastings wrote: > On 06/24/2017 09:40 AM, Terry Reedy wrote: > > On 6/23/2017 11:24 PM, Larry Hastings wrote: > > > You can install blurb from pip: > > > > % pip3.6 install blurb > > This does not seem to work right. On Windows: > > C:\Users\Terry>py -3 -m

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/24/2017 09:40 AM, Terry Reedy wrote: On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-1.0-py3-none-an

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/23/2017 11:24 PM, Larry Hastings wrote: > You can install blurb from pip: > > % pip3.6 install blurb This does not seem to work right. On Windows: C:\Users\Terry>py -3 -m pip install blurb Collecting blurb Downloading blurb-1.0-py3-none-any.whl Installing collected packages: blurb S

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/23/2017 11:25 PM, Serhiy Storchaka wrote: I have installed it, but how to use it? $ python3 -m pip install --user blurb Collecting blurb Using cached blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 $ python3 -m blurb /usr/bin/python3: No

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Terry Reedy
On 6/24/2017 11:57 AM, Larry Hastings wrote: On 06/24/2017 01:53 AM, Antoine Pitrou wrote: Would you like to make it 3.5-compatible? 3.6 is quite young and not all systems have it (e.g. Ubuntu 16.04, which many people use, has 3.5). Well, tbh I think that's a bit silly. First of all, it shou

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Antoine Pitrou
On Sat, 24 Jun 2017 08:57:24 -0700 Larry Hastings wrote: > On 06/24/2017 01:53 AM, Antoine Pitrou wrote: > > Would you like to make it 3.5-compatible? 3.6 is quite young and not > > all systems have it (e.g. Ubuntu 16.04, which many people use, has 3.5). > > Well, tbh I think that's a bit sill

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/23/2017 10:55 PM, Nick Coghlan wrote: Aye, towncrier and OpenStack's reno were the two main alternatives we looked at in addition to Larry's offer of creating a tool specifically for CPython: https://github.com/python/core-workflow/issues/6 Fun fact: all three tools started at about the s

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Larry Hastings
On 06/24/2017 01:53 AM, Antoine Pitrou wrote: Would you like to make it 3.5-compatible? 3.6 is quite young and not all systems have it (e.g. Ubuntu 16.04, which many people use, has 3.5). Well, tbh I think that's a bit silly. First of all, it shouldn't be installed in your system-wide python

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Serhiy Storchaka
24.06.17 11:53, Antoine Pitrou пише: On Fri, 23 Jun 2017 20:24:05 -0700 Larry Hastings wrote: We've been talking about addressing this for years. Fixing this was one of the goals of the new workflow. And finally, as of right now, the future is here. Ladies and gentlemen, I present: blurb.

Re: [Python-Dev] New workflow change: Welcome to blurb

2017-06-24 Thread Antoine Pitrou
On Fri, 23 Jun 2017 20:24:05 -0700 Larry Hastings wrote: > > We've been talking about addressing this for years. Fixing this was one > of the goals of the new workflow. And finally, as of right now, the > future is here. Ladies and gentlemen, I present: blurb. > > https://github.com/pyt