Error on Install - Unable to determine GEOS version

[ssmithClimate]

I'm getting an error when installing using miniconda on macOSX (10.14.6 Mojave).

I've installed using miniconda (v 4.8.3) and that part ran without error.

But when I try to install ESMValTool using:
pip install -e '.[develop]'

I get the following error:

Collecting cartopy
  Downloading Cartopy-0.17.0.tar.gz (8.9 MB)
     |████████████████████████████████| 8.9 MB 2.4 MB/s 
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/miniconda3/bin/python /opt/miniconda3/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/tmpzaloyg9b
       cwd: /private/var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/pip-install-ol6z8v2c/cartopy
  Complete output (3 lines):
  setup.py:171: UserWarning: Unable to determine GEOS version. Ensure you have 3.3.3 or later installed, or installation may fail.
    '.'.join(str(v) for v in GEOS_MIN_VERSION), ))
  Proj 4.9.0 must be installed.
  ----------------------------------------
ERROR: Command errored out with exit status 1: /opt/miniconda3/bin/python /opt/miniconda3/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/tmpzaloyg9b Check the logs for full command output.

When I look into this, it appears that its installed.

e.g.,

/opt/miniconda3/envs/esmvaltool/lib/libgeos-3.7.2.dylib

is present.

[valeriupredoi]

it's not geos the problem but proj4 https://anaconda.org/conda-forge/proj4 - looking at your trace I can see you are not working in a pre-built esmvaltool environment - have you created it and conda activate it? Since if either of these steps have not been performed then proj4 will not be in the installation path, can you pls post the following output:

which python
conda env list
conda list geos
conda list proj4

cheers 🍺

[ssmithClimate]

I finally got it to build. I'm not 100% sure, but might have been I didn't activate first.

[valeriupredoi]

cool! good to know it still works fine on OSX (I haven't tested that in a while), cheers for the heads up 🍺

[ssmithClimate]

@valeriupredoi What would be helpful, in the installation page, for non-python folks like myself, is to change the wording "You can activate the environment using the command:" to something such as "You should then activate the environment using the command:".

[valeriupredoi]

good call, cheers, will put that in the doc 🍺

[valeriupredoi]

#1634

[ssmithClimate]

Useful info in the PR. Looked like this change wasn't there yet...

"You can activate the environment using the command:" ->
"You must then activate the environment using the command:"
(Maybe also put on its own line.)

[valeriupredoi]

just tagged you in the PR at the line that changed 😁