Remove deprecated skip_equivalent pyproj arg
#174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgrss
added a commit
to jgrss/stackstac
that referenced
this pull request
Sep 28, 2022
* Support sequence of `Item`s (gjoseph92#164) * Switch to PDM for dependency management (gjoseph92#169) * Add param links to docs (gjoseph92#170) * Automatically hide `pdm.lock` in GitHub diffs (gjoseph92#171) * Fix docs build for visualization functions (gjoseph92#172) * Fix docs build for PDM again (gjoseph92#175) * Remove deprecated `skip_equivalent` pyproj arg (gjoseph92#174) * Release v0.4.3 (gjoseph92#176) * Fixed link to USGS PDF on qa-pixel (gjoseph92#180) Co-authored-by: Gabe Joseph <gjoseph92@gmail.com> Co-authored-by: Tom Augspurger <taugspurger@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #173
Caused by pyproj4/pyproj#1077.
FYI @snowman2 since pyproj4/pyproj#824 used a
DeprecationWarning, not aFutureWarning, the warning would not have typically been displayed to users. That's probably why neither I nor anybody else noticed it.