-
Notifications
You must be signed in to change notification settings - Fork 394
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
Basemap install failing issue in MacOS #547
Comments
Hi @SongJaeIn! It looks like the problem is coming from the current build dependency definition in the Your installed Probably the implementation in |
@SongJaeIn Can you try installing from the latest commit in the repository? You can do:
After installing, I also recommend you do the simple test: from mpl_toolkits import basemap to ensure that the |
Ok so my changes seem to break the current GitHub workflows... I will need to edit the |
with your help, installation of Basemap was successful
above is the error. |
@SongJaeIn Can you try once again with the same command? I have just updated the
so now your computer should try to build
|
@SongJaeIn By the way, this |
@molinav Now it works perfectly. Thank you very much. |
Great to hear that, @SongJaeIn! When I get some more time, I will prepare a patch release v1.3.4 with this correction and then you will be able to install |
@molinav I have installed Basemap -1.3.6+dev but when I try to test Basemap in Anaconda it says 'module not found' I have Mac with M1-max running Ventura 13.0.1 Appreciate if you can advise. thanks |
Hi @ihaseeburrehman! I am not sure if I am understanding the issue. Do you have separate installations of Python, a normal one (e.g. from Homebrew, I assume Miniconda based on the The installation procedure for Miniconda and Anaconda should be the same in both cases on MacOS with M1. Since there are no precompiled wheels or conda packages for MacOS M1, you need to install python -m pip install basemap or it is even better if you install the dependencies manually with python -m pip install --no-deps basemap Since you were able to install |
Thanks for the additional feedback, @ihaseeburrehman. The issue is that
The Python installations do not share packages, each has its own installation path. To have You can check where Python is pointing to with: command -v python |
I struggling with installation of basemap in anaconda. it says "could not built wheels for basemap." it similar issue reported in #547 I also set the environment for geos but not able to install, any suggestion ? |
Hi @molinav Thanks for your feedback . see the attached the picture. |
Hi @molinav, I tried installing basemap using the commands given above:
but receive the same error: Collecting basemap-data<1.4,>=1.3.2 (from basemap->ezgpx) Any ideas? Should I start a new issue? |
Hi @dvvilkins! You can check if the issue is the same as described in #583. The latest Cython 3.0.0 conflicts with the current |
I am creating MacOS ARM64 wheels locally before I publish them into PyPI. Is somebody with MacOS ARM64 willing to try them? Then I would be sure that what I am uploading to PyPI is actually working (I am not that experienced with MacOS). I would need to know the target Python that you are using. The wheels are bundling GEOS 3.6.5, so there would be no need to install anything manually apart from the |
@molinav I have MacOS ARM64 and am having trouble installing basemap because of the issues described above. Would be happy to try it out, I'm on Python 3.9.7. |
Thanks @tamidodo! I will try to have the wheels ready by end of today. I will attach them here, just with ".zip" extension instead of ".whl" due to GitHub limitations on the message attachments. What is the environment in which you use Python? From python.org installer, from pyenv+homebrew, from Anaconda/Miniforge? |
Sounds good, I use Anaconda. |
@tamidodo Sorry for the late reply, I was busier than expected. I attach here the current wheel file for Python 3.9 (you need to remove the .zip at the end after downloading): Since you are working with Anaconda, I would suggest to install this wheel without the dependencies, and afterwards install the dependencies manually with
The wheel bundles its own precompiled GEOS dylib, which only depends on system libraries, so I hope it works for you without any tweaking. I am happy to hear any feedback from you! |
@tamidodo I also get the same error as you when I create a new virtual environment, but in my case it is caused by the
There is a couple of differences in my environment with respect to yours: Python 3.9 is installed from the official Python website (universal2 installer), and I am using simple Python virtual environments and Some possible things I can be thinking of:
|
I have just tested with
I will try now with Anaconda or Miniforge and check. |
I have just tested with Anaconda downloaded from their website (arm64 installer). I created an environment
And then I have tried to install
|
Sorry for the delay, been busy with holiday things but this was a lovely Christmas surprise! This was what it was, my Anaconda installed Python for x86_64. Got the correct python for arm64 from miniforge and had no issues installing the wheel and getting it running! Thank you for your work on this, seems good to go! |
@tamidodo One very last update, I managed to prepare the
And then a simple import test:
I will be closing the issue, since we have |
Hi, I tried to install Basemap via pip in Mac OS, but I have encountered an error.
I also tried with another version (1.3.0), but those resulted in another error related to GEOS (it is installed and the environment variable is set correctly though).
Really appreciate your effort on this outstanding tool and thank you in advance for your support.
following is the log for installation of v 1.3.3:
$pip install basemap
DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at Homebrew/homebrew-core#76621
Collecting basemap
Using cached basemap-1.3.3.zip (155 kB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [553 lines of output]
Ignoring numpy: markers 'python_version >= "3.10"' don't match your environment
Ignoring numpy: markers 'python_version == "2.6" or (python_version >= "3.2" and python_version <= "3.3")' don't match your environment
Ignoring cython: markers 'python_version == "3.2"' don't match your environment
Collecting setuptools
Downloading setuptools-63.4.1-py3-none-any.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 7.2 MB/s eta 0:00:00
Collecting wheel
Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Collecting numpy==1.16.6
Using cached numpy-1.16.6.zip (5.1 MB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting cython<3.1,>=0.29
Using cached Cython-0.29.32-py2.py3-none-any.whl (986 kB)
Building wheels for collected packages: numpy
Building wheel for numpy (setup.py): started
Building wheel for numpy (setup.py): finished with status 'error'
error: subprocess-exited-with-error
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
WARNING: There was an error checking the latest version of pip.
And, following is NumPy info:
$pip show numpy
Name: numpy
Version: 1.23.1
Summary: NumPy is the fundamental package for array computing with Python.
Home-page: https://www.numpy.org
Author: Travis E. Oliphant et al.
Author-email:
License: BSD
Location: /usr/local/lib/python3.9/site-packages
Requires:
Required-by: cftime, h5py, matplotlib, netCDF4, pandas, ray, scipy, wradlib, xarray
Next is pip, and python versions:
$pip -V
pip 22.1.1 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)
The text was updated successfully, but these errors were encountered: