-
-
Notifications
You must be signed in to change notification settings - Fork 481
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-pip-install: Try installing without --no-deps first #32492
Comments
New commits:
|
Commit: |
Author: Matthias Koeppe |
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.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:10
Adding #29847 as a dependency, which fixes the venv install for |
Dependencies: #29847 |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
This doesn't quite work as intended. Weirdly, |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:20
This version works for me. It makes use of the previously built wheels that are kept in |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:23
This seems to work as advertised. Is there room at some point for a pickier build process that actually produces errors when this kind of thing comes up? (Something that could be used by buildbots or developers working new packages but not the default.) |
comment:24
A related question: how do we convince people to actually check for these warnings? |
comment:25
I think there's room for escalation in a follow-up ticket, but I think it's safer to first bring it to wider testing by developers in the current form. |
comment:26
I've opened #32529 for this. |
comment:27
I tested this with |
Reviewer: John Palmieri |
comment:28
Thanks for reviewing! |
Changed branch from u/mkoeppe/sage_pip_install__try_installing_without___no_deps_first to |
We currently use
pip install
with the option--no-deps
- which suppresses installation of runtime dependencies, as we rely on our own dependency management.In order to make package upgrades (which might change dependencies) more robust, we change this to first attempt an install without
--no-deps
. Since we still use--no-index
(we also throw in a--no-cache
in this ticket), it will not actually attempt to install from PyPI but fail with an error.We then issue a warning (for developers) but fall back to the install with
--no-deps
(for robustness for users).(Prompted by #31280 comment:93, #30974 comment:14)
We also pass
--ignore-requires-python
in the wheel-building phase and in the retry. This simplifies the Python 3.10 preparation and is otherwise harmless.To test:
(this will rebuild all Python packages in a new venv)
In particular highly parallel builds reveal a few missing dependencies -- but there should be no new errors.
Fixing the dependencies will be done in follow-up ticket #32493, not here.
Depends on #29847
Depends on #32361
CC: @dimpase @seblabbe @jhpalmieri
Component: build
Author: Matthias Koeppe
Branch/Commit:
92c855c
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/32492
The text was updated successfully, but these errors were encountered: