brendanjmeade
commented
3 years ago Trying to install following: https://anaconda.org/conda-forge/spherical-geometry and seeing:
conda install -c conda-forge spherical-geometry Collecting package metadata (current_repodata.json): done Solving environment: failed with initial frozen solve. Retrying with flexible solve. Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source. Collecting package metadata (repodata.json): \ WARNING conda.models.version:get_matcher(537): Using . with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 3., but conda is ignoring the .* and treating it as 3 done Solving environment: failed with initial frozen solve. Retrying with flexible solve. Solving environment: | Found conflicts! Looking for incompatible packages. This can take several minutes. Press CTRL-C to abort. failed UnsatisfiableError: The following specifications were found to be incompatible with the existing python installation in your environment:
Specifications:
- spherical-geometry -> python[version='2.7.|3.5.|3.6.*|>=2.7,<2.8.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0']
Your python: python=3.8
If python is on the left-most side of the chain, that's the version you've asked for. When python appears to the right, that indicates that the thing on the left is somehow not available for the python version you are constrained to. Note that conda will not change your python version to a different minor version unless you explicitly specify that.
The main thing here is a an optimization that cuts the runtime of
assign_pointsdown by ~10x from a couple minutes on the global model down to about 5-10 seconds. Before doing a full point in spherical polygon test, we first check if the point lies in the bounding box surrounding that polygon. Especially on the global model, this brings the runtime back down into "playing around" territory from "kind of annoying to play around" territory.A couple other small things:
setup.cfgwhich specifies flake8 parameters.pyproject.tomlwhich is the standard location to putpytestdefault parameters. Yeah, the fragmentation of file names for Python tool configuration files is kind of annoying. I think pyproject.toml is intended to be the eventual consolidated location, but several tools like flake8 haven't migrated yet.