-
-
Notifications
You must be signed in to change notification settings - Fork 567
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's scripts in src/bin should not use build/bin/sage-system-python; remove sage-pypkg-location #29355
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:6
#29951 will only put Repurposing this ticket to change scripts in |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Commit: |
comment:11
|
comment:12
Thanks for catching this. This needs some thought |
comment:13
I think the issue is that the line between build scripts and runtime scripts is blurred. sage-env and sage-num-threads.py, maybe others? |
comment:14
Yes, I agree, I think the solution is to split the build-specific parts (parsing MAKEFLAGS) out from |
comment:16
Sounds good to me. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
In a follow-up ticket, we could probably get rid of |
This comment has been minimized.
This comment has been minimized.
comment:21
I should probably know the answer to this, but is there a promise that "python3" is the official name for the python interpreter in the future? After 2.x is completely dead, they're not going to change it back to "python"? (This is also relevant when we're searching for (only) a system "python3") |
comment:22
The name "python3" should be OK for a long time: |
comment:23
and https://twitter.com/gvanrossum/status/1306082472443084801 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:25
Needs review |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:29
Can we please get this ticket in? |
Reviewer: Dima Pasechnik |
comment:30
lgtm |
comment:31
Thanks! |
comment:32
I was currently checking it also. So, I confirm that
or the above were defined from Anyway, I have:
positive review! |
Changed reviewer from Dima Pasechnik to Dima Pasechnik, Sébastien Labbé |
comment:33
Looks like this ticket was merged as part of #30627. |
In previous tickets we have moved sage-the-distribution scripts out of
src/bin
.Some scripts that are (correctly) located in
src/bin
usesage-system-python
, which is inbuild/bin
and not installed and not available in distributions.We change
sage-coverage*
to just usepython3
. If Sage's venv is in the front of the PATH, this is Sage's python. But these scripts work with "any python3", it does not have to be the one in which sage is installed.We remove
src/bin/sage-pypkg-location
, which is undocumented and unused.We move
src/bin/sage-num-threads.py
tobuild/bin/sage-build-num-threads
(where it keeps usingsage-system-python
), leaving a much simplified versionsrc/bin/sage-num-threads.py
(which is usingpython3
) behind.CC: @dimpase @jhpalmieri @kiwifb @orlitzky @vbraun
Component: scripts
Author: Matthias Koeppe
Branch/Commit: u/mkoeppe/sagelib_s_scripts_in_src_bin_should_not_use_build_bin_sage_system_python__remove_sage_pypkg_location @
a4e757e
Reviewer: Dima Pasechnik, Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/29355
The text was updated successfully, but these errors were encountered: