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

handle KeyboardInterrupt with %gui asyncio #281

Merged
merged 4 commits into from
Nov 27, 2017
Merged

handle KeyboardInterrupt with %gui asyncio #281

merged 4 commits into from
Nov 27, 2017

Commits on Nov 23, 2017

  1. handle KeyboardInterrupt with %gui asyncio 

    when interrupted, re-enter eventloop and don't close it

only close the eventloop when we are done for good.

Also avoid any cleanup when someone else is already running the eventloop (e.g. tornado 5).
    @minrk
    minrk committed Nov 23, 2017
    Configuration menu
    Copy the full SHA
    f3c41be View commit details
    Browse the repository at this point in the history

  2. show tracebacks in execute tests 

    easier debugging when there are errors
    @minrk
    minrk committed Nov 23, 2017
    Configuration menu
    Copy the full SHA
    57ec48c View commit details
    Browse the repository at this point in the history

  3. test interrupting asyncio eventloop

    @minrk
    minrk committed Nov 23, 2017
    Configuration menu
    Copy the full SHA
    e595d52 View commit details
    Browse the repository at this point in the history

Commits on Nov 27, 2017

  1. check for loop.shutdown_asyncgens before calling it 

    new in py36
    @minrk
    minrk committed Nov 27, 2017
    Configuration menu
    Copy the full SHA
    fa814da View commit details
    Browse the repository at this point in the history