Changes between Version 1 and Version 54 of Ticket #29013
- Timestamp:
- 03/19/20 16:24:21 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29013
-
Property
Status
changed from
new
toneeds_work
-
Property
Authors
changed from
Matthias Koeppe
toMatthias Koeppe, Erik Bray
- Property Cc vbraun added
-
Property
Summary
changed from
In a python3 build, install all Python packages into a venv
toIn a python3 build, install all Python packages into a venv different from SAGE_LOCAL
-
Property
Dependencies
changed from
to
#29362
-
Property
Branch
changed from
to
public/29013-use-py3-venv
-
Property
Milestone
changed from
sage-9.1
tosage-wishlist
-
Property
Commit
changed from
to
208c7e68c24c1fe896a5e6573c6aae5399056431
-
Property
Status
changed from
-
Ticket #29013 – Description
v1 v54 1 We propose to create a venv (https://docs.python.org/3/library/venv.html) at `$SAGE_LOCAL/lib/sage/venv/sage/`, 2 to activate the venv in the `sage-env` script, and to install all Python packages (including `sagelib`) into this venv. 1 #27824 makes `$SAGE_LOCAL` a venv if a suitable system python3 is found. 3 2 4 This is preparation for #27824, in which the system's python3 will be used when available.3 On this ticket, we create a venv (https://docs.python.org/3/library/venv.html) instead at `$SAGE_LOCAL/lib/sage/venv/sage/`, run the standard `activate` script in the `sage-env` script, and install all Python packages (including `sagelib`) into this venv. 5 4 6 Note, the proposal is to use `venv` (new since Python 3.3), not `virtualenv`. So this change will be limited to Python 3 builds of Sage. 5 (This used to be preparation for #27824; but the approach of that has been changed.) 6