-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
Errors with python3.7 #431
Comments
I'm only able to reproduce this with 5.0.1 and not the top of master. |
Indeed... Sorry I mixed up 2 virtualenvs. So yes I see the same, not working on 5.0.1, but fine on I guess a new patch release is planed for soon then? Thanks a lot! |
No problem. |
Hi, any eta when a new release will be pushed? |
Closing as a duplicate of #405. @battlemidget No ETA on a release but I'll try to take a look at pending issues over the week-end. |
Well, it was a nice sunny weekend, so no progress here. |
It's been over a week, any idea on when a new release will be published? |
Almost certainly before September. |
(I could type |
#435 suggests that master isn't compatible with Python 3.7 yet. |
(which is a release blocker) |
#437 is another release blocker. |
Version 6.0 adds support for Python 3.7 and is now available on PyPI: https://pypi.org/project/websockets/6.0/#files |
Hi Aymeric,
I may be missing something, but it seems to me that the code is currently not yet compatible with python 3.7 (tested with top of master)
The best way to reproduce is the first test example of the doc:
This raises this exception:
I've seen you are doing some changes at the moment for python3.7, I will be happy to validate further changes. Did not catch it earlier because we were stuck with the
pyyaml
lib even earlier in our deployment... They are pushing deprecation very strongly!The text was updated successfully, but these errors were encountered: