Add --bpo and --section flags to "blurb add".

[larryhastings]

No description provided.

[larryhastings]

Thanks for the suggestion, Mariatta!

[matrixise]

I did a comment about the section parameter, but for me, it's nice.
just one question, the "section" represents the sections from bpo ?

[matrixise]

why don't you keep the same principle with the .. bpo: {bpo}? at this line, you already have a constructed section.
You build the section at that line https://github.com/python/core-workflow/pull/312/files#diff-1bd652c5f766ddebec6cd6dc8f27b3b1R927

Do you make the construction before because you don't want to have a conditional template? is it right?

[matrixise]

in my workflow, I could use that

blurb add --bpo=(git rev-parse --abbrev-ref HEAD | sed -e 's/bpo-//')

so, I am happy with that solution and we can add some alias for the several sections...

alias blurbadddoc="blurb add --bpo=(git rev-parse --abbrev-ref HEAD | sed -e 's/bpo-//') --section=Documentation"

[hugovk]

Works well! Needs a sync with master as blurb 1.0.8 has since been released.

[hugovk]

How about printing the valid sections when this fails?

Suggested change

	error("blurb add --section argument " + repr(section) + " is not a valid section!")
	error("blurb add --section argument " + repr(section) + " is not a valid section! Use one of:\n" + "\n".join(sections))

For example:

$ python blurb.py add --bpo 123 --section aaa
Error: blurb add --section argument 'aaa' is not a valid section! Use one of:
Security
Core and Builtins
Library
Documentation
Tests
Build
Windows
macOS
IDLE
Tools/Demos
C API

[merwok]

Does it make sense to use the bpo abbreviation, or would it be better as issue now?

[hugovk]

This will need recreating for the new repo at https://github.com/python/blurb.

I've opened python/blurb#6 for this.