"sage -python", "sage -pip", etc.: Do not fall back to system Python

[mkoeppe]

(from #29626)

With a fresh tarball, sage --pip install PKG doesn't do what I want: since I'm using the system Python, it installs the package in the system location, not in SAGE_ROOT/local/..

(It gives an error for a bootstrapped, unconfigured tree, but calls system python in a configured tree.)

In this ticket, we change all of sage -pip, sage -python, sage -python3 etc. to give an error if Sage's Python has not been built yet (or the venv over the system python3 set up).

CC: @jhpalmieri @dimpase @vbraun

Component: build

Author: Matthias Koeppe

Branch/Commit: 248c13b

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/29627

[mkoeppe]

comment:1

sage -pip just calls sage-python -m pip.

In fact, sage -python should probably exit with an error if the venv (or Sage's python) has not been created yet.

[mkoeppe]

Author: Matthias Koeppe

[mkoeppe]

Branch: u/mkoeppe/_sage__pip__should_never_install_into_the_system_python_s_site_packages

[dimpase]

Commit: 248c13b

[dimpase]

comment:5

ok, this makes sense.

---

New commits:

248c13b

"sage -python", "sage -pip", etc.: Do not fall back to system Python

[dimpase]

Reviewer: Dima Pasechnik

[mkoeppe]

comment:6

Thanks!

[vbraun]

Changed branch from u/mkoeppe/_sage__pip__should_never_install_into_the_system_python_s_site_packages to 248c13b