Pin morecantile dependency to < v3.0.0 #389
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There have been some major changes in morecantile in version 3.0.0 (see https://github.com/developmentseed/morecantile/issues/620). This means that morecantile has switched to using CRS objects from pyproj rather than CRS objects from rasterio.
This was causing titiler to fail when installed with morecantile 3.0.0 - which was happening automatically when I created a new environment and just installed titiler, because there was no version specification in the setup.py.
This PR adds a version spec to the dependency, ensuring that morecantile stays below version 3.0.0.
(I did also try pinning morecantile to at least version 3.0.0, and updating the titiler code to use the pyproj CRS objects - but i got warnings from pip that various other packages had pinned morecantile to <3.0.0, so it's probably best to stick with that for the moment.)