Elliott Sales de Andrade

Python 2 docs seem to be okay again.

There's some previous discussion in #476, looks like.

Proj and GEOS are C libraries, not the Python `proj`/`geos` you installed. Is there a reason you aren't using `conda` to install a pre-build Cartopy?

> (base) C:\Users\barok>conda install -c conda-forge cartopy You should avoid messing with the base environment and create a new one in which you install everything you need in a self-contained...

I've added a test, pared down from the oceans feature to the limit of what's needed to trigger the error. I tried running the tests a few times on `master`...

Well, it didn't fail for me in testing, but I didn't try the older versions...

OK, it does fail with 2.7 locally, so I will try and investigate.

Well, I'm a bit confused; the values of the points are going in the same, and the init strings going into proj are the same, but somehow `pj_transform` in `CartesianInterpolator::project`...

Oops, apparently I missed the obvious that I was not running the same versions of Proj!

IIRC, this is difficult to get working for both versions of Proj, since they return different values. I think this can't move forward until we bump minimum Proj requirements.