running sys.exit on an engine results in an error trying to handle SystemExit
Bug #400600 reported by
Vishal Vatsa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
IPython |
Fix Committed
|
Medium
|
Brian Granger |
Bug Description
To replicate, start an cluster and do:
from IPython.kernel import client
tc = client.
code = "import sys; sys.exit(0)"
task = client.
id = tc.run(task)
r = tc.get_
r.failure.
"Traceback (most recent call last):\nFailure: exceptions.
I know, should not be doing sys.exit, but if you do this error is really hard to diagnose the actual problem.
Would the attached patch more sense?
Since the Interpreter obj. indeed does not have a resetbuffer() method.
Changed in ipython: | |
status: | New → Incomplete |
importance: | Low → Medium |
milestone: | none → 0.11 |
Changed in ipython: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Brian, I'm changing this one to 'in progress' because there seems to be work on it already, including Vihal's patch. If by any chance you've already merged it, just set it to 'fix committed'.
I'm doing this because I want to leave behind on LP all bugs that are incomplete, invalid, or fix committed/released, so we start on GH only with active bugs. So if I leave this one as 'incomplete', it would get left behind with other ones that are marked incomplete because they are simply missing enough information to even know if they are real bugs.