Fix datetime errors in latest Python #479
Merged
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.
Cron jobs have picked up that the
.local
property of ourAccDateTime
raises issues as it tries to do some non-tzinfo
inherited comparisons.As far as I could tell this is mostly an annoyance due to subclassing the
datetime
class. A very simple fix is to simply cast to datetime first (using our own.datetime
property) and then ask for.astimezone
as previously).PR is a bit more than that since I took the opportunity of dropping Python 3.9 support for this release (as we did with
tfs-pandas
) and solve the mess ofpytables
andnumpy 2.x
dependencies.