[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

Zachary Ware added the comment: With 2.7 now EOL, I'm closing the issue. -- nosy: +zach.ware resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

Change by Serhiy Storchaka : -- type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

Antoine Pitrou added the comment: I'm guessing the backport may end up non-trivial. Do you want to try submitting a PR for it? -- ___ Python tracker

[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

Changes by Serhiy Storchaka : -- nosy: +pitrou ___ Python tracker ___ ___

[issue31297] Unpickleable ModuleImportError in unittest patch not backported to 2.7

New submission from Rachel Tobin: When running the unittest runner in parallel with an module import error present in your code, this exception is raised: _pickle.PicklingError: Can't pickle : attribute lookup ModuleImportFailure on unittest.loader failed unittest should be raising standard