-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fix IPython kernel-related cleanup #188
Conversation
Codecov Report
@@ Coverage Diff @@
## master #188 +/- ##
=========================================
Coverage ? 45.73%
=========================================
Files ? 147
Lines ? 4476
Branches ? 506
=========================================
Hits ? 2047
Misses ? 2384
Partials ? 45
Continue to review full report at Codecov.
|
…ove some unnecessary cleanup
…tdout caching to init_kernel.
I'm getting a
|
The |
I have no additional comments on this PR and any questions I had have been addressed. |
# the existence and content of those messages, and for hiding the | ||
# logger output during the test run). | ||
|
||
class ListHandler(logging.Handler): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels generally useful, and may belong in apptools.logging
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code is now gone; I'll try to remember to open an apptools issue for this and for the output stream capturing before I close this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened enthought/apptools#96
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good, with the caveat that I haven't done the digging into IPython to ensure that clean up is doing all the right things, but it looks reasonable and the tests seem comprehensive enough.
Furthermore, I think that architecturally it is the right sort of thing.
There's something a bit fragile with the current tests and latest
|
Variant on the intermittent failure:
|
@rahulporuri @corranwebster I think this is ready. I'm still investigating the intermittent failure, but it may make most sense for the fix for that to go into a separate PR. |
This turned out to be an |
I think the easiest solution is to not towork around it and wait for ipykernel 5.1.3 (or later) to be released. Merging! |
This PR shows a proof of concept for fixing cleanup issues in the InternalIPKernel and associated plugin. Should eventually address issues #94, #185, #186 and #187.
Currently WIP, so making this a draft PR. Opening a PR now (a) to get CI feedback and (b) to have a place outside the code to record things that are still to do.Ready for review.
To do:
rprint
andrprinte
, which are still used in some versions of the code).ResourceWarning
fromtest_shutdown_closes_console_pipes
Note: commit history is very messy. Please be sure to squash and merge.