-
-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913
Comments
Author: Matthias Koeppe |
Commit: |
This comment has been minimized.
This comment has been minimized.
Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
Will this be able to deal with optional package declarations (in time)? |
comment:11
The plan for optional packages is that users would install a package such as |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed keywords from none to sd111 |
This comment has been minimized.
This comment has been minimized.
comment:16
Added instructions for testing to the ticket description. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:140
no idea about that PS. |
comment:141
We do have the SPKG |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:143
Or try with this fix (which makes no change to how we install things in the Sage distribution, but removes excessive dependencies from the wheels) |
comment:144
(Newer versions of |
comment:145
ohh, nodejs getting installed as a sage package?! |
comment:146
Replying to @mkoeppe:
it did not. trying the latest commit now |
comment:147
the patch let it go further, but now this puzzling "no space left on device"
I really don't get is, there is almost 300Gb left on /home/scratch2/ New commits:
|
comment:148
pip likes to use temporary directories, probably in /tmp or /var/tmp |
comment:149
Try setting |
comment:150
is TMPDIR an env.var. I can export before running this job? Or is it something pythonic? |
comment:151
Just the standard environment variable |
comment:152
OK, this run finishes, with some doctest errors, mainly in sphinx/docs related:
if this is expected, feel free to make it positive review. |
Reviewer: Dima Pasechnik |
comment:153
Thanks for testing! Yes, this looks as expected. The documentation is not built by this invocation. We should disable the corresponding doctests, for example using #30778 - but that's something for the 9.4 series. |
comment:154
Setting priority to blocker to bring this ticket to the attention of the release bot. |
Changed branch from u/mkoeppe/sagelib__add_setup_cfg__install_requires_ to |
After #29500, it is possible to install Python packages built by the Sage distribution into user-defined venvs.
As of Sage 9.3.beta8,
sagelib
is published as a source distribution on PyPI (https://pypi.org/project/sagemath-standard), but the package does not have proper dependency information yet.As part of
bootstrap
, we now generate (1) thepyproject.toml
(PEP 517 metadata) andinstall_requires
information, (2)requirements.txt
and (3)Pipfile
using m4 from the information added in #30719. These files provide 3 distinct ways of setting up a user-defined venv.(Adding
pyproject.toml
does not change how the Sage distribution installs sagelib becausebuild/pkgs/sagelib/spkg-install
usessetup.py install
directly.)To test - use
./bootstrap
and then configure and build the Sage distribution. Then follow the instructions inbuild/pkgs/sagelib/src/tox.ini
:Related or follow-up tickets:
./configure --enable-editable
sage_bootstrap
: Add command "sage -package list --output={install-requires,requirements,pipfile,debian,....}"python -m venv
,virtualenv
(20.x), orpipenv
.References:
CC: @dimpase @tobiasdiez @jhpalmieri @videlec @kiwifb @malb
Component: build
Keywords: sd111
Author: Matthias Koeppe
Branch/Commit:
04da2c6
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/30913
The text was updated successfully, but these errors were encountered: