Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address pandas warnings about future pyarrow requirements #682

Merged
merged 6 commits into from
Feb 20, 2024

Conversation

bpkroth
Copy link
Contributor

@bpkroth bpkroth commented Feb 19, 2024

Simply makes sure that pyarrow is available in the conda environment to make some warnings go away.

Assumes that future versions of pandas will declare their own dependency on pyarrow and this can be removed.

Also includes changes from #680

@bpkroth bpkroth requested a review from a team as a code owner February 19, 2024 21:01
@bpkroth bpkroth added the ready for review Ready for review label Feb 19, 2024
@motus motus enabled auto-merge (squash) February 20, 2024 19:36
@motus motus merged commit 0a0ed73 into microsoft:main Feb 20, 2024
12 checks passed
@bpkroth bpkroth deleted the pyarrow-warnings branch February 20, 2024 20:39
bpkroth added a commit that referenced this pull request Feb 20, 2024
Addressing some warnings from pandas about datetime conversions and
deprecated and future strict behavior.

One issue we currently have is that a timestamp produced by a client may
be in a different timezone or lack timezone info from what that receiver
parses before injecting it into the DB.

This starts to at least attempt to work on those conversions for
consistency.

Currently also includes changes from #682 and #680
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for review Ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants