I will now ask about scipy/sparse on the scipy mailing list. That seems to be the source of my current problem. I just tried rebuilding and re-installing from source, but _sparsetools.so didn't change.
Ryan
On Thu, May 15, 2008 at 2:42 PM, Ryan Krauss ryan...@gmail.com wrote:
I am continuing to plug along. I guess it is a good thing my desktop installation went smoothly or I might have bailed out. I went into my package manager and installed umfpack and then re-bulit and re-installed umpack.py. I got over my previous hurdle, but now came up with a new one:
/usr/lib/python2.5/site-packages/scipy/sparse/sparsetools.py in csr_matvec(*args) 590 npy_clongdouble_wrapper Xx, npy_clongdouble_wrapper Yx) 591 """ --> 592 return _sparsetools.csr_matvec(*args) 593 594 def csc_matvec(*args):
: 'module' object has no attribute 'csr_matvec' WARNING: Failure executing file: On Thu, May 15, 2008 at 2:28 PM, Ryan Krauss ryan...@gmail.com wrote:
I have updated pyparsing on my laptop and am past that problem. I have a new one though:
: global name 'UMFPACK_CONTROL' is not defined WARNING: Failure executing file: coming from
/usr/lib/python2.5/site-packages/scikits/umfpack/umfpack.py in __init__(self, family, **kwargs) 283 self.family = family 284 print('just before UMFPACK_CONTROL') --> 285 self.control = nm.zeros( (UMFPACK_CONTROL, ), dtype = nm.double ) 286 print('just after UMFPACK_CONTROL') 287 print('UMFPACK_CONTROL='+str(UMFPACK_CONTROL))
(the line numbers are probably a bit off since I added some print statements to help me debug).
It seems the problem stems from here:
umfDefines = updateDictWithVars( {}, _um, 'UMFPACK_.*' )
(around line 180 of umfpack.py)
because: _um = None
after this try/except clause at the beginning of umfpack.py: try: # Silence import error. import _umfpack as _um except: _um = None
both computers have umpack installed from scikits svn. And both have the same version of scipy from svn a month or so ago. But my desktop allows import _umfpack and my laptop doesn't.
Any help? Where does _umfpack come from?
Ryan
On Thu, May 15, 2008 at 11:50 AM, Ryan Krauss ryan...@gmail.com wrote:
I must not have the same version installed on both computers. Weird. I will update and report back.
On Thu, May 15, 2008 at 10:54 AM, Robert Cimrman cimr...@ntc.zcu.cz wrote:
Ondrej Certik wrote:
as you can see, there are 3 calls to Optional. Try to run each of them in pdb exactly as you did for the last one. I am sure some will blow up. If not, run the whole line in pdb. Post here the results, I'll help you further. It may well be a bug in pyparsing, but first we need to figure out how to reproduce it besides just your laptop.
Yes, pyparsing is the problem, but it is not a bug. Optional class was made callable very recently -> all that needs to be done is to install the latest version of pyparsing.
thanks for giving assistance when I was away :) r.
>>