-
Notifications
You must be signed in to change notification settings - Fork 687
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
Top level await #1553
Comments
We need to get an ipython upgrade to allow pyppeteer working, this will take a bit of time. In the meantime I've been downgrading tornado to allow the asyncio to work. from google.colab import output
with output.temporary():
!pip install pyppeteer tornado==4.5.3
!apt update
!apt install chromium-chromedriver
import os
import signal
# Kill the process to restart with the older tornado version.
os.kill(os.getpid(), signal.SIGTERM) |
@blois Thanks! That worked |
For those who need TOP LEVEL AWAIT LITERALLY. Upgrade your ipython and ipykernel, because it's of the old version that does not support this feature.
After this restart runtime and you're good to go. |
Internal tracking: b/207773817 |
Describe the current behavior:
I'm having some trouble running pyppeteer in colab (which I'm using to communicate with a reinforcement learning environment called Derk's Gym). It's using async/away, and from what I understand the "normal" way to make that work is to use nest_asyncio. But pyppeteer unfortunately has a bug which prevents it being used with nest_asyncio.
From what I gather ipython/jupyter supports top level awaits, which would solve this problem. Is that something colab has on the roadmap? Or are there other solutions to running async code in colab that I'm not aware of?
Describe the expected behavior:
Would be great if pyppeteer worked :)
Link (not screenshot!) to a minimal, public, self-contained notebook that
reproduces this issue (click the Share button, then Get Shareable Link):
The text was updated successfully, but these errors were encountered: