[matplotlib-devel] MacOS X backend possible leak

2011-01-27 Thread Hubert Holin
Paris (U.E.), le 28/01/2011

Bonsoir

I am trying to code a specialized data visualization technique 
(quite old and mostly forgotten), which I will release under the Python 
Software License. I want to customize the navigation bar read-out so as to give 
more relevant information than cartesian coordinates. I am not quite there yet, 
and may be missing a few things, but I have run into a problem.

If I try to output a specific string to the navigation bar, 
using

fig.canvas.toolbar.set_message("Toto")

then sure enough the correct message appears in the right place. However, using 
the MacOS X backend, I get the leak message reproduced at the end of this 
message. I would much prefer to code in a backend-agnostic manner. Could 
someone please point me in the right direction?

Merci

        Hubert Holin

 8>< === ><8 
2011-01-27 15:22:27.892 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x10ad544c0 of class NSCFString autoreleased with no pool in place - just 
leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x103193750 0x1dd78 0x1000e4910 
0x100033df0 0x1dd78 0x1000eb2f0 0x1000ed840 0x1000eb098 0x1000eaffc 
0x1000eaffc 0x1000ed840 0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 
0x1000eb098 0x1000eaffc 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc 0x100118d60 
0x100133654 0x10f54 0x3)
2011-01-27 15:22:27.895 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x10ad89aa0 of class NSSelectionArray autoreleased with no pool in place - just 
leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff81618b2c 0x7fff81618abc 
0x7fff815499b4 0x7fff815496b8 0x7fff81632598 0x7fff8152a814 0x7fff8152a2d8 
0x103193770 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0 
0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 0x1000e8300 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000ed840 
0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 
0x1000ed950 0x1001188bc 0x100118d60 0x100133654 0x10f54 0x3)
2011-01-27 15:22:27.897 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x10ad70ad0 of class NSSelectionArray autoreleased with no pool in place - just 
leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff8161a1e0 0x7fff81618e64 
0x7fff81618abc 0x7fff815499b4 0x7fff815496b8 0x7fff81632598 0x7fff8152a814 
0x7fff8152a2d8 0x103193770 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 
0x1000eb2f0 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 
0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 
0x1000ed840 0x1000ed950 0x1001188bc 0x100118d60 0x100133654 0x10f54 
0x3)
2011-01-27 15:22:27.899 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x1025f9350 of class NSSelectionArray autoreleased with no pool in place - just 
leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff8161ad88 0x7fff816192f4 
0x7fff81618abc 0x7fff815499b4 0x7fff815496b8 0x7fff81632598 0x7fff8152a814 
0x7fff8152a2d8 0x103193770 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 
0x1000eb2f0 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 
0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 
0x1000ed840 0x1000ed950 0x1001188bc 0x100118d60 0x100133654 0x10f54 
0x3)
2011-01-27 15:22:27.901 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x10ad6d480 of class NSAttributeDictionaryEnumerator autoreleased with no pool 
in place - just leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff83041f08 0x7fff83042100 
0x7fff83044bf0 0x7fff830449a8 0x7fff81619a58 0x7fff81618abc 0x7fff815499b4 
0x7fff815496b8 0x7fff81632598 0x7fff8152a814 0x7fff8152a2d8 0x103193770 
0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0 0x1000ed840 
0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 0x1000e8300 0x1000ed840 
0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000ed840 0x1000eb098 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 0x1000ed950 
0x1001188bc 0x100118d60 0x100133654 0x10f54 0x3)
2011-01-27 15:22:27.903 Python[747:10b] *** _NSAutoreleaseNoPool(): Object 
0x10ad8a8f0 of class NSCFDictionary autoreleased with no pool in place - just 
leaking
Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff81619a58 0x7fff81618abc 
0x7fff815499b4 0x7fff815496b8 0x7fff81632598 0x7fff8152a814 0x7fff8152a2d8 
0x103193770 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0 
0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 0x1000e8300 
0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000ed840 
0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840 
0x1000ed950 0x1001188bc 0x100118d60 0

Re: [matplotlib-devel] I have a Mac!

2013-08-16 Thread Hubert Holin
Paris (U.E.), le 17/08/2013

Bonsoir

Both on my old (PPC) Mac at work and on my (somewhat) more 
recent (Intel) Mac at home, I install from source (no homebrew, Fink, MacPorts 
or whatever, though these are great to-have items!): latest stable release for 
Python itself (2.7 & 3.3), the rest from repositories. I guess I am lucky not 
to have run into a wall, or perhaps just plain stubborn… There is perhaps a 
lack of functionality (I have not delved into IPython notebooks, and Tcl/Tk 
usually is a nightmare for my old box), but for what I have, or want, to do, it 
just works. I should add that at work I am behind a really "thick" firewall, so 
I pay close attention to all dependencies and install these before what depends 
on them (obviously!, though there are (partly) circular references which 
require more work); I do sometimes have to download at home and transfer via 
key…

At any rate, a well-documented (I just whent ahead and kept no 
notes… sorry!) installation roadmap would really be a usefull thing.

And thanks for the great woks which goes into matplotlib (it really 
made my life more bearable)!

        Hubert Holin


On 16 août 2013, at 16:42, Jens Nielsen  wrote:

> On my mac box I'm just using homebrew www.brew.sh to install the latest 
> python along with all non python dependencies and the python dependencies via 
> pip. This seems to work great most of the time. 
> 
> Jens
> 
> 
> On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom  wrote:
> We actually discussed this very issue yesterday in our Google hangout about 
> continuous integration.  We're probably going to need to script a full setup 
> from a clean Mac + XCode to a working matplotlib development environment in 
> order to make that happen, and obviously that will be shared with the world.  
> Things are even more complex on Windows, and I'd like to do that there, too.  
> So stay tuned.
> 
> Mike
> 
> 
> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official" 
>> instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a 
>> linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom  wrote:
>> Thanks to the gracious donation from Hans Petter Langtangen and the
>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>> keep on top of changes that affect the Mac builds and to better track
>> down Mac-only issues.
>> 
>> Stay tuned over the next few weeks and months as we will most likely be
>> using some more of these funds to pay for hosted continuous integration
>> services (as discussed yesterday in our MEP19 Google Hangout).
>> 
>> Cheers,
>> Mike
>> 
>> 
>> 
>> --
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> ___
>> Matplotlib-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk

Re: [matplotlib-devel] I have a Mac!

2013-08-16 Thread Hubert Holin
Paris (U.E.), le 17/08/2013

Bonsoir

Building for various architectures than one is on, on the Mac, 
is something I regretfully bought into (Apple in the beginning told us to go 
for it) but latter found out to be a useless hassle (Apple silently removing 
PPC64 dev tools anybody? Urgh!)

Bon courage

Hubert Holin


On 16 août 2013, at 18:08, Chris Barker - NOAA Federal  
wrote:

> On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom  wrote:
>> We actually discussed this very issue yesterday in our Google hangout about
>> continuous integration.  We're probably going to need to script a full setup
>> from a clean Mac + XCode to a working matplotlib development environment in
>> order to make that happen,
> 
> Just a note -- this did NOT "just work" the other day for me -- it
> found the freetype libs that OS-X has in the X11 build, but didn't
> like them at compile time. I haven't debugged it yet, sorry.
> 
> But the real trick here is what you want to build: which OS-X versions
> do you want to support? which architectures? which Python Build(s)?
> 
> What I've been planning on doing is setting up a gitHub (or something)
> project for building the various dependencies that various python
> packages need -- there are a few that are broadly used: libpng,
> libfreetype (used by MPL, PIL, wxPython, ???). The idea is that if you
> wanted to build MPL (or PIL, or ???) you'd grab the
> MacPyton_Dependencies project, build it, then go from there.
> 
> Anyone want to help? It just feels like we are all repeating
> each-others work a LOT here!
> 
> NOTE: the big issues come up if you want to build binaries that are
> re-distributable (as a package, or with py2app, or???). In this case,
> you need binaries that can run on perhaps older machines than the one
> you're building on, or a different architecture. Building to run on
> the machine it's built-on is a lot easier. (particularly with macport
> or homebrew)
> 
> -CHB
> 
> 
> 
> 
> 
> 
> 
> 
> and obviously that will be shared with the world.
>> Things are even more complex on Windows, and I'd like to do that there, too.
>> So stay tuned.
>> 
>> Mike
>> 
>> 
>> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> 
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official"
>> instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a
>> linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom  wrote:
>>> 
>>> Thanks to the gracious donation from Hans Petter Langtangen and the
>>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>>> keep on top of changes that affect the Mac builds and to better track
>>> down Mac-only issues.
>>> 
>>> Stay tuned over the next few weeks and months as we will most likely be
>>> using some more of these funds to pay for hosted continuous integration
>>> services (as discussed yesterday in our MEP19 Google Hangout).
>>> 
>>> Cheers,
>>> Mike
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>>> It's a free troubleshooting tool designed for production.
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>> ___
>>> Matplotlib-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
>> 
>> 
>> 
>> --
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> ___
>> Matplotlib-devel mailing list
>> Matplotlib

