Skip to content

Support serializing datetimes with datetime.timezone #914

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

Merged
merged 6 commits into from
Apr 13, 2023

Conversation

robsdedude
Copy link
Member

This enables users to use python's standard datetime.timezone for constant utc-offset timezones (only for serialization, data coming back from the server will continue to use pytz).

This change also enables pandas 2 as pandas switched over to datetime.timezone for constant offset timezones
https://pandas.pydata.org/docs/dev/whatsnew/v2.0.0.html#utc-and-fixed-offset-timezones-default-to-standard-library-tzinfo-objects

This enables users to use python's standard `datetime.timezone` for constant
utc-offset timezones (only for serialization, data coming back from the server
will continue to use `pytz`).

This change also enables pandas 2 as pandas switched over to `datetime.timezone`
for constant offset timezones
https://pandas.pydata.org/docs/dev/whatsnew/v2.0.0.html#utc-and-fixed-offset-timezones-default-to-standard-library-tzinfo-objects
The driver may not depend on 3rd party libraries when just being loaded.
This has to be done dynamically when needed to not break pip install which loads
the driver to figure out the version number (and potentially other meta data).
@robsdedude robsdedude merged commit 13e6d98 into neo4j:5.0 Apr 13, 2023
@robsdedude robsdedude deleted the support-pandas-2 branch April 13, 2023 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants