-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
./configure --with-sage-venv=none #30896
Comments
comment:1
To disable building Python packages, the make targets would be replaced by dummy targets in the same way as it is done for packages found by spkg-configure. In addition, this could go through #30383 ("configure --disable-SPKG" for standard packages) so that |
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.
Last 10 new commits:
|
Commit: |
Work Issues: Rework as "--without-sage-venv" (implied by "--without-python") |
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to sd111 |
comment:8
Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Changed work issues from Rework as "--without-sage-venv" (implied by "--without-python") to Rework as "--without-sage-venv" (implied by "--without-python"), rebase on #31362 |
comment:15
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date. |
(split out from #29013)
As of #32442,
./configure --with-sage-venv=no
just means: Keep SAGE_VENV the same as SAGE_LOCAL.In this ticket we add support for a new option, perhaps
./configure --with-sage-venv=none
, which would suppress making any Python venv and suppress building any Python packages.(Using the mechanism of disablable installation trees from #31356, #32759.)
In this configuration,
sage_conf
cannot be built as a wheel, so we only build an sdist (usingsage-bootstrap-python
!) and store that in$SAGE_LOCAL/var/lib/sage/wheels
.Also, the default target
all-start
makes no sense, and also the docbuild cannot be done. Instead, the default would be to build only the targetall-sage
(which would be modified to remove the unnecessary special casesagelib
).This is for users who prefer to install Python packages into their own virtual environments using standard Python tools.
Depends on #31362
CC: @dimpase @jhpalmieri @orlitzky @tobiasdiez
Component: build
Keywords: sd111
Work Issues: Rework as "--with-sage-venv=none" (implied by "--without-python"), rebase on #31362
Branch/Commit: u/mkoeppe/__configure___without_python @
932ebd8
Issue created by migration from https://trac.sagemath.org/ticket/30896
The text was updated successfully, but these errors were encountered: