Skip to content
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

Meta-ticket: Set environment for subprocesses invoked by Sage #30818

Open
mkoeppe opened this issue Oct 23, 2020 · 17 comments
Open

Meta-ticket: Set environment for subprocesses invoked by Sage #30818

mkoeppe opened this issue Oct 23, 2020 · 17 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Oct 23, 2020

Instead of relying on running in an environment set up by sage-env, we should set up specific environment variables whenever we invoke executables. This will be configurable through sage_conf.

This is so that Sage is fully functional even when not being run from within sage-env. This continues what was done in #29038/#30563 for Maxima.

As this ticket removes some hard-coded paths depending on SAGE_LOCAL from sagelib, it will reduce the need for patching for downstream packaging.

A possible implementation strategy goes through sage.features.Executable.

This is part of:

Taken care of in separate tickets:

CC: @kiwifb @tobiasdiez @dimpase @antonio-rojas @orlitzky @seblabbe

Component: refactoring

Keywords: sd111

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

@mkoeppe mkoeppe added this to the sage-9.3 milestone Oct 23, 2020
@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe mkoeppe changed the title Set environment for subprocesses invoked by Sage Meta-ticket: Set environment for subprocesses invoked by Sage Nov 11, 2020
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Dec 6, 2020

comment:6

Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Dec 6, 2020

Changed keywords from none to sd111

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Mar 24, 2021

comment:13

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.

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Mar 24, 2021
@mkoeppe

This comment has been minimized.

@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 18, 2021
@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 May 3, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Sep 19, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.8, sage-9.9 Jan 29, 2023
@mkoeppe mkoeppe modified the milestones: sage-10.0, sage-10.1 Apr 30, 2023
@mkoeppe mkoeppe removed this from the sage-10.1 milestone Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant