[SciPy-user] matrix inversion time (Python vs MATLAB)

[josef.pktd at gmail.com]

On Sat, Jan 10, 2009 at 6:08 PM, Matthieu Brucher
<matthieu.brucher at gmail.com> wrote:
>> So I think that, if you want to link against mkl, then the best would
>> be to make a local copy of the dlls. This seems to be the common
>> policy,  for example, I have more than 10 programs (mostly open
>> source, including numpy/scipy) that all have their own lapack in the
>> local directories.
>
> Contrary to usual programs, Python is scattered in several folders,
> and in the absolute, the dll should be put in the main Python folder
> to be seen by Python at runtime. But then what would you do if other
> modules provide their own MKL dlls?

Currently scipy has duplicates of lapack, blas in different folders,
so having several copies
of another set of dlls wouldn't make much difference. If they are put
in the main python folder, they could be renamed (if that is possible,
since it would be a "private" copy) to lapack_scipy.dll.

But I have no idea what happens when other extensions, e.g. scikits
want to compile against the same libraries and how that can be
supported. But whatever the mechanism, I think numpy/scipy should have
its own copies of the dlls and not rely on a system wide install.

However, for these things, I'm a pure user, who only suffers every
once in a while if programs don't stick to their own territory.

Josef


> The only solution is to load on the fly the dlls, a kind of plugin
> system. This means that someone has to propose a patch to support
> this, without slowdowns compared to the current position (which is
> very good thanks to David efforts to provide fully functional
> Numpy/Scipy installers, even if he does not have much time, PhD
> power). The situation is not optimal, but it is not bad, it is very
> good. If someone wants to do better, he can always propose something
> ;)
>
> Matthieu
> --
> Information System Engineer, Ph.D.
> Website: http://matthieu-brucher.developpez.com/
> Blogs: http://matt.eifelle.com and http://blog.developpez.com/?blog=92
> LinkedIn: http://www.linkedin.com/in/matthieubrucher
> _______________________________________________
> SciPy-user mailing list
> SciPy-user at scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-user
>