Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Broken when using cherrypy>=11.1.0 #15

Closed
matt-hammond-001 opened this issue Nov 23, 2017 · 5 comments
Closed

Broken when using cherrypy>=11.1.0 #15

matt-hammond-001 opened this issue Nov 23, 2017 · 5 comments

Comments

@matt-hammond-001
Copy link
Contributor

CII or TS servers are currently broken when using cherrypy>=11.1.0

This appears to be an upstream problem. See Lawouach/WebSocket-for-Python#235
@matt-hammond-001
Copy link
Contributor Author

Temporary workaround is to use cherrypy>=10.0.0,<=11.0.0

$ pip install "cherrypy>=10.0.0,<=11.0.0"

matt-hammond-001 added a commit that referenced this issue Nov 24, 2017
@matt-hammond-001
Temporary fix for #15
f5bb1b1
@matt-hammond-001 matt-hammond-001 mentioned this issue Nov 24, 2017
Closed
@matt-hammond-001
Copy link
Contributor Author

Release 0.5.1 contains the temporary workaround, but will leave this ticket open until the upstream issue is resolved and the workaround can be reverted.

@matt-hammond-001
Copy link
Contributor Author

The underlying cause is pypa/pip#4887

@matt-hammond-001
Copy link
Contributor Author

Now works for ws4py==0.4.3 and CherryPy==13.1.0

@matt-hammond-001
Copy link
Contributor Author

Will leave on current fix that requires CherryPy >= 10.0.0 and <= 11.0.0.

Please raise an issue if this causes problems for your project.

@PeterHamilton PeterHamilton mentioned this issue Mar 14, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matt-hammond-001