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

delete RISparser from pypi? #59

Open
shapiromatron opened this issue Nov 10, 2023 · 3 comments
Open

delete RISparser from pypi? #59

shapiromatron opened this issue Nov 10, 2023 · 3 comments
Assignees

Comments

@shapiromatron
Copy link
Collaborator

shapiromatron commented Nov 10, 2023

Delete the older version of this package from pypi? https://pypi.org/project/RISparser/

It was last updated w/ python 3.6, which has been EOL for over a year now. This can clear out the historical older versions of the package and potentially make it easier to find the modern version of the package, rispy.

I think this can only be done by @MrTango - I don't have access on the pypi website.

@J535D165
Copy link
Contributor

Enjoy this post with many CPython core devs: https://discuss.python.org/t/stop-allowing-deleting-things-from-pypi/17227.

I suggest cleaning the Description of the latest RISParser release (by publishing a new one) and seeing it fade in Google. Removing RISParser versions might affect users.

@shapiromatron
Copy link
Collaborator Author

shapiromatron commented Nov 15, 2023

I guess from a purity sense this makes sense, but practically, older versions of the library really aren't supported any more and we don't want people using them. It clutters the ecosystem, and I don't ever want to support it again. We have the releases here on github if someone wants them that bad and would rather use an old release.

I'm fine breaking things, even hypothetical ones. The last RISparser release was from 2018.

It's a lot less work for us maintainers to just delete the old ones, instead of mint a new release and publish it on pypi just to tell people not to use it anymore. And this is all hypothetical - they should update to the latest version, or vendor the old version into their application.

We could just publish version 0.4.3 on this github repo if someone needs it; https://github.com/MrTango/rispy/blob/main/HISTORY.rst#v043-2018-04-10

@shapiromatron
Copy link
Collaborator Author

@MrTango - thoughts on this? it's one less possible attack vector on PYPI in my opinion...

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