release process changes #25
Description
Currently there are some issues with the existing release process:
$ python3 setup.py upload
[...]
running upload
gpg --detach-sign -a dist/llfuse-1.3.7.tar.bz2
gpg: using "0xD113FCAC3C4E599F" as default secret key for signing
/home/nikratio/.local/lib/python3.7/site-packages/setuptools/command/upload.py:110: ResourceWarning: unclosed file <_io.BufferedReader name='dist/llfuse-1.3.7.tar.bz2.asc'>
open(filename+".asc", "rb").read())
ResourceWarning: Enable tracemalloc to get the object allocation traceback
Submitting dist/llfuse-1.3.7.tar.bz2 to https://upload.pypi.org/legacy/
Upload failed (400): Invalid file extension: Use .egg, .tar.gz, .whl or .zip extension. See https://www.python.org/dev/peps/pep-0527 for more information.
WARNING: Uploading via this command is deprecated, use twine to upload instead (https://pypi.org/p/twine/)
error: Upload failed (400): Invalid file extension: Use .egg, .tar.gz, .whl or .zip extension. See https://www.python.org/dev/peps/pep-0527 for more information.
Ideas:
- gpg: using "0xD113FCAC3C4E599F" as default secret key for signing
If that key is documented somewhere and the idea is that I could also do releases, guess my key id should be added to that docs.
- Upload failed (400): Invalid file extension: Use .egg, .tar.gz, .whl or .zip extension.
Trivial to fix, as llfuse is used on non-windows platforms, .tar.gz is the way to go for a source package.
- Uploading via this command is deprecated, use twine to upload instead (https://pypi.org/p/twine/)
Needs adding twine to the release process. I've already done that for other projects, no problem.
Metadata
Metadata
Assignees
Labels
No labels