Unpin pydantic, raise versions for pydap and h5netcdf
#559
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
Signed-off-by: Zeitsperre <10819524+Zeitsperre@users.noreply.github.com>
Signed-off-by: Zeitsperre <10819524+Zeitsperre@users.noreply.github.com>
Signed-off-by: Zeitsperre <10819524+Zeitsperre@users.noreply.github.com>
Signed-off-by: Zeitsperre <10819524+Zeitsperre@users.noreply.github.com>
Signed-off-by: Zeitsperre <10819524+Zeitsperre@users.noreply.github.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.
Pull Request Checklist:
number) and pull request (:pull:number) has been added.What kind of change does this PR introduce?
pydantic, as newer patch releases have addressed regressions.h5netcdfandpydap.DeprecationWarningmessages.Does this PR introduce a breaking change?
No.
Other information:
I'm not entirely sure why earlier releases of
pydanticwere failing, but it is entirely possible that recent changes inRavenPyhave addressed the changes that came about in version 2.12.0. Modernpydapversions appear to work perfectly fine with modernxarrayas of this writing.