Set definitions for what Django and Pandas versions to use#400
Set definitions for what Django and Pandas versions to use#400christophertubbs wants to merge 1 commit into
Conversation
christophertubbs
added
the
dependencies
robertbartel
left a comment
robertbartel
left a comment
There was a problem hiding this comment.
I think in a vacuum, I'd prefer moving to Pandas 2.0, but I don't think we actually are compelled to at the moment (correct me if I'm wrong @christophertubbs). On the other hand, we do have a transitive dependency on an earlier version of Pandas pending with #394.
We could either leave this as blocked (until NOAA-OWP/ngen-cal#57 is addressed) or modify the Pandas version specified here to be something compatible with ngen-cal. Thoughts?
|
For now, I'm moving this to Blocked while we wait on the aforementioned ngen-cal issue. |
|
@christophertubbs, @robertbartel, im blocking off time on Monday to investigate the |
|
Still waiting for NOAA-OWP/ngen-cal#64 to be reviewed and then this should be unblocked. |
|
NOAA-OWP/ngen-cal#64 has been merged. Moving this to todo, now that this is unblocked. |
3 participants
We ran into an issue the other day where imported dependencies were dictating that old versions should be used. I updated some of the version definitions to ensure that more modern versions of Pandas and Django are used.