Open mkoeppe opened 3 years ago
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 configure
already shows that the build is disabled for Python packages.
Description changed:
---
+++
@@ -1,4 +1,6 @@
In this ticket we add support for `./configure --with-python=no`, which would suppress making any Python venv and suppress building any Python packages.
+
+In this configuration, the default target `all-start` makes no sense, and also the docbuild cannot be done. Instead, the default would be to build only the target `all-sage` (which would be modified to remove the unnecessary special case `sagelib`).
This is for users who prefer to install Python packages into their own virtual environments using standard Python tools.
Description changed:
---
+++
@@ -1,3 +1,5 @@
+(split out from #29013)
+
In this ticket we add support for `./configure --with-python=no`, which would suppress making any Python venv and suppress building any Python packages.
In this configuration, the default target `all-start` makes no sense, and also the docbuild cannot be done. Instead, the default would be to build only the target `all-sage` (which would be modified to remove the unnecessary special case `sagelib`).
Description changed:
---
+++
@@ -1,8 +1,10 @@
(split out from #29013)
-In this ticket we add support for `./configure --with-python=no`, which would suppress making any Python venv and suppress building any Python packages.
+In this ticket we add support for `./configure --with-sage-venv=no`, which would suppress making any Python venv and suppress building any Python packages.
-In this configuration, the default target `all-start` makes no sense, and also the docbuild cannot be done. Instead, the default would be to build only the target `all-sage` (which would be modified to remove the unnecessary special case `sagelib`).
+In this configuration, `sage_conf` cannot be built as a wheel, so we only build an sdist 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 target `all-sage` (which would be modified to remove the unnecessary special case `sagelib`).
This is for users who prefer to install Python packages into their own virtual environments using standard Python tools.
Last 10 new commits:
f9ac70e | Add install-requires.txt for setuptools, pip |
f6a2c56 | Merge tag '9.3.beta1' into t/30719/add_build_pkgs_spkg_install_requires_txt_for_all_python_packages |
e61929d | build/pkgs/sphinx/install-requires.txt: Update from gentoo |
8fe0e35 | build/pkgs/python_openid: Unused, remove |
ba1d913 | build/pkgs/itsdangerous: Unused, remove |
bb6c4ae | build/pkgs/tox/install-requires.txt: New |
d507501 | build/pkgs/networkx/install-requires.txt: Update from gentoo |
c3a9352 | build/pkgs/pathpy/install-requires.txt: Package removed in #30611, remove |
ebd4610 | build/pkgs/pynac/install-requires.txt: New |
e25b833 | Merge branch 't/30719/add_build_pkgs_spkg_install_requires_txt_for_all_python_packages' into t/30896/__configure___without_python |
Work Issues: Rework as "--without-sage-venv" (implied by "--without-python")
Description changed:
---
+++
@@ -2,7 +2,7 @@
In this ticket we add support for `./configure --with-sage-venv=no`, which would suppress making any Python venv and suppress building any Python packages.
-In this configuration, `sage_conf` cannot be built as a wheel, so we only build an sdist and store that in `$SAGE_LOCAL/var/lib/sage/wheels`.
+In this configuration, `sage_conf` cannot be built as a wheel, so we only build an sdist (using `sage-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 target `all-sage` (which would be modified to remove the unnecessary special case `sagelib`).
Changed keywords from none to sd111
Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111
Changed dependencies from #30719 to #31263
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
fec4b06 | fix sage -b after 30622 |
dff846c | go through make/build/install |
8aff784 | build/pkgs/python3/spkg-configure.m4: Accept --with-python=no |
932ebd8 | m4/sage_spkg_collect.m4: If configured --without-python, mark all Python packages as not required |
Changed dependencies from #31263 to #31362
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
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.
Changed work issues from Rework as "--without-sage-venv" (implied by "--without-python"), rebase on #31362 to Rework as "--with-sage-venv=none" (implied by "--without-python"), rebase on #31362
Description changed:
---
+++
@@ -1,6 +1,8 @@
(split out from #29013)
-In this ticket we add support for `./configure --with-sage-venv=no`, which would suppress making any Python venv and suppress building any Python packages.
+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.
In this configuration, `sage_conf` cannot be built as a wheel, so we only build an sdist (using `sage-bootstrap-python`!) and store that in `$SAGE_LOCAL/var/lib/sage/wheels`.
Description changed:
---
+++
@@ -3,6 +3,7 @@
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 (using `sage-bootstrap-python`!) and store that in `$SAGE_LOCAL/var/lib/sage/wheels`.
(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