FIX: register drivers on import #145
Merged
Conversation
This file contains hidden or 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
Contributor
|
thanks a lot for the fix @brendan-ward . Is there any plan to release a new version of |
weiji14
added a commit
to GenericMappingTools/pygmt
that referenced
this pull request
Jul 9, 2024
Trying to solve `pyogrio.errors.DataSourceError: No driver registered` error by forcing driver registration. Xref geopandas/pyogrio#145
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.
Resoves #144
This moves driver registration to the import step. We were not using it consistently across all internal functions, and this seemed the best way to make sure it was done up front and not repeated.