Setup for release on PyPI

[kba]

Once the tools are versioned (#43), they can be released to PyPI for easy installation with pip.

Uploading a source distribution basically works with the configuration in this PR.

Open Questions:

• Name: hocr-tools with a dash is possible but if the project is properly packaged in the future (Make hocr-tools a proper module #42), it would be wise to have a name that is a valid module name That is not really a problem, seems to be fairly common actually.
• What to put in author / author_email? I started with @tmbdev's credentials I removed the author_email, PyPI warns on register but still carries out the upload, at least for test.
• Specify requirements in setup.py or in requirements.txt? Could be both, discussed here
• Who manages the uploads? I will

[zuphilip]

Another advantage with requirements.txt is that the python docker "onbuild" is exactly looking for this.

(Later more on the other points...)

[kba]

Another advantage with requirements.txt is that the python docker "onbuild" is exactly looking for this.

Good point. From what I understand, requirements.txt is more for defining a complete environment in which to run a project, whereas the requirements in setup.py define the minimum. pip will use the data in setup.py.

[zuphilip]

I think we need here the v as well, e.g. something like

https://github.com/zuphilip/hocr-tools/tarball/v0.3.2

which just redirects to

https://codeload.github.com/zuphilip/hocr-tools/legacy.tar.gz/v0.3.2

[kba]

Fixed it.

[zuphilip]

It might also make sense to add here

    maintainer = '',
    maintainer_email = '',

with the credentials of one of us. 😇 Do you volunteer @kba? We could also discuss this separately if you prefer.

[zuphilip]

Perfect. Thank you! I will squash+merge in the next minutes.

[kba]

Requirements are still open.

[zuphilip]

Looks good for me. Let me know when it is ready to merge+squash.

[kba]

It should work now, we can always improve it.