Changes between Version 8 and Version 9 of Ticket #29500


Ignore:
Timestamp:
Sep 6, 2020, 5:08:41 AM (2 years ago)
Author:
Matthias Köppe
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29500 – Description

    v8 v9  
    33In this ticket, we break the build process into these steps:
    44
    5  1. In `spkg-build`, build the wheel explicitly using `pip wheel` (or `setup.py bdist_wheel`); store the wheel in `SAGE_ROOT/repo`.
     5 1. In `spkg-build`, build the wheel explicitly using `pip wheel` (or `setup.py bdist_wheel`); store the wheel in `SAGE_ROOT/wheelhouse`.
    66
    77 2. In `spkg-install`, install the wheel.
    … …  
    99We drop (for Python packages only) the problematic use of the DESTDIR staging mechanism (#29585). The pip lock (if it is at all still necessary after the major pip upgrades in the 9.2 series) will only need to be held during the wheel installation (step 2).
    1010
    11 Optionally, the wheels in `SAGE_ROOT/repo` will persist after the completed build.  Then we can create a PEP 503 compliant Simple Repository index in `SAGE_ROOT/repo`. Then users can create virtual environments and install the wheels built by the Sage distribution into them, using standard tools such as `pipenv` `[[source]]` or `pip install --find-links` or `pip install --index-url`.
     11Optionally, the wheels in `SAGE_ROOT/wheelhouse` will persist after the completed build.  Then we can create a PEP 503 compliant Simple Repository index in `SAGE_ROOT/wheelhouse`. Then users can create virtual environments and install the wheels built by the Sage distribution into them, using standard tools such as `pipenv` `[[source]]` or `pip install --find-links` or `pip install --index-url`.
    1212
    1313-------