Re: [python-committers] [Python-Dev] 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-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] [Python-Dev] 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-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] [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-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] [Python-Dev] New workflow change: Welcome to blurb
On 24 June 2017 at 14:01, Craig Rodrigues wrote: > On Fri, Jun 23, 2017 at 8:24 PM, 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 > > > Yes, when you have a single NEWS file that needs to get updated, > the process begins to fall apart when you have a pull request type of > workflow > which results in many merge conflicts to the single NEWS file. > > Twisted and Buildbot use towncrier ( https://github.com/hawkowl/towncrier ) > which tries > to solve the same problem as blurb. 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 We ultimately settled on blurb mainly because we wanted to be able to customise various details differently from the way towncrier works, and we figure they're close enough in spirit that folks familiar with one won't have any problems adapting to the other. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ 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] [Python-Dev] New workflow change: Welcome to blurb
One quick heads up – the NEWS file is included in the docs build (if not in the html docs, certainly in the CHM for Windows releases). You may have to do some extra work to keep that from breaking when you remove it. We might also include it as plain text in the installers, I forget right now. Is blurb going to be embedded in the main repository? Not necessarily a problem if not, but I'd rather not have the build process depend on pip. Though I guess Sphinx is dependency already, so perhaps I should just integrate it better into the build… Top-posted from my Windows phone From: Larry Hastings Sent: Friday, June 23, 2017 20:26 To: Python Dev; python-committers Subject: [Python-Dev] New workflow change: Welcome to blurb 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-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
