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.

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

Ctrl-C with -gthread on Windows, causes uncaught IOError #50

Closed
ipython opened this issue May 10, 2010 · 2 comments
Closed

Ctrl-C with -gthread on Windows, causes uncaught IOError #50

ipython opened this issue May 10, 2010 · 2 comments
Milestone

Comments

@ipython
Copy link
Collaborator

ipython commented May 10, 2010

Original Launchpad bug 412353: https://bugs.launchpad.net/ipython/+bug/412353
Reported by: fdo.perez (Fernando Perez).

The proposed fix is, in Shell.py
try:
update_tk(self.tk)
self.IP.runcode()
time.sleep(0.01)
return True
except IOError:
return True

See for details:
http://mail.scipy.org/pipermail/ipython-dev/2009-August/005407.html

Note that with the new inputhook work, this may become completely unnecessary. But still, if we ever put out an 0.10.1 bugfix release on the 0.10 series, this fix should go in.

@fperez
Copy link
Member

fperez commented Mar 13, 2011

Catch IOError on windows with -gthread.

Closed by 8a8ad68, thanks to Pieter Cristiaan de Groot and others on the
list for the fix.

@fperez
Copy link
Member

fperez commented Mar 13, 2011

Thanks to everyone who pitched in for the fix, committed and pushed for the upcoming 0.10.2 (sorry I missed this when pushing 0.10.1 out).

fperez added a commit to minrk/ipython that referenced this issue Jul 1, 2013
fix Out in reference html output (remove non-breaking spaces from test output, since we're not emitting them  now from the conversion code).
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant