matplotlib-users Mailing List for matplotlib

Hello Eric,
Thanks for your reply and suggestions!
> Do you see the problem with any plot at all? E.g.,
<snip>
> Can you eliminate all traces of EPD, and then just cleanly install one version, and see if the problem still appears?
I cleanly installed EPD. Now, with only a single version (EPD 7.0-2, Python 2.7.1), I find that, interestingly,
a) In the 32-bit version (both when independent of and concurrent with 64-bit EPD), simply calling plot() crashes Python, both in bash and IPython shells.
b) In the 64-bit version, plot() goes through and creates the correct plot window but savefig() causes a crash when attempting to save in any format (pdf, ps, svg, png).
As in my original mail the error messages echoed to terminal are "Abort trap" and "Bus error" for 64-bit and 32-bit versions, respectively.
Thus, I wish to believe that there is some bug in matplotlib which is possibly not local to savefig() alone (at least for the 32-bit version). In this regard, I wish to request you as well as list members to advise me as to whether I should use version 1.0.0 ? If so, should I build from source or can I simply use the disk image file (and have it easy!) if I wish to replace the EPD bundled matplotlib ?
Thanks and Regards,
Kaushik

On 05/08/2011 08:58 AM, Kaushik Kalyanaraman wrote:
> Dear List,
>
> I use Matplotlib bundled with the Enthought Python Distribution (EPD) (both 32-bit and 64-bit versions). After a recent update, I find that my Python code (run either in a iPython shell or in bash shell) crashes while attempting to save figures to pdf files using savefig(). However, saving to other formats (png, ps, eps or svg) works fine. The error message echoed to the terminal are "Bus error" with 32-bit EPD and "Abort trap" with 64-bit EPD. Also, converting to pdf from one of the other four formats using *nix utilities like convert or ps2pdf go through fine (prompting to suspect that savefig has a bug). Unfortunately, in a short time, by looking at pyplot.py, I couldn't determine what could be causing this. Therefore, it would be really helpful if list members can provide any hints to fix this. I need to save a bunch of figures from existing code, and it would be great if I could do so without having to modify all savefig statements; additionally, I would prefer not to 
wr
> ite a shell script to perform the conversions to pdf considering the different directories that my figures are saved to.
>
> Also, a few searches using google did not throw up anything useful (although one relevant list archive suggested that if EPD alone is installed on a Mac, this error shouldn't be seen. Since this is the case for me, it didn't help.). The following are my specifications:
>
> Platform: Mac OS X 10.6.7
> Python version: 2.7.1
> Matplotlib version: 1.0.1
> EPD versions: 7.0-2 (both 32-bit and 64-bit)
>
> (Should I also post this to matplotlib-devel ?)
Probably not necessary; I think most of us on -devel read -users, and 
other people on -users may have useful insight and testing to contribute.
The pdf backend is not that different from the ps and svg backends, at 
least superficially--all of them are just python code that write 
files--so it is not obvious why it would cause the sort of problem that 
is usually associated with broken extension code.
Do you see the problem with any plot at all? E.g.,
import matplotlib
matplotlib.use("pdf")
import matplotlib.pyplot as plt
plt.plot([1,2])
plt.savefig("test.pdf")
My guess is that somehow something is getting confused between the two 
EPD versions, or something got confused during the update.
Can you eliminate all traces of EPD, and then just cleanly install one 
version, and see if the problem still appears?
Eric
>
> Thanks and Regards,
> Kaushik Kalyanaraman
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Dear List,
I use Matplotlib bundled with the Enthought Python Distribution (EPD) (both 32-bit and 64-bit versions). After a recent update, I find that my Python code (run either in a iPython shell or in bash shell) crashes while attempting to save figures to pdf files using savefig(). However, saving to other formats (png, ps, eps or svg) works fine. The error message echoed to the terminal are "Bus error" with 32-bit EPD and "Abort trap" with 64-bit EPD. Also, converting to pdf from one of the other four formats using *nix utilities like convert or ps2pdf go through fine (prompting to suspect that savefig has a bug). Unfortunately, in a short time, by looking at pyplot.py, I couldn't determine what could be causing this. Therefore, it would be really helpful if list members can provide any hints to fix this. I need to save a bunch of figures from existing code, and it would be great if I could do so without having to modify all savefig statements; additionally, I would prefer not to write a shell script to perform the conversions to pdf considering the different directories that my figures are saved to.
Also, a few searches using google did not throw up anything useful (although one relevant list archive suggested that if EPD alone is installed on a Mac, this error shouldn't be seen. Since this is the case for me, it didn't help.). The following are my specifications:
Platform: Mac OS X 10.6.7
Python version: 2.7.1
Matplotlib version: 1.0.1
EPD versions: 7.0-2 (both 32-bit and 64-bit)
(Should I also post this to matplotlib-devel ?)
Thanks and Regards,
Kaushik Kalyanaraman

On Sat, May 7, 2011 at 3:34 PM, Ondrej Certik <on...@ce...> wrote:
> Hi,
>
> I am using Matplotlib 1.0 precisely from this branch:
>
> https://github.com/matplotlib/matplotlib/tree/v1.0.x
>
> everything works on Linux, and on Mac, I am getting a segfault when I
> do "import pylab". Stacktrace is here:
>
> https://gist.github.com/960896
>
> I produced it by:
>
> gdb python
> (gdb) run
>>>> import pylab
>
> So it looks like TTF related. Here are some relevant links:
>
> https://github.com/qsnake/qsnake/issues/9
> http://trac.sagemath.org/sage_trac/ticket/7022
>
> I have tried to copy ontList.cache (from the Sage ticket 7022) in to
> ~/.qsnake/matplotlib/, but it still segfaults.
>
> Would anyone know what exactly the problem is, and how to fix it? I
> have numpy 1.6.0. Let me know which other debugging information is
> needed.
Min has solved it --- the problem was in using incorrect options to
build the package. Now we use the make.osx to set the environment
flags correctly and everything works now.
I have no idea what the problem was, but it's gone.
Ondrej