-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix: cleared multiple deperecation notices #821
Conversation
63ab349
to
5907480
Compare
Test Results294 tests 294 ✅ 3s ⏱️ Results for commit 0518989. ♻️ This comment has been updated with latest results. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #821 +/- ##
=======================================
Coverage 98.99% 98.99%
=======================================
Files 11 11
Lines 1293 1293
=======================================
Hits 1280 1280
Misses 13 13 |
5907480
to
d0fc96c
Compare
Signed-off-by: Tomer Figenblat <tomer@tomfi.info>
d0fc96c
to
0518989
Compare
@YogevBokobza would be nice if you can validate the changed method in this PR using a real device |
@thecode, I added related information to the PR's body. I should have done that when I opened the PR. |
Description
When I ran some tests, I noticed a couple of deprecation notices:
datetime.datetime.utcnow()
, the resolution is specified in the deprecation notice:datetime.datetime.now(datetime.UTC)
.ssl.SSLContext()
, since version 3.10, SSLContext, the default value for the SSLContext function, PROTOCOL_TLS, was deprecated in favour of PROTOCOL_TLS_CLIENT and PROTOCOL_TLS_SERVER.Checklist
Additional information