Re: [matplotlib-devel] I have a Mac!

2013-08-16 Thread Hubert Holin
Paris (U.E.), le 17/08/2013

Bonsoir

Pandas does compile on a plain Mac (I use it at work), though I 
have not pulled since may the 22nd, so things may have changed.

Bon courage

Hubert Holin


On 16 août 2013, at 18:27, Paul Hobson  wrote:

> 
> 
> 
> On Fri, Aug 16, 2013 at 7:42 AM, Jens Nielsen  wrote:
> On my mac box I'm just using homebrew www.brew.sh to install the latest 
> python along with all non python dependencies and the python dependencies via 
> pip. This seems to work great most of the time. 
> 
> Jens
> 
> 
> Yeah. I'm sure Homebrew has made a lot of progress since I last tried. A 
> couple of years ago I found a couple of blog posts that all walked you 
> through different ways of getting a dev environment going for the various 
> flavors of python installed (it was never /all/ available through Homebrew). 
> Sometimes one would work for me. Eventually I just said, "screw it" and 
> installed Anaconda for use and fired up a VM for development.
> 
> I guess my point is that it'd be nice to have documentation on matplotlib.org 
> that says, "Here's how Mike D. sets up his Mac to build mpl from source". 
> Because if it works well enough for Mike, it'll probably work well enough for 
> me. (Now if only pandas would do the same thing.)
> 
> A similar document would be great for Windows too.
> -paul
> 
>  
> On Fri, Aug 16, 2013 at 3:32 PM, Michael Droettboom  wrote:
> We actually discussed this very issue yesterday in our Google hangout about 
> continuous integration.  We're probably going to need to script a full setup 
> from a clean Mac + XCode to a working matplotlib development environment in 
> order to make that happen, and obviously that will be shared with the world.  
> Things are even more complex on Windows, and I'd like to do that there, too.  
> So stay tuned.
> 
> Mike
> 
> 
> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official" 
>> instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a 
>> linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom  wrote:
>> Thanks to the gracious donation from Hans Petter Langtangen and the
>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>> keep on top of changes that affect the Mac builds and to better track
>> down Mac-only issues.
>> 
>> Stay tuned over the next few weeks and months as we will most likely be
>> using some more of these funds to pay for hosted continuous integration
>> services (as discussed yesterday in our MEP19 Google Hangout).
>> 
>> Cheers,
>> Mike
> 
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] Dealing (gracefully?) with problematic fonts

2014-12-07 Thread Hubert Holin
Paris (U.E.), le 08/12/2014

The transition to MacOS X 10.10 (and more precisely 10.10.1) is proving 
quite problematic. One problem I am currently stuck with prevents me from using 
matplotlib.

Whether using matplotlib 1.4.2 and freetype 2.3.12 (combination A) or 
matplotlib 59eda228e6a77e842c63078c3af870868120e70c and freetype 2.5.3 
(combination B), importing matplotlib.pylab results in a crash. I have not 
tried other combinations…

In the case of combination A, the crash occurs because FT_Set_Char_Size 
(ft2font.cpp, line 909) returns an error because of the font 
“/System/Library/Fonts/Apple Color Emoji.ttf” and an uncaught exception is then 
thrown on line 916.

In the case of combination B, the crash occurs because FT_Set_Char_Size 
(ft2font.cpp, line 508) returns an error because of an unidentified font (I 
could not quickly find a way, in this version of the file, to access the name 
of the font being tested…) and an uncaught exception is then thrown on line 510.

As the font “/System/Library/Fonts/Apple Color Emoji.ttf” is a system 
font, and therefore off-limits to most users, it would be unadvisable to mess 
with it (including removing it from the system), and even though I would 
personally be quite unlikely to use it in conjunction with matplotlib, our 
Japanese colleagues might see things differently. At any rate, it does not seem 
to be corrupt (it may be complex, though, as TypeTool displays it differently 
from Font Book, which is hardly surprising as it is a *color* font…).

Barring a more sophisticated treatment of such fonts, could it be 
possible to catch the exception, just not take these fonts into account, and 
move on to the rest of the work? I have not grasped the organisation of the 
source that well to know where to propose a patch. Any hint welcome!

Hubert Holin

P.S.: I have also not found a way of creating a figure without having to import 
matplotlib.pylab.


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel