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.
Description
Currently
pyproj
is still pinned toproj
9.3.0 (for example). Howeverproj
recently released9.3.1
( conda-forge/proj.4-feedstock#140 ), whichcuproj
is pulling in at the moment. Sinceproj
pins to the patch version in itsrun_exports
, building against9.3.1
meanscuproj
would need exactly9.3.1
at runtime. This makes it incompatible with everything else, which is still pinned toproj
9.3.0
. Embedded screenshot below to highlight thisSo for now just manually pin
proj
to9.3.0
to buildcuproj
with a consistentproj
version to resolve conflictsThis issue should clear up once to
proj
9.3.1
migration ( conda-forge/conda-forge-pinning-feedstock#5226 ) completes. Then we can bump this or drop it as we see fit thenChecklist