-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
sage --package update-latest: Fix for package-names-containing-dashes; accept package classes :standard:, :optional: etc., restrict to normal Python packages; fix sage --package fix-checksum #31118
Comments
Commit: |
Author: Matthias Koeppe |
New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:9
OK, this appears to fix |
Reviewer: Dima Pasechnik |
comment:10
By the way, only |
comment:11
inability to update spkgs is a blocker all right. |
Changed branch from u/mkoeppe/sage___package_update_latest__fix_for_package_names_containing_dashes to |
... the current code is confused about pypa-normalized names vs. spkg-normalized names:
We also update the code so that it uses the files
checksums.ini
andinstall-requires.txt
to recognize normal Python packages.As a result, the interface has changed slightly:
sage --package update-latest :all:
now also updates optional and experimental packagessage --package update-latest :standard:
for (a better version of) the previous behaviorWe also fix
sage --package fix-checksum
so it does not trip over non-normal packages.CC: @vbraun @seblabbe @jhpalmieri @dimpase @videlec
Component: scripts
Author: Matthias Koeppe
Branch/Commit:
182b3d2
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/31118
The text was updated successfully, but these errors were encountered: