-
Notifications
You must be signed in to change notification settings - Fork 24
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
proj cartopy dependency error #148
Comments
yeah good point on this, there is an issue with cartopy 0.19.0 that uses stale URLs for some basemap downloads. see issue #141 here. i dont think we can pin that otherwise we might run into that same issue. the proj8 issue only comes up if people want to install via pip, which means that proj8 can be installed via source or using i'm not sure a good solution here. any thoughts? |
Sorry, this is actually almost duplicate. Apparently Within pip, the solution is to install proj by source in my local machine. Conda works as a charm, unless it attempt to use inherited global packages (Any idea how to install pycsep by forcing to use the latest dependecies versions within conda forge?). I believe you are right, and is better to wait either |
this is definitely a challenge with i try to create an environment to start that is very lightweight eg, from miniconda and just install the deps within that environment. |
im looking through here. maybe there is an option that would do what you want. to be honest, ive never tested these options myself so i can't vouch for them. |
Dependency issue with latest cartopy updates (> 0.20.0) that points to newer version of proj (8.0.0), which in turn is not available through apt (7.0.0) as suggested in our installation guide (same issue on SciTools/cartopy#1912). Pip finally installs automatically cartopy==0.19.0. This makes me wonder if we should freeze some dependencies in the requirements.txt, e.g. cartopy==19.0.0, and update them as we release new pycsep versions?
The text was updated successfully, but these errors were encountered: