-
-
Notifications
You must be signed in to change notification settings - Fork 519
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-env, sage.env: Remove unused environment and Python variables SAGE_ETC, SAGE_INC #32045
Comments
comment:1
I don't know how to deprecate global variables, so help is welcome. |
comment:2
Basically What do you think about this solution? |
comment:3
Probably not worth doing this. Let's just document it as deprecated. |
comment:4
I thought I was (ab)using |
comment:5
Do you think people will catch on? Then again, they will catch on, once it's gone and then they can look up the release notes. So maybe just document it. |
comment:6
I don't really think anyone will notice
OK, there is one thing that need attention
But |
comment:7
I originally just meant that we should deprecate the Python variables in But we could, of course, also just remove the environment variables, too. Any user package that uses them should certainly be updated anyway to become properly pip-installable. |
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Commit: |
comment:11
This looks okay to me. @kiwifb, how about you? |
comment:12
Replying to @jhpalmieri:
Yes, it looks perfectly fine to me. We are cutting dead branches really. |
Reviewer: François Bissey, John Palmieri |
comment:14
Thanks! |
These variables are unused (and do not have a legitimate use any more).
If there are user packages around that use it... they will need repackaging as pip-installable packages anyway.
CC: @jhpalmieri @kiwifb @kliem @dimpase
Component: build: configure
Author: Matthias Koeppe
Branch/Commit:
6012b45
Reviewer: François Bissey, John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/32045
The text was updated successfully, but these errors were encountered: