matplotlib installation

[Virgil Stokes]

Any suggestions on installing matplotlib for Python 2.6.2 on a Windows
Vista platform?

--V

 

[Alan G Isaac]

Any suggestions on installing matplotlib for Python 2.6.2 on a Windows
Vista platform?

Maintainers for some packages have run into a wall
compiling for 2.6. Matplotlib is one of these:
http://www.nabble.com/binary-instal...fault,-MSVCR90.DLL-and- mingw-td23971661.html

Another package I care about is SimpleParse, which also
found compiling for 2.6 to be impossible. I do not know
if this was the same problem or not, but it means that
SimpleParse is *still* not available as an installer for 2.6.

I assume this is of great concern to the Python community,
but I do not know where the discussion is taking place.

Alan Isaac

 

[David Cournapeau]

Some discussion has occurred in the issue tracker:

 http://bugs.python.org/issue3308
 http://bugs.python.org/issue6007

In general, the people responsible for how CPython builds on Windows
don't seem to consider this an issue.

We got the same problem with numpy. The good news is it is solvable
(at least partially).

http://projects.scipy.org/numpy/browser/trunk/numpy/random/mtrand/randomkit..c

Basically, there are some functions which are erroneously "declared"
in the .lib, but they don't actually exist in the MS C runtime. We
detect when the .C code is built under mingw, and add an hack to
redirect the function to the "real" function, _ftime64 (see around
line 75).

cheers,

David

 

[Lawrence D'Oliveiro]

Basically, there are some functions which are erroneously "declared"
in the .lib, but they don't actually exist in the MS C runtime.

Isn't this a MinGW bug?

 

[Ross Ridge]

Basically, there are some functions which are erroneously "declared"
in the .lib, but they don't actually exist in the MS C runtime.

Isn't this a MinGW bug?

No, MinGW runtime library isn't supposed to be fully compatible with
the Microsoft runtime library. While MinGW happens to use part of an
older Microsoft runtime library (MSVCRT.DLL) the goal of the MinGW has
never been to make a compiler that was 100% compatible with any version
of the Microsoft C compiler. There also isn't anything wrong with the
Microsoft runtime. A library that mixes both objects and import records
is perfectly legitimate.

Ross Ridge