-
Notifications
You must be signed in to change notification settings - Fork 33
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
Pickle Exception.__cause__ and Exception.__traceback__ #54
Conversation
Codecov Report
@@ Coverage Diff @@
## master #54 +/- ##
==========================================
+ Coverage 88.46% 89.38% +0.92%
==========================================
Files 4 4
Lines 208 245 +37
Branches 29 42 +13
==========================================
+ Hits 184 219 +35
- Misses 15 16 +1
- Partials 9 10 +1
Continue to review full report at Codecov.
|
@ionelmc ready for review and merge |
@ionelmc I've implemented all suggestions; ready for second review. |
@ionelmc any update? Thanks |
Ooooooof sorry, I'll look later today. Looks very good so far. |
Very good, released v1.6.0 just now. |
I have not investigated, but this (c6d1796) causes test failures with pytest-parallel: kevlened/pytest-parallel#62
|
The workaround/fix is to move |
Would love to see some explanation on what's going on. |
I, too, struggle to see how importing the module inside a slave thread can be any different from importing it in the main thread. |
Likely because |
if you read the code, install isn't doing anything fancy at all, and unpickle_exception is a perfectly vanilla function defined at the top level of a globally-accessible Python module. |
Closes #53