-
Notifications
You must be signed in to change notification settings - Fork 168
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
Support for Tornado 6.x #68
Comments
Thanks for cutting this. There is a long history of communication on Jupyter and Gremlin about this issue Gremlin discussions: Jupyter discussions The issue preventing us from upgrading as I understand it, is that newer versions of tornado do not allow multiple event loops. Since Jupyter uses tornado, it creates an event loop when a kernel is made, so then when gremlin-python tries to also make one, it no longer can. Tornado throws an exception stating that multiple event loops cannot be made. This change was introduced in Tornado major version 5 This fix is unfortunately non-trivial, but in the meantime, there is a package that can be installed to help mitigate this issue. Please note, we have not tested or verified the stability of this workaround, so use at your own risk. You can install the package nest-asyncio which can be used to patch tornado to allow nested loops.
Hope this helps! |
Adding a note that as of Apache TinkerPop 3.5.0, the Gremlin Python client no longer uses Tornado. AIO HTTP is used instead. Once graph-notebook moves up to that TinkerPop level the Tornado issues should be resolved as graph-notebook will no longer have any Tornado dependencies. |
Hi @jeffmaley, just checking in in case you are still following this. As of Release 3.0.7, setup requirements have been updated to remove the old pinned Tornado version, and upgrade to Closing as the ask is resolved, please feel free to re-open if you have any further questions or concerns. |
Is your feature request related to a problem? Please describe.
Tornado 4.5.3 is older and it is tough to get it approved in higher-security environments.
Describe the solution you'd like
I would like to see tornado 6.x supported.
Describe alternatives you've considered
We're dealing with the existing requirement, but it presents internal complexities.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: