matplotlib-users Mailing List for matplotlib (Page 11)

Thanks again for all your work on this. I moved my old minGW and installed
MinGW-5.1.3, and was already running the others--except numpy, I have the
latest version from svn, which I compiled and built fine after building
atlas. I checked out matplotlib from svn and did the same as you
--I didn't try using the importlib batch file--I have a libpython25.a--so,
after changing the profile24.bat to profile25.bat with appropriate path
changes and your modifications to setup.py, I built it. I then installed
it--no problems yet. I then tried to use it with embedding_in_wx4.py and
python crashes and burns. I find that it crashes with the same LazyValue
error. Something similar happened to one of my colleagues who tried building
with visual studio instead of mingw. He's given up and is now running it on
his Mac. Sadly, I don't have that option. Does anyone else have any ideas?
Thanks,
William
On 8/2/07, Michael Droettboom <md...@st...> wrote:
>
> Well, the good news is that I was able to get it to compile and run the
> wxPython backend on Windows. The bad news is that my symptoms are different
> enough from yours that I'm not sure this will help you.
>
> I started with a reasonably clean Windows XP SP2 machine with no
> development tools on it. I installed (using the standard binary installers)
> the most recent stable releases of the following:
>
> - Python 2.5.1 (python.org)
> - wxPython-2.8.4.0
> - numpy-1.0.3
> - MinGW-5.1.3 (selecting the "current" release option)
> - MSys-1.0.10
>
> I checked out the latest matplotlib from svn (r3662).
>
> I downloaded and uncompressed win32_static from here:
> http://matplotlib.sourceforge.net/win32_static.tar.gz
>
> I did not do the pexports step, as I don't think MinGW requires it any
> longer.
>
> I updated profile24.bat to point at my new Python 2.5 (this should
> probably be added to win32_static when someone gets a chance).
>
> I then built and installed using:
>
> python setup.py build --compiler=mingw32 install
>
> (Note that I didn't build and use the Windows installer as the
> instructions suggest -- I doubt that makes a difference, though).
>
> It built fine the first time.
>
> Then I ran into problems. When importing certain extension modules
> (ft2font, _transforms etc.), but not others (ttconv), I got a dialog with
> the error message:
>
> "The procedure entry point _ctype could not be located in
> the dynamic link library msvcr71.dll"
>
> ...and then the module would fail to load.
>
> This is quite different from what William was seeing, since for him the
> modules were obviously loading and then failing in the initialization code.
>
> Googling tells me that this is because libstdc++ (specifically the
> <string> and <iostream> stuff) depends on _ctype for determining the types
> of various ASCII characters, which was in msvcrt.dll but was removed from
> msvcrt71.dll. Python2.5 is built with and therefore requires its
> extensions to link to msvcrt71.dll, so that's what you get by
> default. Fortunately, it doesn't seem to hurt to link to both. I added the
> following to setup.py, right before the final "distrib = setup(..."
> section:
>
> from setupext import get_win32_compiler
> if sys.platform == 'win32' and get_win32_compiler() == 'mingw32':
> for module in ext_modules:
> module.libraries.append("msvcrt")
>
> After this change, I was able to run embedding_in_wx4.py and get a window
> with a plot in it. Everything *seems* to be in order.
>
> William, I'm really curious if the above fix solves your problem. I
> probably shouldn't spend too much more time on this myself, as Windows isn't
> a very common platform for us (by that I mean my employer, STScI, not
> matplotlib as a whole). If I can admit selfishness, I really just wanted to
> make sure I hadn't hosed anything with my recent setup.py changes. I
> think that has been ruled out, and instead we now have what looks like a big
> amorphous configuration-difference problem.
>
> Cheers,
> Mike
>

Well, the good news is that I was able to get it to compile and run the wxPython backend on Windows. The bad news is that my symptoms are different enough from yours that I'm not sure this will help you.
I started with a reasonably clean Windows XP SP2 machine with no development tools on it. I installed (using the standard binary installers) the most recent stable releases of the following:
 - Python 2.5.1 (python.org)
 - wxPython-2.8.4.0
 - numpy-1.0.3
 - MinGW-5.1.3 (selecting the "current" release option)
 - MSys-1.0.10
I checked out the latest matplotlib from svn (r3662).
I downloaded and uncompressed win32_static from here: http://matplotlib.sourceforge.net/win32_static.tar.gz
I did not do the pexports step, as I don't think MinGW requires it any longer.
I updated profile24.bat to point at my new Python 2.5 (this should probably be added to win32_static when someone gets a chance).
I then built and installed using:
python setup.py build --compiler=mingw32 install
(Note that I didn't build and use the Windows installer as the instructions suggest -- I doubt that makes a difference, though).
It built fine the first time.
Then I ran into problems. When importing certain extension modules (ft2font, _transforms etc.), but not others (ttconv), I got a dialog with the error message:
 "The procedure entry point _ctype could not be located in
the dynamic link library msvcr71.dll"
...and then the module would fail to load.
This is quite different from what William was seeing, since for him the modules were obviously loading and then failing in the initialization code.
Googling tells me that this is because libstdc++ (specifically the <string> and <iostream> stuff) depends on _ctype for determining the types of various ASCII characters, which was in msvcrt.dll but was removed from msvcrt71.dll. Python2.5 is built with and therefore requires its extensions to link to msvcrt71.dll, so that's what you get by default. Fortunately, it doesn't seem to hurt to link to both. I added the following to setup.py, right before the final "distrib = setup(..." section:
 from setupext import get_win32_compiler
 if sys.platform == 'win32' and get_win32_compiler() == 'mingw32':
 for module in ext_modules:
 module.libraries.append("msvcrt")
After this change, I was able to run embedding_in_wx4.py and get a window with a plot in it. Everything *seems* to be in order.
William, I'm really curious if the above fix solves your problem. I probably shouldn't spend too much more time on this myself, as Windows isn't a very common platform for us (by that I mean my employer, STScI, not matplotlib as a whole). If I can admit selfishness, I really just wanted to make sure I hadn't hosed anything with my recent setup.py changes. I think that has been ruled out, and instead we now have what looks like a big amorphous configuration-difference problem.
Cheers,
Mike

Thank you Christopher that's great. wxPython working fine, no warnings.
Cong.
On 8/2/07, Christopher Barker <Chr...@no...> wrote:
>
> fri...@gm... wrote:
> > Dear all: The first problem was fixed by upgrading to a recent version
> > of ipython. As for the second (IPP stuff) warning ... still pending but
> > doesn't doing harm currently.
>
> A question to the wxPython mailing list may be in order for that one. AS
> a little test, trying running the enclosed, about-as-small-as-it-gets
> wxPython app, and see if you get the same warning.
>
> -Chris
>
>
> --
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
>
> Chr...@no...
>
>

Hi all,
Here a quick update:
I'm trying to have a concise / sparse module with containing only
pylab-specific names and not all names I already have in numpy.
To easy typing I want to call numpy "N" and my pylab "P".
I'm now using this code:
<code snipplet for importing matplotlib>
 import matplotlib, new
 matplotlib.use('WXAgg')
 from matplotlib import pylab
 P = new.module("pylab_sparse","""pylab module minus stuff alreay
in numpy""")
 for k,v in pylab.__dict__.iteritems():
 try:
 if v is N.__dict__[k]:
 continue
 except KeyError:
 pass
 P.__dict__[k] = v
 P.ion()
 del matplotlib, new, pylab
</code sniplet for importing matplotlib>
The result is "some" reduction in the number of non-pylab-specific
names in my "P"-module. However there seem to be still many extra
names left, like e.g.:
alltrue, amax, array, ...
look at this:
 # 20070802
 # >>> len(dir(pylab))
 # 441
 # >>> len(dir(P))
 # 346
 # >>> P.nx.numpy.__version__
 # '1.0.1'
 # >>> N.__version__
 # '1.0.1'
 # >>> N.alltrue
 # <function alltrue at 0x01471B70>
 # >>> P.alltrue
 # <function alltrue at 0x019142F0>
 # >>> N.alltrue.__doc__
 # 'Perform a logical_and over the given axis.'
 # >>> P.alltrue.__doc__
 # >>> #N.alltrue(x, axis=None, out=None)
 # >>> #P.alltrue(x, axis=0)
I'm using matplotlib with
__version__ = '0.90.0'
__revision__ = '$Revision: 3003 $'
__date__ = '$Date: 2007年02月06日 22:24:06 -0500 (2007年2月06日) $'
Any hint how to further reduce the number of names in "P" ?
My ideal would be that the "P" module (short for pylab) would only
contain the stuff described in the __doc__ strings of `pylab.py` and
`__init__.py`(in matplotlib) (+ plus some extra, undocumented, yet
pylab specific things)
Thanks
-Sebastian
On 3/16/07, Eric Firing <ef...@ha...> wrote:
> Sebastian Haase wrote:
> > Hi!
> > I use the wxPython PyShell.
> > I like especially the feature that when typing a module and then the
> > dot "." I get a popup list of all available functions (names) inside
> > that module.
> >
> > Secondly, I think it really makes code clearer when one can see where
> > a function comes from.
> >
> > I have a default
> > import numpy as N
> > executed before my shell even starts.
> > In fact I have a bunch of my "standard" modules imported as <some
> > single capital letter>.
> >
> > This - I think - is a good compromise to the commonly used "extra
> > typing" and "unreadable" argument.
> >
> > a = sin(b) * arange(10,50, .1) * cos(d)
> > vs.
> > a = N.sin(b) * N.arange(10,50, .1) * N.cos(d)
>
> I generally do the latter, but really, all those "N." bits are still
> visual noise when it comes to reading the code--that is, seeing the
> algorithm rather than where the functions come from. I don't think
> there is anything wrong with explicitly importing commonly-used names,
> especially things like sin and cos.
>
> >
> > I would like to hear some comments by others.
> >
> >
> > On a different note: I just started using pylab, so I did added an
> > automatic "from matplotlib import pylab as P" -- but now P contains
> > everything that I already have in N. It makes it really hard to
> > *find* (as in *see* n the popup-list) the pylab-only functions. --
> > what can I do about this ?
>
> A quick and dirty solution would be to comment out most of the imports
> in pylab.py; they are not needed for the pylab functions and are there
> only to give people lots of functionality in a single namespace.
>
> I am cross-posting this to matplotlib-users because it involves mpl, and
> an alternative solution would be for us to add an rcParam entry to allow
> one to turn off all of the namespace consolidation. A danger is that if
> someone is using "from pylab import *" in a script, then whether it
> would run would depend on the matplotlibrc file. To get around that,
> another possibility would be to break pylab.py into two parts, with
> pylab.py continuing to do the namespace consolidation and importing the
> second part, which would contain the actual pylab functions. Then if
> you don't want the namespace consolidation, you could simply import the
> second part instead of pylab. There may be devils in the details, but
> it seems to me that this last alternative--splitting pylab.py--might
> make a number of people happier while having no adverse effects on
> everyone else.
>
> Eric
> >
> >
> > Thanks,
> > Sebastian

william ratcliff wrote:
> This also occurs when I run
> import matplotlib
> matplotlib.use("Agg")
> from pylab import *,
> then it crashes with LazyValue::init_type
That's in the _transforms module. You might try with
matplotlib.use("Template") and see if it still crashes--not that I would 
know how to track down the problem in either case.
Eric
> 
> 
> On 8/1/07, * william ratcliff* <wil...@gm... 
> <mailto:wil...@gm...>> wrote:
> 
> No, thank you for trying so hard.
> 
> I just tried running setup.py with VERBOSE=True on a clean installation.
> when it crashes I get:
> LazyValue::init_type
> 
> does this mean anything to anyone?
> 
> William
> 
> 
> On 8/1/07, *Michael Droettboom* <md...@st...
> <mailto:md...@st...>> wrote:
> 
> It's probably something in C++ backend code for Agg. Maybe
> someone else
> on this list knows the last time it built and worked on Windows
> and can
> track down a change that may have broken it.
> 
> It will probably take some work with a debugger to figure out
> where it
> is crashing. I'd be completely guessing at this point. If you feel
> adventurous and can get a C backtrace out of the crash somehow,
> (does
> gdb work with mingw?), that could be useful. Barring that,
> maybe one of
> the other Windows folk on this list has some ideas.
> 
> Thanks for your considerable patience ;)
> 
> Cheers,
> Mike
> 
> william ratcliff wrote:
> > Yes. It crashes at the savefig line.
> >
> > On 8/1/07, *Michael Droettboom* < md...@st...
> <mailto:md...@st...>
> > <mailto: md...@st... <mailto:md...@st...>>> wrote:
> >
> > william ratcliff wrote:
> > > Ok--I reverted to head and it fixed the undefined references
> > error and
> > > everything seems to build normally.
> > Well, that's partially good news...
> > > But, if I try to run the embedding_in_wx4.py example, it
> crashes
> > > python 2.5.1
> > >
> > > If I install from the .msi then things do work in python
> 2.5.1,
> > so it
> > > must be something with the build.
> > Just to clarify, you mean the 0.90.1 installer downloaded from
> > SourceForge?
> > >
> > > I also tried to just start python from the command
> window, then ran:
> > > import numpy as N
> > > x=N.array([1,2,3])
> > > from pylab import *
> > > plot(x,x)
> > > show()
> > >
> > > The plot command generates a Line2D instance,
> > > but the show() command kills python in the same way that the
> > embedding
> > > example does. In the embedding example, I notice that the
> > CanvasFrame
> > > is generated before the crash.
> > Does it also crash if you use the Agg backend alone and
> save to an
> > image
> > file?
> >
> > import matplotlib
> > matplotlib.use("Agg")
> > from pylab import *
> > plot([1,2,3])
> > savefig("test.png")
> >
> > Cheers,
> > Mike
> > >
> > > On 8/1/07, *william ratcliff* <
> wil...@gm... <mailto:wil...@gm...>
> > <mailto: wil...@gm...
> <mailto:wil...@gm...>>
> > > <mailto:wil...@gm...
> <mailto:wil...@gm...>
> > <mailto: wil...@gm...
> <mailto:wil...@gm...>>>> wrote:
> > >
> > > Let me try this.
> > >
> > > On 8/1/07, *Michael Droettboom* < md...@st...
> <mailto:md...@st...>
> > <mailto: md...@st... <mailto:md...@st...>>
> > > <mailto: md...@st... <mailto:md...@st...>
> <mailto:md...@st... <mailto:md...@st...>>>> wrote:
> > >
> > > I'm going to summarize, just to make sure I have
> everything
> > > straight.
> > >
> > > 1) HEAD doesn't build (you get lots of "undefined
> > reference to
> > > `_imp__FT_Done_FreeType'")
> > > 2) revision 3645 (yesterday before my setup.py
> changes),
> > > builds, but you
> > > got the float('inf') error (which is now fixed)
> > > 3) much earlier revisions (3608) have other issues
> > (which seem
> > > to be
> > > related to out-of-date wxPython code)
> > >
> > > I have just committed a possible fix for 1). You
> may
> > want to try
> > > updating to HEAD and building that.
> > >
> > > If that doesn't work for you, I'm worried about
> things
> > getting
> > > out of
> > > hand and annoying a lot of people with my (well
> intentioned)
> > > setup.py
> > > changes yesterday. If that's the case, I will
> revert my
> > build
> > > changes
> > > until I have a chance to sit in front of a
> Windows box and
> > > figure out
> > > what's really going wrong.
> > >
> > > Apologies all around,
> > > Mike
> > >
> > > william ratcliff wrote:
> > > > 3608 also runs into problems of linking with
> the freetype
> > > libraries.
> > > > Some much older versions (say in the 3500s)
> compile, but
> > > still crash
> > > > python2.5.1 with errors like:
> > > >
> > > >
> > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > > embedding_in_wx4.
> > > > py
> > > > embedding_in_wx4.py:24: DeprecationWarning: The
> wxPython
> > > compatibility
> > > > package i
> > > > s no longer automatically generated or actively
> > > maintained. Please
> > > > switch to th
> > > > e wx package as soon as possible.
> > > > from wxPython.wx import *
> > > >
> > > > Thanks again for the help!
> > > >
> > > > William
> > > >
> > > > On 8/1/07, *John Hunter* < jd...@gm...
> <mailto:jd...@gm...>
> > <mailto: jd...@gm... <mailto:jd...@gm...>>
> > > <mailto: jd...@gm...
> <mailto:jd...@gm...> <mailto: jd...@gm...
> <mailto:jd...@gm...>>>
> > <mailto: jd...@gm... <mailto:jd...@gm...>
> <mailto:jd...@gm... <mailto:jd...@gm...>>
> > > <mailto: jd...@gm...
> <mailto:jd...@gm...> <mailto: jd...@gm...
> <mailto:jd...@gm...>>>>
> > > > > wrote:
> > > >
> > > > On 8/1/07, william ratcliff <
> > wil...@gm...
> <mailto:wil...@gm...>
> <mailto:wil...@gm...
> <mailto:wil...@gm...>>
> > > <mailto: wil...@gm...
> <mailto:wil...@gm...>
> > <mailto:wil...@gm...
> <mailto:wil...@gm...>>>
> > > > <mailto: wil...@gm...
> <mailto:wil...@gm...>
> > <mailto:wil...@gm...
> <mailto:wil...@gm...>>
> > > <mailto: wil...@gm...
> <mailto:wil...@gm...>
> > <mailto:wil...@gm...
> <mailto:wil...@gm...>>>>> wrote:
> > > > > from matplotlib.mathtext import
> > math_parse_s_ft2font
> > > > > File
> > > > >
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1182, in <mo
> > > > > dule>
> > > > > class Vlist(List):
> > > > > File
> > > > >
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1189, in Vli
> > > > > st
> > > > > def vpack(self, h=0., m='additional',
> > l=float('inf')):
> > > > > ValueError: invalid literal for float(): inf
> > > >
> > > > It's not clear to me why you should be hitting
> > mathtext
> > > at all, since
> > > > the wxcursor_demo.py does not use it, as
> far as I can
> > > tell. Michael,
> > > > would any of your earlier work caused him
> to get into
> > > mathtext
> > > > inapproriately? You may need to revert a
> little
> > farther,
> > > William, eg
> > > > to r3608 while we get this sorted out.
> > > >
> > > > JDH
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

fri...@gm... wrote:
> Dear all: The first problem was fixed by upgrading to a recent version 
> of ipython. As for the second (IPP stuff) warning ... still pending but 
> doesn't doing harm currently.
A question to the wxPython mailing list may be in order for that one. AS 
a little test, trying running the enclosed, about-as-small-as-it-gets 
wxPython app, and see if you get the same warning.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

Dear all: The first problem was fixed by upgrading to a recent version of
ipython. As for the second (IPP stuff) warning ... still pending but doesn't
doing harm currently.
Thank you all.
Cong.
On 8/2/07, Christopher Barker <Chr...@no...> wrote:
>
> fri...@gm... wrote:
> > /usr/lib/python2.5/site-packages/IPython/Shell.py:709:
> > DeprecationWarning: The wxPython compatibility package is no longer
> > automatically generated or actively maintained. Please switch to the wx
> > package as soon as possible.
>
> > I don't understand what was said by the Deprecation Warning message. The
> > wxPython on my computer is up-to-date.
>
> This isn't an issue with your wx package, it's an issue with how ipython
> or mpl is using wx -- are you using the latest versions of each of
> these? I'm pretty sure this was fixed in recent MPLs.
>
> However, it's a deprecation warning, so it should still work for now.
>
> > ** (python:15301): WARNING **: IPP request failed with status 1030
>
> I have no idea about this one -- hopefully it will be familiar to someone.
>
> -Chris
>
> --
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
>
> Chr...@no...
>

Jonathan Makem wrote:
> How do I scale an image of a plot so that it fits a landscape A4 
> page?
What back-end are you using?
> How do you increase the font size of the numbers on each axis?
This page may be helpful for some of these questions:
http://www.scipy.org/Cookbook/Matplotlib/AdjustingImageSize
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

This also occurs when I run
import matplotlib
matplotlib.use("Agg")
from pylab import *,
then it crashes with LazyValue::init_type
On 8/1/07, william ratcliff <wil...@gm...> wrote:
>
> No, thank you for trying so hard.
>
> I just tried running setup.py with VERBOSE=True on a clean installation.
> when it crashes I get:
> LazyValue::init_type
>
> does this mean anything to anyone?
>
> William
>
> On 8/1/07, Michael Droettboom <md...@st...> wrote:
> >
> > It's probably something in C++ backend code for Agg. Maybe someone else
> > on this list knows the last time it built and worked on Windows and can
> > track down a change that may have broken it.
> >
> > It will probably take some work with a debugger to figure out where it
> > is crashing. I'd be completely guessing at this point. If you feel
> > adventurous and can get a C backtrace out of the crash somehow, (does
> > gdb work with mingw?), that could be useful. Barring that, maybe one of
> >
> > the other Windows folk on this list has some ideas.
> >
> > Thanks for your considerable patience ;)
> >
> > Cheers,
> > Mike
> >
> > william ratcliff wrote:
> > > Yes. It crashes at the savefig line.
> > >
> > > On 8/1/07, *Michael Droettboom* < md...@st...
> > > <mailto:md...@st...>> wrote:
> > >
> > > william ratcliff wrote:
> > > > Ok--I reverted to head and it fixed the undefined references
> > > error and
> > > > everything seems to build normally.
> > > Well, that's partially good news...
> > > > But, if I try to run the embedding_in_wx4.py example, it crashes
> > > > python 2.5.1
> > > >
> > > > If I install from the .msi then things do work in python 2.5.1,
> > > so it
> > > > must be something with the build.
> > > Just to clarify, you mean the 0.90.1 installer downloaded from
> > > SourceForge?
> > > >
> > > > I also tried to just start python from the command window, then
> > ran:
> > > > import numpy as N
> > > > x=N.array([1,2,3])
> > > > from pylab import *
> > > > plot(x,x)
> > > > show()
> > > >
> > > > The plot command generates a Line2D instance,
> > > > but the show() command kills python in the same way that the
> > > embedding
> > > > example does. In the embedding example, I notice that the
> > > CanvasFrame
> > > > is generated before the crash.
> > > Does it also crash if you use the Agg backend alone and save to an
> >
> > > image
> > > file?
> > >
> > > import matplotlib
> > > matplotlib.use("Agg")
> > > from pylab import *
> > > plot([1,2,3])
> > > savefig("test.png")
> > >
> > > Cheers,
> > > Mike
> > > >
> > > > On 8/1/07, *william ratcliff* < wil...@gm...
> > > <mailto: wil...@gm...>
> > > > <mailto:wil...@gm...
> > > <mailto:wil...@gm... >>> wrote:
> > > >
> > > > Let me try this.
> > > >
> > > > On 8/1/07, *Michael Droettboom* < md...@st...
> > > <mailto: md...@st...>
> > > > <mailto:md...@st... <mailto:md...@st...>>> wrote:
> > > >
> > > > I'm going to summarize, just to make sure I have
> > everything
> > > > straight.
> > > >
> > > > 1) HEAD doesn't build (you get lots of "undefined
> > > reference to
> > > > `_imp__FT_Done_FreeType'")
> > > > 2) revision 3645 (yesterday before my setup.py changes),
> > > > builds, but you
> > > > got the float('inf') error (which is now fixed)
> > > > 3) much earlier revisions (3608) have other issues
> > > (which seem
> > > > to be
> > > > related to out-of-date wxPython code)
> > > >
> > > > I have just committed a possible fix for 1). You may
> > > want to try
> > > > updating to HEAD and building that.
> > > >
> > > > If that doesn't work for you, I'm worried about things
> > > getting
> > > > out of
> > > > hand and annoying a lot of people with my (well
> > intentioned)
> > > > setup.py
> > > > changes yesterday. If that's the case, I will revert my
> > > build
> > > > changes
> > > > until I have a chance to sit in front of a Windows box
> > and
> > > > figure out
> > > > what's really going wrong.
> > > >
> > > > Apologies all around,
> > > > Mike
> > > >
> > > > william ratcliff wrote:
> > > > > 3608 also runs into problems of linking with the
> > freetype
> > > > libraries.
> > > > > Some much older versions (say in the 3500s) compile,
> > but
> > > > still crash
> > > > > python2.5.1 with errors like:
> > > > >
> > > > >
> > > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > > > embedding_in_wx4.
> > > > > py
> > > > > embedding_in_wx4.py:24: DeprecationWarning: The
> > wxPython
> > > > compatibility
> > > > > package i
> > > > > s no longer automatically generated or actively
> > > > maintained. Please
> > > > > switch to th
> > > > > e wx package as soon as possible.
> > > > > from wxPython.wx import *
> > > > >
> > > > > Thanks again for the help!
> > > > >
> > > > > William
> > > > >
> > > > > On 8/1/07, *John Hunter* < jd...@gm...
> > > <mailto: jd...@gm...>
> > > > <mailto: jd...@gm... <mailto:jd...@gm...>>
> > > <mailto: jd...@gm... <mailto:jd...@gm...>
> > > > <mailto:jd...@gm... <mailto: jd...@gm...>>>
> > > > > > wrote:
> > > > >
> > > > > On 8/1/07, william ratcliff <
> > > wil...@gm... <mailto:wil...@gm...>
> > > > <mailto: wil...@gm...
> > > <mailto:wil...@gm...>>
> > > > > <mailto: wil...@gm...
> > > <mailto:wil...@gm...>
> > > > <mailto:wil...@gm...
> > > <mailto:wil...@gm...>>>> wrote:
> > > > > > from matplotlib.mathtext import
> > > math_parse_s_ft2font
> > > > > > File
> > > > > >
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > > line 1182, in <mo
> > > > > > dule>
> > > > > > class Vlist(List):
> > > > > > File
> > > > > >
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > > line 1189, in Vli
> > > > > > st
> > > > > > def vpack(self, h=0., m='additional',
> > > l=float('inf')):
> > > > > > ValueError: invalid literal for float(): inf
> > > > >
> > > > > It's not clear to me why you should be hitting
> > > mathtext
> > > > at all, since
> > > > > the wxcursor_demo.py does not use it, as far as I
> > can
> > > > tell. Michael,
> > > > > would any of your earlier work caused him to get
> > into
> > > > mathtext
> > > > > inapproriately? You may need to revert a little
> > > farther,
> > > > William, eg
> > > > > to r3608 while we get this sorted out.
> > > > >
> > > > > JDH
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

fri...@gm... wrote:
> I'm an astronomy major college student in Beijing who recently 
> switched to Python for most of his homework in numeric analysis and 
> data visualization (and really loving Python). I run Python 2.5 
> with NumPy, SciPy and matplotlib on a Fedora 7 Linux system. The 
> matplotlib on my computer was build from source but most of the 
> required dependecies (incl. wxPython, gtk2-devel things, etc.) were 
> installed from the "official" Fedora repository via yum. During 
> compilation of matplotlib I set the BUILD_WXAGG variable to 1 and left 
> everything else untouched.
>
> The compilation was smooth but the first test run seems not. After 
> invoking ipython with -pylab parameter I received the warning (and 
> welcome) messages:
>
> /usr/lib/python2.5/site-packages/IPython/Shell.py:709: 
> DeprecationWarning: The wxPython compatibility package is no longer 
> automatically generated or actively maintained. Please switch to the 
> wx package as soon as possible.
> import wxPython.wx as wx
This is actually coming from ipython, not matplotlib. This indicates 
that version of ipython you have installed was written for an earlier 
version of wxPython. It may still work despite this warning. (Maybe an 
ipython expert can comment on that.) The current release of ipython 
(0.8.1) has been updated and does not present this warning with the 
current release of wxPython (2.8.4.0).
If both your ipython and wxPython are from official Fedora packages, 
that's a version mismatch, and should probably be reported as a 
packaging bug to Fedora. You may want to upgrade ipython if you can do 
so easily.
> Then I threw a test command to ipython and things seem to be wrong 
> again. A typical session goes like this:
>
> In [1]: # This is just a test plot. It generates a figure in the GUI 
> with some warning message.
>
> In [2]: plot([1, 3, 8, 0])
>
> ** (python:15301): WARNING **: IPP request failed with status 1030
>
> ** (python:15301): WARNING **: IPP request failed with status 1030
That's very strange. AFAIK, IPP is "Internet Printing Protocol", and 
this message usually comes from CUPS or something. My best guess is 
that when wxPython initializes its first window, it also initializes the 
wxWidgets printing stuff, and there's something underlying that that is 
broken on your system. (Only a guess). Again, it's possible that 
things could continue normally despite this warning.
I would look into your printer configuration to see if these messages 
can be eliminated.
> The correct figure was generated in a GUI but error messages pop 
> up whenever "plot" is used.
What are the error messages? (Or do you just mean the ones above?)
>
> Currently I've got no idea about either warning message. They 
> certainly told me something but I can't even make sure whether there 
> are things going wrong! *shrug* So any hints?
>
> Thanks in advance
I think if the plots being generated are okay, both of these warnings 
could be benign, though annoying.
Cheers,
Mike

No, thank you for trying so hard.
I just tried running setup.py with VERBOSE=True on a clean installation.
when it crashes I get:
LazyValue::init_type
does this mean anything to anyone?
William
On 8/1/07, Michael Droettboom <md...@st...> wrote:
>
> It's probably something in C++ backend code for Agg. Maybe someone else
> on this list knows the last time it built and worked on Windows and can
> track down a change that may have broken it.
>
> It will probably take some work with a debugger to figure out where it
> is crashing. I'd be completely guessing at this point. If you feel
> adventurous and can get a C backtrace out of the crash somehow, (does
> gdb work with mingw?), that could be useful. Barring that, maybe one of
> the other Windows folk on this list has some ideas.
>
> Thanks for your considerable patience ;)
>
> Cheers,
> Mike
>
> william ratcliff wrote:
> > Yes. It crashes at the savefig line.
> >
> > On 8/1/07, *Michael Droettboom* <md...@st...
> > <mailto:md...@st...>> wrote:
> >
> > william ratcliff wrote:
> > > Ok--I reverted to head and it fixed the undefined references
> > error and
> > > everything seems to build normally.
> > Well, that's partially good news...
> > > But, if I try to run the embedding_in_wx4.py example, it crashes
> > > python 2.5.1
> > >
> > > If I install from the .msi then things do work in python 2.5.1,
> > so it
> > > must be something with the build.
> > Just to clarify, you mean the 0.90.1 installer downloaded from
> > SourceForge?
> > >
> > > I also tried to just start python from the command window, then
> ran:
> > > import numpy as N
> > > x=N.array([1,2,3])
> > > from pylab import *
> > > plot(x,x)
> > > show()
> > >
> > > The plot command generates a Line2D instance,
> > > but the show() command kills python in the same way that the
> > embedding
> > > example does. In the embedding example, I notice that the
> > CanvasFrame
> > > is generated before the crash.
> > Does it also crash if you use the Agg backend alone and save to an
> > image
> > file?
> >
> > import matplotlib
> > matplotlib.use("Agg")
> > from pylab import *
> > plot([1,2,3])
> > savefig("test.png")
> >
> > Cheers,
> > Mike
> > >
> > > On 8/1/07, *william ratcliff* < wil...@gm...
> > <mailto:wil...@gm...>
> > > <mailto:wil...@gm...
> > <mailto:wil...@gm...>>> wrote:
> > >
> > > Let me try this.
> > >
> > > On 8/1/07, *Michael Droettboom* < md...@st...
> > <mailto:md...@st...>
> > > <mailto:md...@st... <mailto:md...@st...>>> wrote:
> > >
> > > I'm going to summarize, just to make sure I have
> everything
> > > straight.
> > >
> > > 1) HEAD doesn't build (you get lots of "undefined
> > reference to
> > > `_imp__FT_Done_FreeType'")
> > > 2) revision 3645 (yesterday before my setup.py changes),
> > > builds, but you
> > > got the float('inf') error (which is now fixed)
> > > 3) much earlier revisions (3608) have other issues
> > (which seem
> > > to be
> > > related to out-of-date wxPython code)
> > >
> > > I have just committed a possible fix for 1). You may
> > want to try
> > > updating to HEAD and building that.
> > >
> > > If that doesn't work for you, I'm worried about things
> > getting
> > > out of
> > > hand and annoying a lot of people with my (well
> intentioned)
> > > setup.py
> > > changes yesterday. If that's the case, I will revert my
> > build
> > > changes
> > > until I have a chance to sit in front of a Windows box and
> > > figure out
> > > what's really going wrong.
> > >
> > > Apologies all around,
> > > Mike
> > >
> > > william ratcliff wrote:
> > > > 3608 also runs into problems of linking with the
> freetype
> > > libraries.
> > > > Some much older versions (say in the 3500s) compile, but
> > > still crash
> > > > python2.5.1 with errors like:
> > > >
> > > >
> > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > > embedding_in_wx4.
> > > > py
> > > > embedding_in_wx4.py:24: DeprecationWarning: The wxPython
> > > compatibility
> > > > package i
> > > > s no longer automatically generated or actively
> > > maintained. Please
> > > > switch to th
> > > > e wx package as soon as possible.
> > > > from wxPython.wx import *
> > > >
> > > > Thanks again for the help!
> > > >
> > > > William
> > > >
> > > > On 8/1/07, *John Hunter* < jd...@gm...
> > <mailto:jd...@gm...>
> > > <mailto: jd...@gm... <mailto:jd...@gm...>>
> > <mailto: jd...@gm... <mailto:jd...@gm...>
> > > <mailto:jd...@gm... <mailto:jd...@gm...>>>
> > > > > wrote:
> > > >
> > > > On 8/1/07, william ratcliff <
> > wil...@gm... <mailto:wil...@gm...>
> > > <mailto: wil...@gm...
> > <mailto:wil...@gm...>>
> > > > <mailto: wil...@gm...
> > <mailto:wil...@gm...>
> > > <mailto:wil...@gm...
> > <mailto:wil...@gm...>>>> wrote:
> > > > > from matplotlib.mathtext import
> > math_parse_s_ft2font
> > > > > File
> > > > >
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1182, in <mo
> > > > > dule>
> > > > > class Vlist(List):
> > > > > File
> > > > >
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1189, in Vli
> > > > > st
> > > > > def vpack(self, h=0., m='additional',
> > l=float('inf')):
> > > > > ValueError: invalid literal for float(): inf
> > > >
> > > > It's not clear to me why you should be hitting
> > mathtext
> > > at all, since
> > > > the wxcursor_demo.py does not use it, as far as I
> can
> > > tell. Michael,
> > > > would any of your earlier work caused him to get
> into
> > > mathtext
> > > > inapproriately? You may need to revert a little
> > farther,
> > > William, eg
> > > > to r3608 while we get this sorted out.
> > > >
> > > > JDH
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>

It's probably something in C++ backend code for Agg. Maybe someone else 
on this list knows the last time it built and worked on Windows and can 
track down a change that may have broken it.
It will probably take some work with a debugger to figure out where it 
is crashing. I'd be completely guessing at this point. If you feel 
adventurous and can get a C backtrace out of the crash somehow, (does 
gdb work with mingw?), that could be useful. Barring that, maybe one of 
the other Windows folk on this list has some ideas.
Thanks for your considerable patience ;)
Cheers,
Mike
william ratcliff wrote:
> Yes. It crashes at the savefig line.
>
> On 8/1/07, *Michael Droettboom* <md...@st... 
> <mailto:md...@st...>> wrote:
>
> william ratcliff wrote:
> > Ok--I reverted to head and it fixed the undefined references
> error and
> > everything seems to build normally.
> Well, that's partially good news...
> > But, if I try to run the embedding_in_wx4.py example, it crashes
> > python 2.5.1
> >
> > If I install from the .msi then things do work in python 2.5.1,
> so it
> > must be something with the build.
> Just to clarify, you mean the 0.90.1 installer downloaded from
> SourceForge?
> >
> > I also tried to just start python from the command window, then ran:
> > import numpy as N
> > x=N.array([1,2,3])
> > from pylab import *
> > plot(x,x)
> > show()
> >
> > The plot command generates a Line2D instance,
> > but the show() command kills python in the same way that the
> embedding
> > example does. In the embedding example, I notice that the
> CanvasFrame
> > is generated before the crash.
> Does it also crash if you use the Agg backend alone and save to an
> image
> file?
>
> import matplotlib
> matplotlib.use("Agg")
> from pylab import *
> plot([1,2,3])
> savefig("test.png")
>
> Cheers,
> Mike
> >
> > On 8/1/07, *william ratcliff* < wil...@gm...
> <mailto:wil...@gm...>
> > <mailto:wil...@gm...
> <mailto:wil...@gm...>>> wrote:
> >
> > Let me try this.
> >
> > On 8/1/07, *Michael Droettboom* < md...@st...
> <mailto:md...@st...>
> > <mailto:md...@st... <mailto:md...@st...>>> wrote:
> >
> > I'm going to summarize, just to make sure I have everything
> > straight.
> >
> > 1) HEAD doesn't build (you get lots of "undefined
> reference to
> > `_imp__FT_Done_FreeType'")
> > 2) revision 3645 (yesterday before my setup.py changes),
> > builds, but you
> > got the float('inf') error (which is now fixed)
> > 3) much earlier revisions (3608) have other issues
> (which seem
> > to be
> > related to out-of-date wxPython code)
> >
> > I have just committed a possible fix for 1). You may
> want to try
> > updating to HEAD and building that.
> >
> > If that doesn't work for you, I'm worried about things
> getting
> > out of
> > hand and annoying a lot of people with my (well intentioned)
> > setup.py
> > changes yesterday. If that's the case, I will revert my
> build
> > changes
> > until I have a chance to sit in front of a Windows box and
> > figure out
> > what's really going wrong.
> >
> > Apologies all around,
> > Mike
> >
> > william ratcliff wrote:
> > > 3608 also runs into problems of linking with the freetype
> > libraries.
> > > Some much older versions (say in the 3500s) compile, but
> > still crash
> > > python2.5.1 with errors like:
> > >
> > >
> C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > embedding_in_wx4.
> > > py
> > > embedding_in_wx4.py:24: DeprecationWarning: The wxPython
> > compatibility
> > > package i
> > > s no longer automatically generated or actively
> > maintained. Please
> > > switch to th
> > > e wx package as soon as possible.
> > > from wxPython.wx import *
> > >
> > > Thanks again for the help!
> > >
> > > William
> > >
> > > On 8/1/07, *John Hunter* < jd...@gm...
> <mailto:jd...@gm...>
> > <mailto: jd...@gm... <mailto:jd...@gm...>>
> <mailto: jd...@gm... <mailto:jd...@gm...>
> > <mailto:jd...@gm... <mailto:jd...@gm...>>>
> > > > wrote:
> > >
> > > On 8/1/07, william ratcliff <
> wil...@gm... <mailto:wil...@gm...>
> > <mailto: wil...@gm...
> <mailto:wil...@gm...>>
> > > <mailto: wil...@gm...
> <mailto:wil...@gm...>
> > <mailto:wil...@gm...
> <mailto:wil...@gm...>>>> wrote:
> > > > from matplotlib.mathtext import
> math_parse_s_ft2font
> > > > File
> > > >
> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1182, in <mo
> > > > dule>
> > > > class Vlist(List):
> > > > File
> > > >
> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1189, in Vli
> > > > st
> > > > def vpack(self, h=0., m='additional',
> l=float('inf')):
> > > > ValueError: invalid literal for float(): inf
> > >
> > > It's not clear to me why you should be hitting
> mathtext
> > at all, since
> > > the wxcursor_demo.py does not use it, as far as I can
> > tell. Michael,
> > > would any of your earlier work caused him to get into
> > mathtext
> > > inapproriately? You may need to revert a little
> farther,
> > William, eg
> > > to r3608 while we get this sorted out.
> > >
> > > JDH
> > >
> > >
> >
> >
> >
>
>

Dear all,
I'm an astronomy major college student in Beijing who recently switched to
Python for most of his homework in numeric analysis and data visualization
(and really loving Python). I run Python 2.5 with NumPy, SciPy
and matplotlib on a Fedora 7 Linux system. The matplotlib on my computer was
build from source but most of the required dependecies (incl. wxPython,
gtk2-devel things, etc.) were installed from the "official" Fedora
repository via yum. During compilation of matplotlib I set the BUILD_WXAGG
variable to 1 and left everything else untouched.
The compilation was smooth but the first test run seems not. After invoking
ipython with -pylab parameter I received the warning (and welcome) messages:
/usr/lib/python2.5/site-packages/IPython/Shell.py:709: DeprecationWarning:
The wxPython compatibility package is no longer automatically generated or
actively maintained. Please switch to the wx package as soon as possible.
import wxPython.wx as wx
Python 2.5 (r25:51908, Apr 10 2007, 10:29:13)
Type "copyright", "credits" or "license" for more information.
IPython 0.7.2 -- An enhanced Interactive Python.
? -> Introduction to IPython's features.
%magic -> Information about IPython's 'magic' % functions.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.
Welcome to pylab, a matplotlib-based Python environment.
For more information, type 'help(pylab)'.
I don't understand what was said by the Deprecation Warning message. The
wxPython on my computer is up-to-date.
Then I threw a test command to ipython and things seem to be wrong again. A
typical session goes like this:
In [1]: # This is just a test plot. It generates a figure in the GUI with
some warning message.
In [2]: plot([1, 3, 8, 0])
** (python:15301): WARNING **: IPP request failed with status 1030
** (python:15301): WARNING **: IPP request failed with status 1030
Out[2]: [<matplotlib.lines.Line2D instance at 0x971648c>]
In [3]:
The correct figure was generated in a GUI but error messages pop
up whenever "plot" is used.
Currently I've got no idea about either warning message. They certainly told
me something but I can't even make sure whether there are things going
wrong! *shrug* So any hints?
Thanks in advance
Cong.

Yes. It crashes at the savefig line.
On 8/1/07, Michael Droettboom <md...@st...> wrote:
>
> william ratcliff wrote:
> > Ok--I reverted to head and it fixed the undefined references error and
> > everything seems to build normally.
> Well, that's partially good news...
> > But, if I try to run the embedding_in_wx4.py example, it crashes
> > python 2.5.1
> >
> > If I install from the .msi then things do work in python 2.5.1, so it
> > must be something with the build.
> Just to clarify, you mean the 0.90.1 installer downloaded from
> SourceForge?
> >
> > I also tried to just start python from the command window, then ran:
> > import numpy as N
> > x=N.array([1,2,3])
> > from pylab import *
> > plot(x,x)
> > show()
> >
> > The plot command generates a Line2D instance,
> > but the show() command kills python in the same way that the embedding
> > example does. In the embedding example, I notice that the CanvasFrame
> > is generated before the crash.
> Does it also crash if you use the Agg backend alone and save to an image
> file?
>
> import matplotlib
> matplotlib.use("Agg")
> from pylab import *
> plot([1,2,3])
> savefig("test.png")
>
> Cheers,
> Mike
> >
> > On 8/1/07, *william ratcliff* <wil...@gm...
> > <mailto:wil...@gm...>> wrote:
> >
> > Let me try this.
> >
> > On 8/1/07, *Michael Droettboom* < md...@st...
> > <mailto:md...@st...>> wrote:
> >
> > I'm going to summarize, just to make sure I have everything
> > straight.
> >
> > 1) HEAD doesn't build (you get lots of "undefined reference to
> > `_imp__FT_Done_FreeType'")
> > 2) revision 3645 (yesterday before my setup.py changes),
> > builds, but you
> > got the float('inf') error (which is now fixed)
> > 3) much earlier revisions (3608) have other issues (which seem
> > to be
> > related to out-of-date wxPython code)
> >
> > I have just committed a possible fix for 1). You may want to
> try
> > updating to HEAD and building that.
> >
> > If that doesn't work for you, I'm worried about things getting
> > out of
> > hand and annoying a lot of people with my (well intentioned)
> > setup.py
> > changes yesterday. If that's the case, I will revert my build
> > changes
> > until I have a chance to sit in front of a Windows box and
> > figure out
> > what's really going wrong.
> >
> > Apologies all around,
> > Mike
> >
> > william ratcliff wrote:
> > > 3608 also runs into problems of linking with the freetype
> > libraries.
> > > Some much older versions (say in the 3500s) compile, but
> > still crash
> > > python2.5.1 with errors like:
> > >
> > > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > embedding_in_wx4.
> > > py
> > > embedding_in_wx4.py:24: DeprecationWarning: The wxPython
> > compatibility
> > > package i
> > > s no longer automatically generated or actively
> > maintained. Please
> > > switch to th
> > > e wx package as soon as possible.
> > > from wxPython.wx import *
> > >
> > > Thanks again for the help!
> > >
> > > William
> > >
> > > On 8/1/07, *John Hunter* < jd...@gm...
> > <mailto:jd...@gm...> <mailto: jd...@gm...
> > <mailto:jd...@gm...>>
> > > > wrote:
> > >
> > > On 8/1/07, william ratcliff < wil...@gm...
> > <mailto:wil...@gm...>
> > > <mailto: wil...@gm...
> > <mailto:wil...@gm...>>> wrote:
> > > > from matplotlib.mathtext import math_parse_s_ft2font
> > > > File
> > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1182, in <mo
> > > > dule>
> > > > class Vlist(List):
> > > > File
> > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1189, in Vli
> > > > st
> > > > def vpack(self, h=0., m='additional',
> l=float('inf')):
> > > > ValueError: invalid literal for float(): inf
> > >
> > > It's not clear to me why you should be hitting mathtext
> > at all, since
> > > the wxcursor_demo.py does not use it, as far as I can
> > tell. Michael,
> > > would any of your earlier work caused him to get into
> > mathtext
> > > inapproriately? You may need to revert a little farther,
> > William, eg
> > > to r3608 while we get this sorted out.
> > >
> > > JDH
> > >
> > >
> >
> >
> >
>
>

william ratcliff wrote:
> Ok--I reverted to head and it fixed the undefined references error and 
> everything seems to build normally.
Well, that's partially good news...
> But, if I try to run the embedding_in_wx4.py example, it crashes 
> python 2.5.1
>
> If I install from the .msi then things do work in python 2.5.1, so it 
> must be something with the build.
Just to clarify, you mean the 0.90.1 installer downloaded from 
SourceForge? 
>
> I also tried to just start python from the command window, then ran:
> import numpy as N
> x=N.array([1,2,3])
> from pylab import *
> plot(x,x)
> show()
>
> The plot command generates a Line2D instance,
> but the show() command kills python in the same way that the embedding 
> example does. In the embedding example, I notice that the CanvasFrame 
> is generated before the crash.
Does it also crash if you use the Agg backend alone and save to an image 
file?
import matplotlib
matplotlib.use("Agg")
from pylab import *
plot([1,2,3])
savefig("test.png")
Cheers,
Mike
>
> On 8/1/07, *william ratcliff* <wil...@gm... 
> <mailto:wil...@gm...>> wrote:
>
> Let me try this.
>
> On 8/1/07, *Michael Droettboom* < md...@st...
> <mailto:md...@st...>> wrote:
>
> I'm going to summarize, just to make sure I have everything
> straight.
>
> 1) HEAD doesn't build (you get lots of "undefined reference to
> `_imp__FT_Done_FreeType'")
> 2) revision 3645 (yesterday before my setup.py changes),
> builds, but you
> got the float('inf') error (which is now fixed)
> 3) much earlier revisions (3608) have other issues (which seem
> to be
> related to out-of-date wxPython code)
>
> I have just committed a possible fix for 1). You may want to try
> updating to HEAD and building that.
>
> If that doesn't work for you, I'm worried about things getting
> out of
> hand and annoying a lot of people with my (well intentioned)
> setup.py
> changes yesterday. If that's the case, I will revert my build
> changes
> until I have a chance to sit in front of a Windows box and
> figure out
> what's really going wrong.
>
> Apologies all around,
> Mike
>
> william ratcliff wrote:
> > 3608 also runs into problems of linking with the freetype
> libraries.
> > Some much older versions (say in the 3500s) compile, but
> still crash
> > python2.5.1 with errors like:
> >
> > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > embedding_in_wx4.
> > py
> > embedding_in_wx4.py:24: DeprecationWarning: The wxPython
> compatibility
> > package i
> > s no longer automatically generated or actively
> maintained. Please
> > switch to th
> > e wx package as soon as possible.
> > from wxPython.wx import *
> >
> > Thanks again for the help!
> >
> > William
> >
> > On 8/1/07, *John Hunter* < jd...@gm...
> <mailto:jd...@gm...> <mailto: jd...@gm...
> <mailto:jd...@gm...>>
> > > wrote:
> >
> > On 8/1/07, william ratcliff < wil...@gm...
> <mailto:wil...@gm...>
> > <mailto: wil...@gm...
> <mailto:wil...@gm...>>> wrote:
> > > from matplotlib.mathtext import math_parse_s_ft2font
> > > File
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > line 1182, in <mo
> > > dule>
> > > class Vlist(List):
> > > File
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > line 1189, in Vli
> > > st
> > > def vpack(self, h=0., m='additional', l=float('inf')):
> > > ValueError: invalid literal for float(): inf
> >
> > It's not clear to me why you should be hitting mathtext
> at all, since
> > the wxcursor_demo.py does not use it, as far as I can
> tell. Michael,
> > would any of your earlier work caused him to get into
> mathtext
> > inapproriately? You may need to revert a little farther,
> William, eg
> > to r3608 while we get this sorted out.
> >
> > JDH
> >
> >
>
>
>

I also looked at the log_bar.py example and found that it's also at the
pylab.show() command that it dies
On 8/1/07, william ratcliff <wil...@gm...> wrote:
>
> Ok--I reverted to head and it fixed the undefined references error and
> everything seems to build normally. But, if I try to run the
> embedding_in_wx4.py example, it crashes python 2.5.1
>
> If I install from the .msi then things do work in python 2.5.1, so it must
> be something with the build.
>
> I also tried to just start python from the command window, then ran:
> import numpy as N
> x=N.array([1,2,3])
> from pylab import *
> plot(x,x)
> show()
>
> The plot command generates a Line2D instance,
> but the show() command kills python in the same way that the embedding
> example does. In the embedding example, I notice that the CanvasFrame is
> generated before the crash.
>
>
> Cheers,
> William
>
>
> On 8/1/07, william ratcliff <wil...@gm...> wrote:
> >
> > Let me try this.
> >
> > On 8/1/07, Michael Droettboom < md...@st...> wrote:
> > >
> > > I'm going to summarize, just to make sure I have everything straight.
> > >
> > > 1) HEAD doesn't build (you get lots of "undefined reference to
> > > `_imp__FT_Done_FreeType'")
> > > 2) revision 3645 (yesterday before my setup.py changes), builds, but
> > > you
> > > got the float('inf') error (which is now fixed)
> > > 3) much earlier revisions (3608) have other issues (which seem to be
> > > related to out-of-date wxPython code)
> > >
> > > I have just committed a possible fix for 1). You may want to try
> > > updating to HEAD and building that.
> > >
> > > If that doesn't work for you, I'm worried about things getting out of
> > > hand and annoying a lot of people with my (well intentioned) setup.py
> > > changes yesterday. If that's the case, I will revert my build changes
> > >
> > > until I have a chance to sit in front of a Windows box and figure out
> > > what's really going wrong.
> > >
> > > Apologies all around,
> > > Mike
> > >
> > > william ratcliff wrote:
> > > > 3608 also runs into problems of linking with the freetype libraries.
> > >
> > > > Some much older versions (say in the 3500s) compile, but still crash
> > > > python2.5.1 with errors like:
> > > >
> > > > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > > embedding_in_wx4.
> > > > py
> > > > embedding_in_wx4.py:24: DeprecationWarning: The wxPython
> > > compatibility
> > > > package i
> > > > s no longer automatically generated or actively maintained. Please
> > > > switch to th
> > > > e wx package as soon as possible.
> > > > from wxPython.wx import *
> > > >
> > > > Thanks again for the help!
> > > >
> > > > William
> > > >
> > > > On 8/1/07, *John Hunter* < jd...@gm... <mailto:jd...@gm...
> > > >
> > > > > wrote:
> > > >
> > > > On 8/1/07, william ratcliff < wil...@gm...
> > > > <mailto: wil...@gm...>> wrote:
> > > > > from matplotlib.mathtext import math_parse_s_ft2font
> > > > > File
> > > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1182, in <mo
> > > > > dule>
> > > > > class Vlist(List):
> > > > > File
> > > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > > line 1189, in Vli
> > > > > st
> > > > > def vpack(self, h=0., m='additional', l=float('inf')):
> > > > > ValueError: invalid literal for float(): inf
> > > >
> > > > It's not clear to me why you should be hitting mathtext at all,
> > > since
> > > > the wxcursor_demo.py does not use it, as far as I can
> > > tell. Michael,
> > > > would any of your earlier work caused him to get into mathtext
> > > > inapproriately? You may need to revert a little farther,
> > > William, eg
> > > > to r3608 while we get this sorted out.
> > > >
> > > > JDH
> > > >
> > > >
> > >
> > >
> >
>

Ok--I reverted to head and it fixed the undefined references error and
everything seems to build normally. But, if I try to run the
embedding_in_wx4.py example, it crashes python 2.5.1
If I install from the .msi then things do work in python 2.5.1, so it must
be something with the build.
I also tried to just start python from the command window, then ran:
import numpy as N
x=N.array([1,2,3])
from pylab import *
plot(x,x)
show()
The plot command generates a Line2D instance,
but the show() command kills python in the same way that the embedding
example does. In the embedding example, I notice that the CanvasFrame is
generated before the crash.
Cheers,
William
On 8/1/07, william ratcliff <wil...@gm...> wrote:
>
> Let me try this.
>
> On 8/1/07, Michael Droettboom <md...@st...> wrote:
> >
> > I'm going to summarize, just to make sure I have everything straight.
> >
> > 1) HEAD doesn't build (you get lots of "undefined reference to
> > `_imp__FT_Done_FreeType'")
> > 2) revision 3645 (yesterday before my setup.py changes), builds, but you
> > got the float('inf') error (which is now fixed)
> > 3) much earlier revisions (3608) have other issues (which seem to be
> > related to out-of-date wxPython code)
> >
> > I have just committed a possible fix for 1). You may want to try
> > updating to HEAD and building that.
> >
> > If that doesn't work for you, I'm worried about things getting out of
> > hand and annoying a lot of people with my (well intentioned) setup.py
> > changes yesterday. If that's the case, I will revert my build changes
> > until I have a chance to sit in front of a Windows box and figure out
> > what's really going wrong.
> >
> > Apologies all around,
> > Mike
> >
> > william ratcliff wrote:
> > > 3608 also runs into problems of linking with the freetype libraries.
> > > Some much older versions (say in the 3500s) compile, but still crash
> > > python2.5.1 with errors like:
> > >
> > > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > > embedding_in_wx4.
> > > py
> > > embedding_in_wx4.py:24: DeprecationWarning: The wxPython compatibility
> > > package i
> > > s no longer automatically generated or actively maintained. Please
> > > switch to th
> > > e wx package as soon as possible.
> > > from wxPython.wx import *
> > >
> > > Thanks again for the help!
> > >
> > > William
> > >
> > > On 8/1/07, *John Hunter* <jd...@gm... <mailto: jd...@gm...
> > >
> > > > wrote:
> > >
> > > On 8/1/07, william ratcliff < wil...@gm...
> > > <mailto: wil...@gm...>> wrote:
> > > > from matplotlib.mathtext import math_parse_s_ft2font
> > > > File
> > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1182, in <mo
> > > > dule>
> > > > class Vlist(List):
> > > > File
> > > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > > line 1189, in Vli
> > > > st
> > > > def vpack(self, h=0., m='additional', l=float('inf')):
> > > > ValueError: invalid literal for float(): inf
> > >
> > > It's not clear to me why you should be hitting mathtext at all,
> > since
> > > the wxcursor_demo.py does not use it, as far as I can
> > tell. Michael,
> > > would any of your earlier work caused him to get into mathtext
> > > inapproriately? You may need to revert a little farther, William,
> > eg
> > > to r3608 while we get this sorted out.
> > >
> > > JDH
> > >
> > >
> >
> >
>

Let me try this.
On 8/1/07, Michael Droettboom <md...@st...> wrote:
>
> I'm going to summarize, just to make sure I have everything straight.
>
> 1) HEAD doesn't build (you get lots of "undefined reference to
> `_imp__FT_Done_FreeType'")
> 2) revision 3645 (yesterday before my setup.py changes), builds, but you
> got the float('inf') error (which is now fixed)
> 3) much earlier revisions (3608) have other issues (which seem to be
> related to out-of-date wxPython code)
>
> I have just committed a possible fix for 1). You may want to try
> updating to HEAD and building that.
>
> If that doesn't work for you, I'm worried about things getting out of
> hand and annoying a lot of people with my (well intentioned) setup.py
> changes yesterday. If that's the case, I will revert my build changes
> until I have a chance to sit in front of a Windows box and figure out
> what's really going wrong.
>
> Apologies all around,
> Mike
>
> william ratcliff wrote:
> > 3608 also runs into problems of linking with the freetype libraries.
> > Some much older versions (say in the 3500s) compile, but still crash
> > python2.5.1 with errors like:
> >
> > C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
> > embedding_in_wx4.
> > py
> > embedding_in_wx4.py:24: DeprecationWarning: The wxPython compatibility
> > package i
> > s no longer automatically generated or actively maintained. Please
> > switch to th
> > e wx package as soon as possible.
> > from wxPython.wx import *
> >
> > Thanks again for the help!
> >
> > William
> >
> > On 8/1/07, *John Hunter* <jd...@gm... <mailto:jd...@gm...>
> > > wrote:
> >
> > On 8/1/07, william ratcliff < wil...@gm...
> > <mailto:wil...@gm...>> wrote:
> > > from matplotlib.mathtext import math_parse_s_ft2font
> > > File
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > line 1182, in <mo
> > > dule>
> > > class Vlist(List):
> > > File
> > > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > line 1189, in Vli
> > > st
> > > def vpack(self, h=0., m='additional', l=float('inf')):
> > > ValueError: invalid literal for float(): inf
> >
> > It's not clear to me why you should be hitting mathtext at all,
> since
> > the wxcursor_demo.py does not use it, as far as I can
> tell. Michael,
> > would any of your earlier work caused him to get into mathtext
> > inapproriately? You may need to revert a little farther, William,
> eg
> > to r3608 while we get this sorted out.
> >
> > JDH
> >
> >
>
>

I run from the command line. Essentially, it just goes poof. There is no
output--it generates an error report (as usual in windows)--but nothing pops
out that I can understand...
Cheers,
William
On 8/1/07, Michael Droettboom <md...@st...> wrote:
>
> Do you get any output (e.g. a traceback) or it just goes poof? (You may
> need to run it from the command line if you aren't already).
>
> Cheers,
> Mike
>
> william ratcliff wrote:
> > Now, it no longer gives rise to the previous error, but python crashes
> > when I run the embedding_in_wx4.py example.
> >
> > William
> >
> > On 8/1/07, *John Hunter* <jd...@gm...
> > <mailto:jd...@gm...>> wrote:
> >
> > On 8/1/07, Michael Droettboom < md...@st...
> > <mailto:md...@st...>> wrote:
> >
> > > >> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > > >> line 1189, in Vli
> > > >> st
> > > >> def vpack(self, h=0., m='additional', l=float('inf')):
> > > >> ValueError: invalid literal for float(): inf
> >
> > > I'm not opposed to importing mathtext on demand only, but that
> > would be new.
> >
> > I see, it wasn't clear to me on my first look that the bug was
> > triggered at module load time. I had assumed the bug was triggered
> by
> > *using* mathtext. Since you seem to have found the fix (numpy.inf)
> > I'm happy to leave it as is.
> >
> > JDH
> >
> >
>
>

Now, it no longer gives rise to the previous error, but python crashes when
I run the embedding_in_wx4.py example.
William
On 8/1/07, John Hunter <jd...@gm...> wrote:
>
> On 8/1/07, Michael Droettboom <md...@st...> wrote:
>
> > >> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > >> line 1189, in Vli
> > >> st
> > >> def vpack(self, h=0., m='additional', l=float('inf')):
> > >> ValueError: invalid literal for float(): inf
>
> > I'm not opposed to importing mathtext on demand only, but that would be
> new.
>
> I see, it wasn't clear to me on my first look that the bug was
> triggered at module load time. I had assumed the bug was triggered by
> *using* mathtext. Since you seem to have found the fix (numpy.inf)
> I'm happy to leave it as is.
>
> JDH
>

I'm going to summarize, just to make sure I have everything straight.
1) HEAD doesn't build (you get lots of "undefined reference to 
`_imp__FT_Done_FreeType'")
2) revision 3645 (yesterday before my setup.py changes), builds, but you 
got the float('inf') error (which is now fixed)
3) much earlier revisions (3608) have other issues (which seem to be 
related to out-of-date wxPython code)
I have just committed a possible fix for 1). You may want to try 
updating to HEAD and building that.
If that doesn't work for you, I'm worried about things getting out of 
hand and annoying a lot of people with my (well intentioned) setup.py 
changes yesterday. If that's the case, I will revert my build changes 
until I have a chance to sit in front of a Windows box and figure out 
what's really going wrong.
Apologies all around,
Mike
william ratcliff wrote:
> 3608 also runs into problems of linking with the freetype libraries. 
> Some much older versions (say in the 3500s) compile, but still crash 
> python2.5.1 with errors like:
>
> C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe 
> embedding_in_wx4.
> py
> embedding_in_wx4.py:24: DeprecationWarning: The wxPython compatibility 
> package i
> s no longer automatically generated or actively maintained. Please 
> switch to th
> e wx package as soon as possible.
> from wxPython.wx import *
>
> Thanks again for the help!
>
> William
>
> On 8/1/07, *John Hunter* <jd...@gm... <mailto:jd...@gm...> 
> > wrote:
>
> On 8/1/07, william ratcliff < wil...@gm...
> <mailto:wil...@gm...>> wrote:
> > from matplotlib.mathtext import math_parse_s_ft2font
> > File
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > line 1182, in <mo
> > dule>
> > class Vlist(List):
> > File
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > line 1189, in Vli
> > st
> > def vpack(self, h=0., m='additional', l=float('inf')):
> > ValueError: invalid literal for float(): inf
>
> It's not clear to me why you should be hitting mathtext at all, since
> the wxcursor_demo.py does not use it, as far as I can tell. Michael,
> would any of your earlier work caused him to get into mathtext
> inapproriately? You may need to revert a little farther, William, eg
> to r3608 while we get this sorted out.
>
> JDH
>
>

3608 also runs into problems of linking with the freetype libraries. Some
much older versions (say in the 3500s) compile, but still crash
python2.5.1with errors like:
C:\matplotlib\trunk\matplotlib\examples>c:\python25\python.exe
embedding_in_wx4.
py
embedding_in_wx4.py:24: DeprecationWarning: The wxPython compatibility
package i
s no longer automatically generated or actively maintained. Please switch
to th
e wx package as soon as possible.
 from wxPython.wx import *
Thanks again for the help!
William
On 8/1/07, John Hunter <jd...@gm...> wrote:
>
> On 8/1/07, william ratcliff <wil...@gm...> wrote:
> > from matplotlib.mathtext import math_parse_s_ft2font
> > File
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > line 1182, in <mo
> > dule>
> > class Vlist(List):
> > File
> > "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > line 1189, in Vli
> > st
> > def vpack(self, h=0., m='additional', l=float('inf')):
> > ValueError: invalid literal for float(): inf
>
> It's not clear to me why you should be hitting mathtext at all, since
> the wxcursor_demo.py does not use it, as far as I can tell. Michael,
> would any of your earlier work caused him to get into mathtext
> inapproriately? You may need to revert a little farther, William, eg
> to r3608 while we get this sorted out.
>
> JDH
>

John Hunter wrote:
> On 8/1/07, william ratcliff <wil...@gm...> wrote:
> 
>> from matplotlib.mathtext import math_parse_s_ft2font
>> File
>> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
>> line 1182, in <mo
>> dule>
>> class Vlist(List):
>> File
>> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
>> line 1189, in Vli
>> st
>> def vpack(self, h=0., m='additional', l=float('inf')):
>> ValueError: invalid literal for float(): inf
>> 
>
> It's not clear to me why you should be hitting mathtext at all, since
> the wxcursor_demo.py does not use it, as far as I can tell. Michael,
> would any of your earlier work caused him to get into mathtext
> inapproriately? 
The call to "float('inf')", since it's in a default argument spec, will 
get called at import time. Most (maybe all) of the backends import 
mathtext unconditionally, so this will get run whether mathtext is 
used/called or not.
I'm not opposed to importing mathtext on demand only, but that would be new.
Cheers,
Mike

On 8/1/07, Michael Droettboom <md...@st...> wrote:
> >> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> >> line 1189, in Vli
> >> st
> >> def vpack(self, h=0., m='additional', l=float('inf')):
> >> ValueError: invalid literal for float(): inf
> I'm not opposed to importing mathtext on demand only, but that would be new.
I see, it wasn't clear to me on my first look that the bug was
triggered at module load time. I had assumed the bug was triggered by
*using* mathtext. Since you seem to have found the fix (numpy.inf)
I'm happy to leave it as is.
JDH

Do you get any output (e.g. a traceback) or it just goes poof? (You may 
need to run it from the command line if you aren't already).
Cheers,
Mike
william ratcliff wrote:
> Now, it no longer gives rise to the previous error, but python crashes 
> when I run the embedding_in_wx4.py example. 
>
> William
>
> On 8/1/07, *John Hunter* <jd...@gm... 
> <mailto:jd...@gm...>> wrote:
>
> On 8/1/07, Michael Droettboom < md...@st...
> <mailto:md...@st...>> wrote:
>
> > >> "c:\python25\Lib\site-packages\matplotlib\mathtext.py",
> > >> line 1189, in Vli
> > >> st
> > >> def vpack(self, h=0., m='additional', l=float('inf')):
> > >> ValueError: invalid literal for float(): inf
>
> > I'm not opposed to importing mathtext on demand only, but that
> would be new.
>
> I see, it wasn't clear to me on my first look that the bug was
> triggered at module load time. I had assumed the bug was triggered by
> *using* mathtext. Since you seem to have found the fix (numpy.inf)
> I'm happy to leave it as is.
>
> JDH
>
>