add shebang line to script in tools

[fabbox]

This update fix #405.

It enables to run the scripts in tools (especially pdf2txt.py and dumppdf.py) directly from terminal.

[loqs]

Should it not be python3 as the python 2 no longer supported in line with https://www.python.org/dev/peps/pep-0394/ ?

[fabbox]

As python2 is now "deprecated" since January 2020, I didn't think about it. I must admit that according to https://www.python.org/dev/peps/pep-0394/#future-changes-to-this-recommendation, authors says the PEP394 should be update if the support for python2 is completly drop. On the other hand, most of scripts already containing the shebang line used the "python" and not "python3", so I really don't know.

[eli-schwartz]

@fabbox the Python PEP requirement is that for programs, such as this, which are incompatible with python2 and only work on python3, the shebang should specifically reference python3.

It is wrong to use #!/usr/bin/env python anywhere in this project, ever since support for python2 was dropped in 3502dc9. The current PR as-is will break Debian, since python2 is the preferred unversioned python there and that is what will end up being used.

[eli-schwartz]

Why did you close this PR, abandon the review, and open a new PR #421 with the exact same content?

[fabbox]

I close this pull request and creat a new one with the proposition (with python3).
Sorry for the long delay between the two propositions.. I though it was the way to do. Should I be able to edit this PR ?

[eli-schwartz]

Sure, this PR even updated when you pushed additional commits, then a minute later you closed it.

Github doesn't require you to close a PR and open a new one, ever.

[fabbox]

OK, I think I miss something in the PR workflow. I didn't find how to edit the PR. I will close the new one and try to update this one.

Sorry to all, my bad here, I was thinking it do not accept my PR but it was updating it...
I completly agreed with the proposed change so I updated it with python3 everywhere the shebang line appeared.

[pietermarsman]

@fabbox Thanks!

[estshorter]

@pietermarsman
I hope this fix will be released soon.

I'm a maintainer of a pdfminer.six-feedstock repositry which enables installation of pdfminer.six via conda.
The latest release (20200402) breaks tests because of no shebang line, and I cannot upgrade version on conda (sticking to 20191020)...

[pietermarsman]

@estshorter done!

Let me know if it works.

[estshorter]

Thanks @pietermarsman !
Now we can get the latest pdfminer.six via conda.