Setup GitHub actions to build and publish sdist and wheels

[hroncok]

Followups:

• Create and store encrypted secrets
• Release rc6
• Update installation instructions in the README

[hroncok]

The wheels are ready to review in the artifacts section of any given job. Upon GitHub release, they shall be uploaded to PyPI.
@kliment Could you please store your PyPI credentials (PYPI_USERNAME, PYPI_PASSWORD) (or alternatively, give me the rights to store mine (I assume admin to the repo))? Once merged, we could release rc6 to actually test it and later we should update the installation instructions in README.

[kliment]

@hroncok I've created a pypi API token and added it as a secret named PIPY_API_KEY use token as username and this API key as password. I looked all over but couldn't find a way to allow anyone but the repo owner to add secrets.

[hroncok]

Thanks. Amended. Is this good to merge and shall we release rc6 as a followup?

[hroncok]

Ehm, one more thing. PIPY_API_KEY should have probably been PYPI_API_KEY, right?

[kliment]

Yes, except github's formatting mangled my message - the username needs to be __token__

[kliment]

Ehm, one more thing. PIPY_API_KEY should have probably been PYPI_API_KEY, right?

No, actually, it's correct as PIPY - I typoed it. Looks like it's impossible to rename.

[kliment]

I now added a second secret with the correct spelling

[hroncok]

Thanks. So we should be good now. The only way to test is is to actually use it.

[kliment]

Okay, from my pov we're good to merge. Feel free to do so if you feel the same way.

[kliment]

If you want I can also make a pypi test repo API key

[hroncok]

If you want I can also make a pypi test repo API key

I don't think that is necessary, better to squat the name sooner than later.

[hroncok]

I'm working to prep the PR with rc6 with chnagelog.

[hroncok]

#1085

[hroncok]

Run twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading Printrun-2.0.0rc6.tar.gz

  0%|          | 0.00/478k [00:00<?, ?B/s]
  2%|▏         | 8.00k/478k [00:00<00:08, 56.1kB/s]
 59%|█████▊    | 280k/478k [00:00<00:02, 79.5kB/s] 
100%|██████████| 478k/478k [00:00<00:00, 1.16MB/s]
NOTE: Try --verbose to see response content.
HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/
Invalid or non-existent authentication information. See https://pypi.org/help/#invalid-auth for more information.

[kliment]

I'll try manually uploading one with the same key to check

[hroncok]

Try the sdist probably.

[kliment]

I tried it and it says "The name 'Printrun' isn't allowed. See https://pypi.org/help/#project-name for more information."

[hroncok]

And I know why. What is your PyPI username?

[kliment]

My PyPI username is "kliment"

[kliment]

So the manual upload gave a different error than the automated one, suggesting we're not correctly setting the twine credentials. I'll create a new api key just for this and update the secrets.

[hroncok]

OK. The good news is nobody will claim the printrun name before you do, so we don't need to figure this out immediately.

pypi/support#529

[kliment]

2020-08-02T20:07:53.3841762Z The name 'Printrun' isn't allowed. See https://pypi.org/help/#project-name for more information.

So it works correctly now, but we can't upload because the name is locked.