-
Notifications
You must be signed in to change notification settings - Fork 224
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
Offline installation using pip no longer works #2097
Comments
This comment is confusing to me because I tried |
Here are a series of commands I run without internet access:
Running |
It seems there are two different issues here.
@maxrjones Are you talking about the first one? |
Yes, I was talking about the first one. #2097 (comment) makes sense as an explanation, as I had setuptools installed in my environment. |
I'm inclined to close the issue to reduce the number of our opened issues, mainly because:
Closing the issue but feel free to reopen it if necessary. |
Description of the problem
Originally posted by @maxrjones in #1848 (comment)
A downside here is that
make install
no longer works without internet access, even if setuptools>=64 is installed in the environment. I'll do some more searching for a workaround but if anyone knows a solution that would be helpful.Originally posted by @weiji14 in #1848 (comment)
I tried disconnecting and used
pip install --no-deps --no-build-isolation --editable=.
which seems to work offline (presumably it manages to pick up a pre-downloadedsetuptools>=64
). However, it results in a editable version namedpygmt-0.0.0
. Maybe the offline feature can be raised upstream to PyPA?Originally posted by @seisman in #1848 (comment)
It's unrelated to this PR. Offline
make install
worked for pygmt<=0.2.0 and started to fail since v0.3.0, in which we switched from versioneer to setuptools_scm (https://www.pygmt.org/dev/changes.html#id47). So it's likely a problem for setuptools_scm.This command gives the correct version for pygmt <= 0.6.0 but results in
pygmt-0.0.0
for pygmt v0.7.0. Not sure if it's caused by changes in #1945.The text was updated successfully, but these errors were encountered: