Re: [Python-Dev] New workflow change: Welcome to blurb
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/python/core-workflow/tree/master/blurb "blurb's only dependency is Python 3.6+." 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). Regards Antoine. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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. https://github.com/python/core-workflow/tree/master/blurb "blurb's only dependency is Python 3.6+." 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). +1 ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 python3 interpreter. Second, I assumed core devs were compiling their own Python interpreters locally in their account--in no small part so they can install any packages they want. And finally, you're asking me to give up f-strings. If someone else wants to send me a PR getting it to work on 3.5, I'd look at it. I'm guessing it's really just f-strings but I can't say for sure what else is a 3.6 dependency. //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 same time, at least according to publicly visible commits. Towncrier started December 2015, reno in August 2015, and my first commits to "mergenews" (which eventually became blurb) were in September of 2015. We'd actually been discussing it on bpo since at least September 2013: https://bugs.python.org/issue18967 //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 silly. First of all, it shouldn't be > installed in your system-wide python3 interpreter. Well, you can always create a venv using the system python3. Nowadays, to be honest, I use conda and Anaconda a lot, so I can very quickly create a local Python 3.6 environment on my work machine, even if my OS doesn't provide a Python 3.6. I'm just not sure everyone has the same habits as me, though I'm all for more core developers adopting conda :-) > Second, I assumed > core devs were compiling their own Python interpreters locally in their > account--in no small part so they can install any packages they want. I used to do that, but in the end it feels too confusing and cumbersome. So I don't install self-compiled Pythons anymore. Of course, since you are doing the work, it's ok for me if you don't want to make blurb Python 3.5-compatible. I'm just pointing out that it would ideally be better if it were :-) Regards Antoine. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 shouldn't be installed in your system-wide python3 interpreter. Second, I assumed core devs were compiling their own Python interpreters locally in their account--in no small part so they can install any packages they want. And finally, you're asking me to give up f-strings. If someone else wants to send me a PR getting it to work on 3.5, I'd look at it. I'm guessing it's really just f-strings but I can't say for sure what else is a 3.6 dependency. I believe cherry-picker also requires 3.6, for the same reason. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 module named blurb It's on your path. Just run % blurb from inside a CPython repo. I'm amazed that your first thought was "python -m blurb". //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. tjr ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not a package or a module. It should be a command on your path. TBH I don't know if installation of a command-line tool like that works on Windows. The tool itself was ported to Windows by Zach at the PyCon core dev sprints last month, though that predates the PyPI work, and in any case I could have broken the Windows support since then. Unfortunately I'm no longer a qualified Windows developer, so if it doesn't work on Windows I fear someone will have to send me a PR. //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 pip install blurb > Collecting blurb > Downloading blurb-1.0-py3-none-any.whl > Installing collected packages: blurb > Successfully installed blurb-1.0 > > Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' > directory but neither blurb.py nor 'blurb/' is present. So the following > are to be expected. > > C:\Users\Terry>py -3 -m blurb > C:\Programs\Python36\python.exe: No module named blurb > > > py -3 > >>> import blurb > ... > ModuleNotFoundError: No module named 'blurb' > > Serhiy reported a similar problem on, I presume, some flavor of Linux. > > > I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not > a package or a module. It should be a command on your path. > > TBH I don't know if installation of a command-line tool like that works on > Windows. The tool itself was ported to Windows by Zach at the PyCon core > dev sprints last month, though that predates the PyPI work, and in any case > I could have broken the Windows support since then. Unfortunately I'm no > longer a qualified Windows developer, so if it doesn't work on Windows I > fear someone will have to send me a PR. > One of the great perks of `python3 -m blurb` is it avoids needing to care about your PATH on any platform. Anyway, the next release of blurb -- whether that's 1.0.0.post1 or a bigger release -- will have a blurb.py as well as the entry point giving people the `blurb` command. And people can also use pipsi if they want to install blurb as more of a self-contained command-line app (at least on UNIX; don't know about its support on Windows). ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 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 have a > conflict if they lose a push race, which means a little editing. You'll > have a similar, if slightly worse, problem when cherry-picking a fix > between versions. Worst of all used to be the manual merges necessary > after cutting a release--this was the bane of a CPython release > manager's existence. (Though the new git-based workflow may have > obviated the worst of this.) > > The real problem is that we have one central file that everybody > continually edits in a haphazard way. We aren't actually editing the > same information, we aren't actually changing the same lines. But our > revision control systems and diff algorithms don't understand the > structure of Misc/NEWS and so they get confused. And for what? It's not > like there's a tremendous benefit to having this central file everyone's > fighting over. > > 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/python/core-workflow/tree/master/blurb > > > blurb is an interactive command-line tool that helps you write Misc/NEWS > entries. You simply run blurb from anywhere inside a CPython repo. > blurb runs an editor for you with a template open. You fill in these > three pieces of information: > > * the bugs.python.org or "bpo" issue number, > * what "section" of Misc/NEWS this entry should go in (by uncommenting > the correct line), and > * the text of the Misc/NEWS entry, in ReST format. > > You save and exit and you're done. blurb even stages the Misc/NEWS > entry in git for you! > > > Behind the scenes, blurb writes your information here: > > Misc/NEWS.d/next// > > The "" is the name of the section in Misc/NEWS where your > entry should go. contains the current date and time, the bpo > number, and a nonce to prevent collisions. > > These "next" files get merged together into a single aggregate .rst file > by the release manager when cutting a release (using "blurb release"). > One nice feature of this approach: when you cherry-pick a change, its > Misc/NEWS entry in "next" gets cherry-picked along with it. > > > One important change: Misc/NEWS will no longer be checked in. It'll > still be present in CPython tarballs; it will be generated by the > release manager as part of cutting a release. But as a repository of > information, it's been superseded by the various blurb data files. And > by regenerating it from data files, we ensure that we'll never ever have > a Misc/NEWS conflict ever again! > > The plan is to leave Misc/NEWS in the CPython repo for maybe another > week, to let the current crop of PRs get merged. But new work should > switch to using blurb immediately. > > > You can install blurb from pip: > > % pip3.6 install blurb > > In fact--please do! > > > //arry/ > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 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 >> Collecting blurb >> Downloading blurb-1.0-py3-none-any.whl >> Installing collected packages: blurb >> Successfully installed blurb-1.0 >> >> Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' >> directory but neither blurb.py nor 'blurb/' is present. So the following >> are to be expected. >> >> C:\Users\Terry>py -3 -m blurb >> C:\Programs\Python36\python.exe: No module named blurb >> >> > py -3 >> >>> import blurb >> ... >> ModuleNotFoundError: No module named 'blurb' >> >> Serhiy reported a similar problem on, I presume, some flavor of Linux. >> >> >> I replied to Serhiy; it's just "blurb", it's a command-line tool, it's >> not a package or a module. It should be a command on your path. >> >> TBH I don't know if installation of a command-line tool like that works >> on Windows. The tool itself was ported to Windows by Zach at the PyCon >> core dev sprints last month, though that predates the PyPI work, and in any >> case I could have broken the Windows support since then. Unfortunately I'm >> no longer a qualified Windows developer, so if it doesn't work on Windows I >> fear someone will have to send me a PR. >> > > One of the great perks of `python3 -m blurb` is it avoids needing to care > about your PATH on any platform. > > Anyway, the next release of blurb -- whether that's 1.0.0.post1 or a > bigger release -- will have a blurb.py as well as the entry point giving > people the `blurb` command. And people can also use pipsi if they want to > install blurb as more of a self-contained command-line app (at least on > UNIX; don't know about its support on Windows). > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] For all branches? [was Re: New workflow change: Welcome to blurb]
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 have a > conflict if they lose a push race, which means a little editing. You'll > have a similar, if slightly worse, problem when cherry-picking a fix > between versions. Worst of all used to be the manual merges necessary > after cutting a release--this was the bane of a CPython release > manager's existence. (Though the new git-based workflow may have > obviated the worst of this.) > > The real problem is that we have one central file that everybody > continually edits in a haphazard way. We aren't actually editing the > same information, we aren't actually changing the same lines. But our > revision control systems and diff algorithms don't understand the > structure of Misc/NEWS and so they get confused. And for what? It's not > like there's a tremendous benefit to having this central file everyone's > fighting over. > > 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/python/core-workflow/tree/master/blurb > > > blurb is an interactive command-line tool that helps you write Misc/NEWS > entries. You simply run blurb from anywhere inside a CPython repo. > blurb runs an editor for you with a template open. You fill in these > three pieces of information: > > * the bugs.python.org or "bpo" issue number, > * what "section" of Misc/NEWS this entry should go in (by uncommenting > the correct line), and > * the text of the Misc/NEWS entry, in ReST format. > > You save and exit and you're done. blurb even stages the Misc/NEWS > entry in git for you! > > > Behind the scenes, blurb writes your information here: > > Misc/NEWS.d/next// > > The "" is the name of the section in Misc/NEWS where your > entry should go. contains the current date and time, the bpo > number, and a nonce to prevent collisions. > > These "next" files get merged together into a single aggregate .rst file > by the release manager when cutting a release (using "blurb release"). > One nice feature of this approach: when you cherry-pick a change, its > Misc/NEWS entry in "next" gets cherry-picked along with it. > > > One important change: Misc/NEWS will no longer be checked in. It'll > still be present in CPython tarballs; it will be generated by the > release manager as part of cutting a release. But as a repository of > information, it's been superseded by the various blurb data files. And > by regenerating it from data files, we ensure that we'll never ever have > a Misc/NEWS conflict ever again! > > The plan is to leave Misc/NEWS in the CPython repo for maybe another > week, to let the current crop of PRs get merged. But new work should > switch to using blurb immediately. > > > You can install blurb from pip: > > % pip3.6 install blurb > > In fact--please do! > > > //arry/ > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] For all branches? [was Re: New workflow change: Welcome to blurb]
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 mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 Collecting blurb Downloading blurb-1.0-py3-none-any.whl Installing collected packages: blurb Successfully installed blurb-1.0 Explorer shows that 3.6 site-packages has a 'blurb-1.0.dist-info' directory but neither blurb.py nor 'blurb/' is present. So the following are to be expected. C:\Users\Terry>py -3 -m blurb C:\Programs\Python36\python.exe: No module named blurb > py -3 >>> import blurb ... ModuleNotFoundError: No module named 'blurb' Serhiy reported a similar problem on, I presume, some flavor of Linux. I replied to Serhiy; it's just "blurb", it's a command-line tool, it's not a package or a module. It should be a command on your path. The reason I tried " -m blurb" is because that is the standard and recommended way to run installed scripts on Windows. That is how I run pip and cherry_picker, for instance. I found 'blurb' in <36dir>/Scripts/. The name and location are errors. 1. On Windows, python files need the .py extension. 2. That directory is not currently on the path on my machine. I believe it once was, but installing 3.5.3 replaced it with the 3.5 /Scripts. On Windows, 3rd party installers must not presume that any /Scripts directory is on the path. By default, none are. 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. TBH I don't know if installation of a command-line tool like that works on Windows. The tool itself was ported to Windows by Zach at the PyCon core dev sprints last month, though that predates the PyPI work, and in any case I could have broken the Windows support since then. Unfortunately I'm no longer a qualified Windows developer, so if it doesn't work on Windows I fear someone will have to send me a PR. I only know what the end result should be. Pip-installed Cherry_picker works on Windows, so copy from the spec files for that, or ask whoever wrote the pip-upload. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb
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 the installer with "flit" and pushed, and he says you should now be able to run blurb via "python3 -m blurb". Please update blurb (via pip3.6) and let us know if it now works for you on Windows. Cheers, //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 entries. > I opened https://bugs.python.org/issue30750 for that if someone wants to make the change. 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. -Brett > > 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 have a > > conflict if they lose a push race, which means a little editing. You'll > > have a similar, if slightly worse, problem when cherry-picking a fix > > between versions. Worst of all used to be the manual merges necessary > > after cutting a release--this was the bane of a CPython release > > manager's existence. (Though the new git-based workflow may have > > obviated the worst of this.) > > > > The real problem is that we have one central file that everybody > > continually edits in a haphazard way. We aren't actually editing the > > same information, we aren't actually changing the same lines. But our > > revision control systems and diff algorithms don't understand the > > structure of Misc/NEWS and so they get confused. And for what? It's not > > like there's a tremendous benefit to having this central file everyone's > > fighting over. > > > > 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/python/core-workflow/tree/master/blurb > > > > > > blurb is an interactive command-line tool that helps you write Misc/NEWS > > entries. You simply run blurb from anywhere inside a CPython repo. > > blurb runs an editor for you with a template open. You fill in these > > three pieces of information: > > > > * the bugs.python.org or "bpo" issue number, > > * what "section" of Misc/NEWS this entry should go in (by uncommenting > > the correct line), and > > * the text of the Misc/NEWS entry, in ReST format. > > > > You save and exit and you're done. blurb even stages the Misc/NEWS > > entry in git for you! > > > > > > Behind the scenes, blurb writes your information here: > > > > Misc/NEWS.d/next// > > > > The "" is the name of the section in Misc/NEWS where your > > entry should go. contains the current date and time, the bpo > > number, and a nonce to prevent collisions. > > > > These "next" files get merged together into a single aggregate .rst file > > by the release manager when cutting a release (using "blurb release"). > > One nice feature of this approach: when you cherry-pick a change, its > > Misc/NEWS entry in "next" gets cherry-picked along with it. > > > > > > One important change: Misc/NEWS will no longer be checked in. It'll > > still be present in CPython tarballs; it will be generated by the > > release manager as part of cutting a release. But as a repository of > > information, it's been superseded by the various blurb data files. And > > by regenerating it from data files, we ensure that we'll never ever have > > a Misc/NEWS conflict ever again! > > > > The plan is to leave Misc/NEWS in the CPython repo for maybe another > > week, to let the current crop of PRs get merged. But new work should > > switch to using blurb immediately. > > > > > > You can install blurb from pip: > > > > % pip3.6 install blurb > > > > In fact--please do! > > > > > > //arry/ > > > > > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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` doesn't know to examine the NEWS.d > > directory when checking for NEWS entries. > > > > I opened https://bugs.python.org/issue30750 for that if someone wants to > make the change. Ok, then I edited the title for https://github.com/python/cpython/pull/2381 :-) Regards Antoine. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 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 python3 interpreter. > > Well, you can always create a venv using the system python3. > > Nowadays, to be honest, I use conda and Anaconda a lot, so I can > very quickly create a local Python 3.6 environment on my work machine, > even if my OS doesn't provide a Python 3.6. I'm just not sure everyone > has the same habits as me, though I'm all for more core developers > adopting conda :-) I already have a cpicker venv set up in vex to run cherry-picker [1], so I'll probably just add blurb to that (or create a new "cpydev" one with all the CPython workflow tools). 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 old to let them just use "pip install --user" or "pipsi install" Cheers, Nick. [1] Based on a "make altinstall"ed 3.6 for now, although I'll be able to drop that once I upgrade to Fedora 26 -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 multiple patches on an issue, whereas an issue usually gets only one news item. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 PRs / checkins for a single issue. Can you describe the problem you're having? //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 there isn't? There are sometimes good reasons to have multiple > patches on an issue, whereas an issue usually gets only one news item. 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). Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 installed in your system-wide python3 interpreter. Second, I assumed core devs were compiling their own Python interpreters locally in their account--in no small part so they can install any packages they want. 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. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 old to let them just use "pip install --user" or "pipsi install" Don't forget that not only core developers but all committers need to use blurb. This makes committing to CPython more difficult for new committers. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 trivial. 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. 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). What if the patch removes a NEWS entry? Or fixes a number in an existing entry? ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 committers. And blurb makes that easy. But it's pretty easy to write them by hand; that's why we pre-created the "next" directories, and there are instructions in the dev guide. Also it should be easy for some JavaScript expert to write a static page that generates blurb files for you--it provides a form, you fill it out, and you "download" the blurb file. (I've seen pages that do that sort of thing, though I don't know how to write that kind of JavaScript myself.) //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 to run those tools if their system Python is too old to let them just use "pip install --user" or "pipsi install" Don't forget that not only core developers but all committers need to With rare exception, 'committer' == 'core developer'. Do you mean 'contributor'? use blurb. This makes committing to CPython more difficult for new committers. Brand-new contributors may leave the news item for someone else, but we will no longer have to ask contributors to skip it because of merge conflicts. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 Bedevere for a news file unless the PR is labeled as trivial. And what if there isn't? In particular, will Belvedere suggest adding a news entry or mandate one? There are sometimes good reasons to have multiple patches on an issue, whereas an issue usually gets only one news item. 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 suggesting adding a possibly incomplete entry with the first patch. If that is so, it would be helpful if blurb could pull an existing file for an issue into the editor. What if the patch removes a NEWS entry? If the news entry is proper, it should only be removed as part of reverting the patch, but only if it is the last remaining PR for the issue. Or fixes a number in an existing entry? I believe bpo numbers are part of the file *name*, not part of the news entry. (The consolidator should do the formatting.) So the issue is changing file names. Belvedere should flag mismatches between PR title and news file names. Changing the number in the title, which is sometimes necessary, will create a mismatch. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New workflow change: Welcome to blurb
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 suggesting adding a possibly incomplete entry with the first > patch. If that is so, it would be helpful if blurb could pull an existing > file for an issue into the editor. I was mainly referring to cases where either an initial commit (with a complete NEWS entry) requires follow-up fixes (no NEWS edit necessary). However, another case did occur to me, which is fixing bugs reported against never-released features (which is what I'm currently working on for PEP 538). So trying to automate that particular check may end up proving to be more hassle than it's worth. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
