-
Notifications
You must be signed in to change notification settings - Fork 762
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
Broken typing annotations fixed #949
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #949 +/- ##
==========================================
+ Coverage 83.33% 83.41% +0.08%
==========================================
Files 13 13
Lines 1374 1381 +7
Branches 258 258
==========================================
+ Hits 1145 1152 +7
Misses 152 152
Partials 77 77
☔ View full report in Codecov by Sentry. |
Using Currently a single release of websocket-client is intended to support all Python versions that are not EOL. If you'd suggest a change in strategy to support multiple versions simultaneously, I'm open to ideas. |
If you want typing annotations valid for Python 3.8, you should write Your old |
I looked into this more, you're right. Even mypy outputs an error of "Invalid type comment or annotation" on the lines using In order to maintain backwards compatibility with 3.8, would you be willing to replace the usage of |
I've fixed the annotations, please run the checks. Or even better make checks to run automatically on commits to PRs. |
Thank you for the helpful upgrade! |
Running an app using
websocket-client
undertypeguard
produced a number of crashes due to typing annotations inwebsocket-client
being broken and not compliant to the real data types. This PR fixes those broken annotations.Fixes #934 and #948.