-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Remove use of SAGE_LIB in sage.misc #33821
Comments
Dependencies: #33793 |
Commit: |
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
The failure in "Build&Test" is in |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:11
You have a repeated block
If it ends up being useful in more than two files, should it be factored somewhere? |
comment:13
Good suggestion, done now |
comment:14
LGTM, let's ship it. |
Reviewer: François Bissey |
comment:15
Thanks! |
Changed branch from u/mkoeppe/remove_use_of_sage_lib_in_sage_misc to |
We delay importing
lazy_import_cache
until a lazy star import is done (which the Sage library never does).We change two copies of essentially the same code that tries to use
SAGE_SRC
andSAGE_LIB
to turn a source filename to a qualified package name so thatsage.env.SAGE_SRC
cannot be imported or is emptySAGE_LIB
by usingsage.__path__
(to handle namespace packages correctly)part of Meta-ticket #33037 (Remove use of
SAGE_LIB
andSAGE_EXTCODE
variables)Depends on #33793
CC: @kiwifb @antonio-rojas @tornaria
Component: refactoring
Author: Matthias Koeppe
Branch/Commit:
748d9fb
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/33821
The text was updated successfully, but these errors were encountered: