matplotlib-devel Mailing List for matplotlib

Hi Ondrej,
Good things last and take time.
2010年4月13日 Ondrej Certik <on...@ce...>:
> I am now getting the exact same problem with pylab and FEMhub and Mac.
> I used http://sagemath.org/packages/standard/matplotlib-0.99.1.p4.spkg:
It might a different problem than just architecture mismatch. But
maybe I'm getting something wrong and misunderstand you.
Michael, notice that 0.99.1 seems to the last version before your
commit af9954d46e5 which introduces versioning of the fontcache. (It
is not tagged in git, only the commit message reveals it:
8398d9bd2c47.
I cannot see from http://trac.sagemath.org/sage_trac/ticket/7022 what
happened between the sagemath matplotlib-0.99.1.p2.spkg to
matplotlib-0.99.1.p4.spkg (patch 2 => patch 4). But the last post by
jhpalmieri on that page might be related: "[...] But with my computer,
"uname -r" returns "10.2.0", not "10.0.0". [...]" On my system it
returns currently 10.8.0 (I think since it's OS X 10.6.8).
> ondrej@bsd:~/repos/femhub-0.9.9.beta3-mac(master)$ ./femhub
> ----------------------------------------------------------------------
> | FEMhub Version 0.9.9.beta2, Release Date: 2010年04月02日        |
> | Type lab() for the GUI.                      |
> ----------------------------------------------------------------------
> In [1]: import pylab
> /Users/ondrej/repos/femhub-0.9.9.beta3-mac/local/lib/python2.6/site-packages/matplotlib/rcsetup.py:117:
> UserWarning: rcParams key "numerix" is obsolete and has no effect;
> please delete it from your matplotlibrc file
> warnings.warn('rcParams key "numerix" is obsolete and has no effect;\n'
> /Users/ondrej/repos/femhub-0.9.9.beta3-mac/local/bin/sage-sage: line
> 203: 28516 Abort trap       sage-ipython "$@" -i
>
> It's using the "bsd" Mac machine from William, I guess the same as
> John was using above.
>
> Has anybody figured out a solution? Apparently Sage must work on the
> Mac, so it must be something different than just matplotlib?
Can you please check if you do have /Library/Fonts/NISC18030.ttf on
your system and maybe do a ``stat -f "%c"
/Library/Fonts/NISC18030.ttf`` on it? For me, this one generates a
Bus error (32bit) / Abort trap (64bit) on importing matplotlib.figure,
for example. My issue is related to loading that font file I
specified. It might a different font file for you and it might also
be totally unrelated at all :-/
Or maybe you solved the problem in the meantime?
Do you still have this machine? William, assumed he's William Stein,
was the one who posted
http://groups.google.com/group/sage-devel/browse_thread/thread/2c538915abc99946
in 2009, and who was able to partly track it down.
>From the page http://trac.sagemath.org/sage_trac/ticket/7022 I see
that exactly that font file was installed on it (probably).
Thanks,
Friedrich
> Some
> other package, that we have in femhub, but not in Sage, or some
> different version of something. Here is a list of packages that I have
> installed:
>
> ondrej@bsd:~/repos/femhub-0.9.9.beta3-mac(master)$ ./femhub -i
> Currently installed packages:
> blas-20070724
> bzip2-1.0.5
> cmake-2.6.2.p1
> configobj-4.5.3
> cython-0.12.1
> dir-0.1
> docutils-0.5.p0
> femhub-lab-97141eb
> fipy-2.1-eb4aacf
> fortran-20071120.p8
> freetype-2.3.5.p2
> gnutls-2.2.1.p3
> hermes2d-9bbfd39
> ipython-bzr1174
> jinja-1.2.p0
> judy-1.0.5.p1
> lapack-20071123.p1
> libfemhub-78c07cb
> libgcrypt-1.4.3.p2
> libgpg_error-1.6.p2
> libpng-1.2.35.p0
> matplotlib-0.99.1.p4
> mayavi-3.3.1.p2
> mesa-7.4.4.p3
> numpy-1.3.0.p2
> pexpect-2.0.p3
> prereq-0.3
> pygments-0.11.1.p0
> pyparsing-1.5.2
> pysparse-1.1-6301cea
> python-2.6.4.p7
> python_gnutls-1.1.4.p7
> readline-6.0
> sage_scripts-3.4.2
> scipy-0.7.p4
> setuptools-0.6c9.p0
> sfepy-2009.3
> sphinx-0.6.3.p4
> swig-1.3.36
> sympy-5d78c29
> termcap-1.3.1.p1
> twisted-9.0.p2
> vtk-cvs-20090316-minimal.p6
> zlib-1.2.3.p5
Looks ok. But I didn't check it in detail. I think it might be unrelated.

2010年12月21日 Russell E. Owen <ro...@uw...>:
> I built a binary installer for matplotlib trunk rev 8843 (because it
> leaks memory less than 1.0.0 release). I built it the same way I built
> the 1.0.0 binary
> <http://www.astro.washington.edu/users/rowen/BuildingMatplotlibForMac.htm
> l> on Mac OS X 10.4 using python.org Python 2.6.x (where x is probably
> 6).
>
> The binary is available here:
> <http://www.astro.washington.edu/users/rowen/python/matplotlib-1.0.0+svn8
> 843-python.org-py2.6-macosx10.3.dmg>
>
> It work fine on Mac OS X 10.4 and 10.5, but on 10.6 attempting to import
> pylab almost always segfaults (and the few times I've gotten it to work
> on 10.6 I can break it by deleting ~/.fontconfig and ~/.matplotlib and
> running Python again). I've tried it on newly created accounts and it
> segfaults. Another user of Snow Leopard first reported the problem. So
> it's not just me.
>
> I've appended part of a crash log.
>
> I built this binary the same way I built the matplotlib 1.0.0 binary,
> which has no problems.
>
> Any ideas?
Yap; did you make any progress on this?
I found that approximately that time on my machine was the
NISC18030.ttf font installed (I see it from the date of birth) and it
breaks the FontManager of nearly all matplotlibs including the recent
one (from last week).
Friedrich
> -- Russell
>
> Exception Type: EXC_BAD_ACCESS (SIGABRT)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Application Specific Information:
> abort() called
>
> Thread 0 Crashed: Dispatch queue: com.apple.main-thread
> 0  libSystem.B.dylib        0x90e1b176 __kill + 10
> 1  libSystem.B.dylib        0x90e1b168 kill$UNIX2003 + 32
> 2  libSystem.B.dylib        0x90ead89d raise + 26
> 3  libSystem.B.dylib        0x90ec39bc abort + 93
> 4  org.python.python        0x004e3e99 Py_FatalError + 73
> 5  libSystem.B.dylib        0x90e2046b _sigtramp + 43
> 6  ???               0000000000 0 + 0
> 7  libSystem.B.dylib        0x90e29378
> _Unwind_GetLanguageSpecificData + 24
> 8  libstdc++.6.dylib        0x940c4d86 __gxx_personality_v0 + 120
> 9  libgcc_s.1.dylib        0x0389f476 _Unwind_Backtrace + 278
> 10 libgcc_s.1.dylib        0x0389f890 _Unwind_Resume + 112
> 11 ft2font.so           0x03d5c3a3
> FT2Font::FT2Font(std::string) + 4385
> 12 ft2font.so           0x03d5c805
> ft2font_module::new_ft2font(Py::Tuple const&) + 505
> 13 ft2font.so           0x03dc89c2
> Py::ExtensionModule<ft2font_module>::invoke_method_varargs(void*,
> Py::Tuple const&) + 90
> 14 ft2font.so           0x03d7170c
> method_varargs_call_handler + 342
> 15 org.python.python        0x004bcd25 PyEval_EvalFrameEx + 19429
> 16 org.python.python        0x004bee9d PyEval_EvalCodeEx + 2109
> 17 org.python.python        0x004bcf0c PyEval_EvalFrameEx + 19916
Michael, here you probably have the traceback you asked for (assumed
I'm right with my assumption above) :-)
Friedrich

On Nov 12, 2011, at 2:47 AM, Paul Ivanov <piv...@gm...> wrote:
> On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root <ben...@ou...> wrote:
>> On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote:
>>> 
>>> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote:
>>>> 
>>>> Just wanted to re-ping the list, but include John and Ben directly:
>>>> 
>>>> can we get the appropriate commit tagged as v1.1.0 in the git repo?
>>>> 
>>> 
>>> Sure thing. I will add that tag.
>>> 
>>> Ben Root
>>> 
>> 
>> The best I can figure is that commit
>> 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release
>> announcement by John on Oct. 11. There was subsequently a commit on that
>> day to fix ipython links. I can't remember if that happened before or after
>> (I think after).
>> 
>> Can anybody concur?
> 
> On my PR to fix those links, John closed it and said he'd add it to
> the release branch, and they're up on the site, so I'd say that commit
> made it in. But I don't know if there were others afterward that made
> it in
> 
My memory is that the ipy pull request came just after the tarball, so I think you have it right Ben
> 

On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root <ben...@ou...> wrote:
> On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote:
>>
>> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote:
>>>
>>> Just wanted to re-ping the list, but include John and Ben directly:
>>>
>>> can we get the appropriate commit tagged as v1.1.0 in the git repo?
>>>
>>
>> Sure thing. I will add that tag.
>>
>> Ben Root
>>
>
> The best I can figure is that commit
> 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release
> announcement by John on Oct. 11. There was subsequently a commit on that
> day to fix ipython links. I can't remember if that happened before or after
> (I think after).
>
> Can anybody concur?
On my PR to fix those links, John closed it and said he'd add it to
the release branch, and they're up on the site, so I'd say that commit
made it in. But I don't know if there were others afterward that made
it in
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root <ben...@ou...> wrote:
> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote:
>
>> Just wanted to re-ping the list, but include John and Ben directly:
>>
>> can we get the appropriate commit tagged as v1.1.0 in the git repo?
>>
>>
> Sure thing. I will add that tag.
>
> Ben Root
>
>
The best I can figure is that commit
0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the
release announcement by John on Oct. 11. There was subsequently a commit
on that day to fix ipython links. I can't remember if that happened before
or after (I think after).
Can anybody concur?
Ben Root

On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov <piv...@gm...> wrote:
> Just wanted to re-ping the list, but include John and Ben directly:
>
> can we get the appropriate commit tagged as v1.1.0 in the git repo?
>
>
Sure thing. I will add that tag.
Ben Root