#8785: avoid subtle interaction between importing multiprocessing and twisted
----------------------+-----------------------------------------------------
Reporter: was | Owner: jason
Type: defect | Status: new
Priority: major | Milestone: sage-4.4.1
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------+-----------------------------------------------------
It turns out that on some platforms, importing multiprocessing, then
twisted, leads to an "int object is not callable" TypeError. This breaks
devel/sage/sage/all.py's quit_sage function, causing a big traceback at
exit. This could also cause great confusion for people writing a program
that uses @parallel('multiprocessing') followed by anything involving
twisted.
A simple fix is to import the relevant part of twisted before using
multiprocessing in @parallel. The attached patch does this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8785>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
