Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PyPI package #163

Open
SilverRainZ opened this issue Aug 14, 2023 · 5 comments
Open

Update PyPI package #163

SilverRainZ opened this issue Aug 14, 2023 · 5 comments

Comments

@SilverRainZ
Copy link

python-ly on PyPI is still 0.9.7, how about updating it to the latest 0.9.8?

@jeanas
Copy link
Member

jeanas commented Aug 14, 2023

Speaking as the person who did the release in #160 (basically to unblock the update of python-ly in the Frescobaldi Flatpak package), I'm aware it's suboptimal that we did a release without uploading it to PyPI, but only @wbsoft has access there, and he has little time for free software projects at the moment.

@wbsoft Maybe you have time to upload the release now? Actually this would also be useful for Frescobaldi too.

Alternatively, I'll be happy to do this if you give me PyPI access on frescobaldi and python-ly, and I'm sure @fedelibre would say the same, although I of course understand perfectly if you don't want to.

@wvengen
Copy link

wvengen commented Mar 21, 2024

Thanks for doing the release! As you already have Github access, I think it makes sense for you to have PyPI access as well (perhaps ideally this could be a Github action uploading a release when creating a tag).
As a user, I would very much like this release (and future ones) to be published on PyPI.

Did you already try e-mailing @wbsoft directly? If there is no response (assuming because he is too busy), there will be a moment where requesting PyPI project name claim may be appropriate.

@jeanas
Copy link
Member

jeanas commented Mar 21, 2024

Did you already try e-mailing @wbsoft directly?

Yes.

If there is no response (assuming because he is too busy), there will be a moment where requesting PyPI project name claim may be appropriate.

Perhaps. That process has been on hold for a long time, but now that they're hiring someone to do that job, it will probably get better soon. However, I have very little time for LilyPond/Frescobaldi myself now, so I doubt my own capacities to maintain python-ly besides running the release process…

@wvengen
Copy link

wvengen commented Mar 22, 2024

Ah, you are more aware of what is going on there than me :)
If you would only be doing releases, that may already be great, in my view.
I would also be happy to add a Github Action that auto-publishes new releases to PyPi, if that is deemed useful.

@jeanas
Copy link
Member

jeanas commented Mar 22, 2024

I would also be happy to add a Github Action that auto-publishes new releases to PyPi, if that is deemed useful.

Thank you, but I'm familiar with Python packaging (I've contributed to https://packaging.python.org, though I don't really have the time anymore either), so trusted publishing via GHA wouldn't really save me time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants