[SciPy-user] what's wrong with radom.multivariate_normal

Pearu Peterson pearu at scipy.org
Fri Dec 16 06:35:58 CST 2005



On Fri, 16 Dec 2005, Robert Kern wrote:

> I've just commited my changes to scipy_core. Now, I must be missing something,
> because scipy.linalg still exists and is the same module as scipy.basic.linalg,
> not scipy.linalg from full scipy no matter how I try to import things. I'm using
> a regular install; not eggs.

scipy.basic.linalg is exposed as scipy.linalg via scipy/basic/info.py.
When full scipy is installed, scipy.linalg is reset to scipy.linalg (from 
full scipy):

In [1]: import scipy
Skip importing scipy packages (NO_SCIPY_IMPORT=1)

In [2]: scipy.linalg
Out[2]: <module 'scipy.basic.linalg' from 
'/usr/local/lib/python2.3/site-packages/scipy/basic/linalg.pyc'>

and

In [1]: import scipy

In [2]: scipy.linalg
Out[2]: <module 'scipy.linalg' from 
'/usr/local/lib/python2.3/site-packages/scipy/linalg/__init__.pyc'>

after installing full scipy. So, I would expect that you don't have full 
scipy installed..

>> I suggest then moving some of scipy.corelib packages under scipy.basic as
>> well. Currently linalg related codes, for instance, are dispersed in too
>> many places: scipy.lib.lapack_lite, scipy.basic.linalg,
>> scipy.basic.basic_lite + full scipy packages scipy.lib.lapack,
>> scipy.linalg. I would move scipy.lib.lapack_lite under scipy.basic and
>> joining scipy.basic.linalg and scipy.basic.basic_lite to
>> scipy.basic.linalg.
>>
>> I suggest also renaming scipy/corelib to scipy/lib.
>>
>> I can do some of the code clean up today as well.
>
> Can you do what you suggested? I'm pretty sure I'll muck it up somehow.

I have now moved lapack_lite and fftpack_lite to core/scipy/basic, created 
core/scipy/basic/{linalg,fftpack}.py modules and removed old files,
and renamed corelib to lib.

All scipy core and scipy tests pass ok here after these changes.

Pearu



More information about the SciPy-user mailing list