-
Notifications
You must be signed in to change notification settings - Fork 2
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
fragile SAGE_LIB in setup.py #5
Comments
@videlec do you have any suggestion for fixing this? Importing SAGE_LIB from sage.env is fine for just doing |
By providing the The You could possibly ask the question on sage-devel as I am not an expert of these Python packaging subtleties. |
The discussion at pypa/pip#5033 is relevant. |
Also pypa/pip#6718 |
I am still looking into this but it appears it is not possible to bypass the build isolation from any configuration file. It seems to be an explicit intention in the current pip development that package authors should not be able to do this, only end users.
What I have tried and unfortunately doesn't work is to use something like cmd = "import sage; from sage.env import SAGE_LIB; print(SAGE_LIB)" It works from a standard python prompty but somehow the isolated environment that pip creates makes it so that the sage library is not found even from within the sage executable... I still haven't asked on sage-devel but will try to do that soon. I just wanted to try all options I could think of myself first... |
@videlec What do you think about Matthias Koeppes response (https://groups.google.com/g/sage-devel/c/QtfFtjdePcY)? I am thinking that maybe I should aim at an install through: |
It is a solution but not great. Most users won't use version |
I understand that but I don't know of any perfect solution. The most straightforward solution would be to go against PEP517 and delete pyproject.toml so pip uses the legacy build backend without build isolation. This would probably work for at least a few years until the pip developers deprecate it. Another more complicated option might be to setup some kind of buildbot to make wheels for as many platforms as possible. Since pip prefers installs from existing wheels before source distributions that should make it possible for most users to just do |
The assumption about the localtion of
SAGE_LIB
might be wrongOn my system the compiled version of sage does not satisfy the above
Part of openjournals/joss-reviews#3996
The text was updated successfully, but these errors were encountered: