#6503: remove the pyprocessing spkg from sage, then sort out any fallout that
results
------------------------+---------------------------------------------------
Reporter: was | Owner: mabshoff
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-4.3.2
Component: packages | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by jhpalmieri):
First, we need a patch to the sage library changing any remaining imports
of "processing" to "multiprocessing"; this involves changes to
parallel/multiprocessing.py, plus perhaps changing the name of that file
(so that in parallel/decorate.py, a line like {{{import multiprocessing}}}
means import parallel/multiprocessing.py, while in
parallel/multiprocessing.py, a line like {{{from multiprocessing import
Pool}}} means to import the Python multiprocessing module).
The file SAGE_ROOT/devel/sage/setup.py also imports from the processing
module, so that needs to be changed.
Also, as awebb suggests, the api seems to have changed: when I make these
changes and run doctests on sage/parallel/, I get errors like
{{{
AttributeError: 'Pool' object has no attribute 'imapUnordered'
}}}
After making the appropriate changes, perhaps we should test everything by
moving the pyprocessing files out of SAGE_ROOT/local/lib/python/site-
packages/ to make sure they're not being loaded?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6503#comment:5>
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.