Message 299142 - Python tracker (original) (raw)

• I was told that blurb needed to be in the core-workflow repo, that this was better than checking it in to CPython itself. Okay. If you want to debate the point, loop in Brett Cannon, he's the one with the strong opinions.

• Ned has taken over the 3.3 branch, and he's asked that we not bother to blurbify it (convert it to use blurb). My expectation is that we will blurbify all other active branches: 2.7 3.4 3.5 3.6 master.

• As part of the release process this weekend, I blurbified the 3.4 and 3.5 branches. There were already NEWS items stored in the Misc/NEWS.d/next directory, so I had to do something, and Brett has been encouraging me to move a little faster, so... I figured it was best to start there, as people don't care so much about 3.4 and 3.5 anymore, and they're "my" branches (as RM) so I wouldn't be inconveniencing anyone else. I assume we'll get all the problems ironed out before the next 3.6 release.

• When a branch is converted over to blurb, you'll have to use blurb to build the docs from a git checkout of that branch.

• When a branch is converted over to blurb, Misc/NEWS will no longer be a checked-in file. It will only be generated, by the release manager when making a release, or for fun whenever somebody feels like generating it I guess. It's important to remove it, because it's an output file, and if we leave it checked in people will modify it by hand, and then those changes will be lost the next time it's generated. In the 3.4 and 3.5 branches Misc/NEWS has been deleted.

• As Ned points out, blurb isn't necessary for tarballs released by the RM. My makefile-fu isn't up to the task, but essentially Doc/Makefile should run this logic (assuming cwd is Doc):

  if os.path.exists("../Misc/NEWS"): shutil.copy("../Misc/NEWS", "build/NEWS") else: os.system("blurb merge build/NEWS")

• I honestly don't understand the disposition of the venv in Doc/Makefile. Is it used automatically? Isn't it? It seems to be used under 3.5--when I do a docs build it installs a bunch of packages--so why didn't blurb get installed for doko? What about 3.4, which predates the venv in Doc/Makefile? TBH I'm a big dummy when it comes to venv stuff. I'm hoping someone smart like Ned will figure it all out and make it sane, regular, and predictable. (Hint hint!)

• Building the docs already requires a dozen packages (Sphinx, which in turn depends on markupsafe et al). I assumed requiring one more package, also installed from pip, was not the worst thing in the world. Is it?