doc tools/books*py: improve argument handling of DOC_LANG, and others

[ceri]

Summary

1. fix shebang lines;
2. add a -o option that makes no changes but prints the files that would be updated/created;
3. allow the -l argument (and therefore DOC_LANG) to be whitespace separated, comma separated, or a mixture of both

Test Plan

1. chmod +x ./tools/books-toc-creator.py; ./tools/books-toc-creator.py -l en

2. python3 ./tools/books-toc-creator.py -o -l en,es,hu

3. python3 ./tools/books-toc-creator.py -l en,fr de ja el,it python3 ./tools/books-toc-creator.py -l en,fr de ja el,it -o zh-cn

[ceri]

missed gnu_getopts in two files.

[ceri]

Adding blackend as we had discussed the DOC_LANG separators some weeks ago.

[dbaio]

This kind of option remembers something with verbose and dry run options.

I've tested here and this seems fine.

Out of curiosity, is this for help debugging Makefile changes/improvements?

[ceri]

In D30732#690947, @dbaio wrote:

Out of curiosity, is this for help debugging Makefile changes/improvements?

The DOC_LANG restores previous behaviour documented in make.conf (or share/examples/make.conf, I can’t check at the moment) and white space separated variables are arguably easier to work with in make.

The -o option is a start at reintroducing proper dependency tracking, so that the python targets can stop being .PHONY and incremental builds can come back.

[dbaio]

In D30732#691069, @ceri wrote:

In D30732#690947, @dbaio wrote:

Out of curiosity, is this for help debugging Makefile changes/improvements?

The DOC_LANG restores previous behaviour documented in make.conf (or share/examples/make.conf, I can’t check at the moment) and white space separated variables are arguably easier to work with in make.

The -o option is a start at reintroducing proper dependency tracking, so that the python targets can stop being .PHONY and incremental builds can come back.

Right.
Thanks for the information.

[blackend]

Seems fine.