Changes between Version 86 and Version 93 of Ticket #29013


Ignore:
Timestamp:
04/04/21 19:14:39 (7 months ago)
Author:
mkoeppe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29013

    • Property Status changed from needs_work to needs_review
    • Property Dependencies changed from #31362 to
    • Property Commit changed from d04b08b61ba7e86e75da625a30717b9809606cb7 to 92f1a1bba94a5dd6a4c9458438c39b781b101ead
    • Property Work issues changed from AC_ARG_WITH to
  • Ticket #29013 – Description

    v86 v93  
    99 - This is activated by running, for example,
    1010`./configure --with-python=/usr/bin/python3.8 --with-sage-venv="$SAGE_LOCAL/var/lib/sage/venv/python3.8"`.
     11
     12
     13As of this ticket, we are able to establish the venv in an arbitrary configured directory instead of `SAGE_LOCAL`. This is already useful for #31396 to create a wheel-building venv that will not be packaged as part of `SAGE_LOCAL`.
     14
     15In follow-up tickets, we gain the full functionality that facilitates testing with several Python versions without having to rebuild the Sage distribution.  This depends on:
     16
     17 - #30534 Repackage `pynac` as a pip-installable package
     18
     19Follow-ups:
     20
    1121 - We also want to support `./configure --with-sage-venv=no` which would suppress making any venv (#30896)
    1222
    13 (Tricky case: When system python3 is not in use and SAGE_VENV != SAGE_LOCAL, then both a real `$SAGE_LOCAL/bin/python3` needs to be built and a venv in SAGE_VENV created... or should python3 be installed in `$SAGE_VENV`?)
     23 - Support the tricky case: When system python3 is not in use and SAGE_VENV != SAGE_LOCAL, then both a real `$SAGE_LOCAL/bin/python3` needs to be built and a venv in SAGE_VENV created... or should python3 be installed in `$SAGE_VENV`?)
    1424
    15 (Optional: A file `build/pkgs/SPKG/trees` could override the install tree determination - this would allow us to for example install a package such as `jupyter_core` both into something like `SAGE_NOTEBOOK_VENV` and `SAGE_VENV`...)
    16 
    17 This facilitates testing with several Python versions without having to rebuild the Sage distribution.
    18 
    19 This depends on:
    20  - #30534 Repackage `pynac` as a pip-installable package
     25 - Optional: A file `build/pkgs/SPKG/trees` could override the install tree determination - this would allow us to for example install a package such as `jupyter_core` both into something like `SAGE_NOTEBOOK_VENV` and `SAGE_VENV`...