-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
sage.features.Executable: Prepend $SAGE_VENV/bin:$SAGE_LOCAL/bin to PATH #31296
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date. |
Dependencies: #32565 |
Changed dependencies from #32565 to none |
Dependencies: #31292 |
Author: Matthias Koeppe |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:14
Please extract
to a central place (I would say sage.env but you probably don't like this) for easier reuse in similar situations.
this is a normal variable and thus should be lowercase. |
comment:24
Replying to @tobiasdiez:
Yes, a year, what's the rush? |
comment:25
Replying to @tobiasdiez:
Writing that is no easier than wrapping |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
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:36
I presume the latte doctest patch #33467 comment:4 |
comment:37
Yes, that's right, can you push it to the ticket please? |
comment:38
later today, will do. |
New commits:
|
Changed branch from u/mkoeppe/sage_features_executable_SAGE_LOCAL to u/dimpase/sage_features_executable_SAGE_LOCAL |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Dima Pasechnik, Tobias Diez |
comment:42
Thank you! |
Changed branch from u/dimpase/sage_features_executable_SAGE_LOCAL to |
Follow-up from #22731.
This is so that Sage becomes fully functional even when not being run from within
sage-env
(which setsPATH
)Of course,
PATH
is not actually manipulated, onlyExecutable
finds the executable in more places.As an illustration, we update
sage.interfaces.four_ti_2
andsage.interfaces.latte
to useExecutable.absolute_filename()
from #31292. Then, aftersage -i 4ti2 latte_int
, the following works with this ticket:In follow-up tickets, other code that calls executables needs to be updated to use
Executable.absolute_path()
from #31292. The first tickets to do so are #33440, #33465, #33466, #32645, #33467, #33405.This is work towards:
Depends on #31292
CC: @tobiasdiez @kiwifb @tobihan @antonio-rojas @orlitzky
Component: build: configure
Author: Matthias Koeppe
Branch/Commit:
160e9af
Reviewer: Dima Pasechnik, Tobias Diez
Issue created by migration from https://trac.sagemath.org/ticket/31296
The text was updated successfully, but these errors were encountered: