Add build/pkgs/SPKG/requirements.txt for all Python SPKG

[mkoeppe]

These files were added in #29287 (SPKG type: Make "normal/script/pip" orthogonal to "base/standard/optional/experimental") for all pip packages.

We record "abstract" version requirements in files build/pkgs/SPKG/install-requires.txt - this is #30719.

In this ticket, we additionally record "concrete" versions for all Python packages in build/pkgs/SPKG/requirements.txt.

(cf. https://packaging.python.org/discussions/install-requires-vs-requirements/)

Some scripts need updating to make sure that checksums.ini wins over requirements.txt - to keep normal packages normal.

Depends on #30719

CC: @slel @jhpalmieri @orlitzky

Component: build

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

[tobiasdiez]

comment:2

I would strongly suggest to have a look at pipenv, which manages python dependencies via pipfile and pipfile.lock (replacing requirements.txt and checksums.ini (?)).

[mkoeppe]

comment:3

Not sure if we can use pipenv as a drop in solution.

For various Python packages, we currently have to use patches or special build steps. I have sketched a way forward in #29500 -- use our custom build scripts to build wheels (and store them in a wheelhouse / private package index), which can then be installed by all standard tools (and also by users into separate venvs). We can certainly generate a Pipfile that makes this easier for users

[mkoeppe]

comment:4

Let's discuss two separate concerns on two separate tickets:

• sagelib's concern to declare the requirements regarding Python packages - sage_bootstrap: Add command "sage -package list --output={install-requires,requirements,pipfile,debian,....}" #29041
• sage-the-distribution's concern to provide working versions of Python packages as wheels - Install all Python packages via pip wheel (or setup.py bdist_wheel), store wheels in $SAGE_LOCAL/var/lib/sage/wheels #29500

[mkoeppe]

Dependencies: #30719

[mkoeppe]

Closing as not planned.