Closed apetresc closed 4 years ago
Thanks, this looks good! I'm very happy that you are handling packaging to pypi, but wouldn't mind being added as co-maintainer (my handle is gauteh
). Would be great with Github Actions.
Done! I'll send over the Github Action workflow later tonight, hopefully.
Hi, I am planning a new release as soon as possible. There were some changes to the send
command that makes it more safe, so should release a new version fast. #154
@gauteh can you give a heads-up once a new version was released? Happy to update the description in nixpkgs
to the new release.
Florian Klink writes on May 18, 2020 13:05:
@gauteh can you give a heads-up once a new version was released? Happy to update the description in
nixpkgs
to the new release.
Yes, I'll do it here. Let's test the latests changes at least a day.
v1.2 has been released.
@gauteh pypi still is on 1.1? Is this expected?
Florian Klink writes on May 23, 2020 14:31:
@gauteh pypi still is on 1.1? Is this expected?
Uploaded.
@gauteh, @apetresc I see there was some discussion about uploading to PyPI automatically on releases via GitHub Actions. I assume this isn't yet automated, right?
Should we keep fetching from GitHub, or download from PyPI?
For packaging distros I recommend sticking with the source directly.
This is required by PyPI if the description format is not the default (restructured text).
On that note, I should add that I've been uploading lieer source dists to PyPI so that users can do a simple
pip install lieer
: https://github.com/apetresc/lieer/pull/new/pypi-compat. This is the only change that is required to make it compatible.If you would prefer to take over the PyPI entry for the project, please let me know! I will happily transfer it over (and can even help you write a Github Actions workflow to automatically deploy it there whenever you create a tagged release)