-
Notifications
You must be signed in to change notification settings - Fork 37
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
adapt to timezone-aware objects #58
base: master
Are you sure you want to change the base?
Conversation
This change seems to only be for testing files and not for datetimes produced by this library. The things it is testing seems to be from its dependency https://github.com/jborean93/smbprotocol which was fixed with jborean93/smbprotocol#252. While yes our test should be updated it should be updated so it's not using the deprecated |
In my point of view it is better for the compatibility when the library accepts also timezone-naive datetimes, so I didn't want the changes to be too widespread. Anyway, should I make more changes? Where, how? |
The changes in this PR are just for tests and not part of the actual codebase. It also continues to use the deprecated |
True, this is not user-facing, so it is not urgent to merge 🥲 . And I agree this is more of a hotfix than improvement. |
What I'm trying to say is I'm happy to merge this but it should be using the non-deprecated API |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #58 +/- ##
==========================================
+ Coverage 98.15% 98.52% +0.36%
==========================================
Files 7 7
Lines 1085 1085
==========================================
+ Hits 1065 1069 +4
+ Misses 20 16 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Python 3.12 now strongly preffers timezone-aware datetime objects and some libraries have already been adapted to that. I didn't investigate which libraries, maybe the change is only a PR and we patched it in our distribution. However, the produced datetimes are now timezone-aware (or will be in near future) and this adapts pypsexec tests to this change.