-
Notifications
You must be signed in to change notification settings - Fork 3
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
Deprecate PyPI/CADET #40
Comments
Please consider adding another CI Pipeline to automate this. |
|
Important Note: After talking to @lieres, we decided to stop publising code in PyPI/cadet. Instead, we should simply add are README containing: "Wer das installiert ist doof" (or similar) and refer to the proper package. This way, we don't "lose" the name in the package index s.t. we can later still use it for meta packages. |
The readme should contain a short explanation (CADET is now used for the organization on GitHub and might be used for a meta package on PyPI) and links to the following pages for further information: |
FYI, there is a broken link in the README. |
Also, if I may nitpick, If I remember correctly, we had consider to raise an error on import which tells the users from where to get the "correct" packages. |
I did what you and Eric stated here
If you feel that is not enough, I can reopen the issue? |
I hope you used a polite alternative for "doof" ;) |
Added error on import and changed link in meta data. |
Since CADET (https://pypi.org/project/CADET/) is currently an alias fo CADET-Python, the release needs to be done there separately with the
cadet_pypi_release
branch to push the correct README.The text was updated successfully, but these errors were encountered: