matplotlib-devel Mailing List for matplotlib (Page 79)

Brought to you by: cjgohlke, dsdale, efiring, heeres, and 8 others

matplotlib-devel — matplotlib developers

You can subscribe to this list here.

2003	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov (33)	Dec (20)
2004	Jan (7)	Feb (44)	Mar (51)	Apr (43)	May (43)	Jun (36)	Jul (61)	Aug (44)	Sep (25)	Oct (82)	Nov (97)	Dec (47)
2005	Jan (77)	Feb (143)	Mar (42)	Apr (31)	May (93)	Jun (93)	Jul (35)	Aug (78)	Sep (56)	Oct (44)	Nov (72)	Dec (75)
2006	Jan (116)	Feb (99)	Mar (181)	Apr (171)	May (112)	Jun (86)	Jul (91)	Aug (111)	Sep (77)	Oct (72)	Nov (57)	Dec (51)
2007	Jan (64)	Feb (116)	Mar (70)	Apr (74)	May (53)	Jun (40)	Jul (519)	Aug (151)	Sep (132)	Oct (74)	Nov (282)	Dec (190)
2008	Jan (141)	Feb (67)	Mar (69)	Apr (96)	May (227)	Jun (404)	Jul (399)	Aug (96)	Sep (120)	Oct (205)	Nov (126)	Dec (261)
2009	Jan (136)	Feb (136)	Mar (119)	Apr (124)	May (155)	Jun (98)	Jul (136)	Aug (292)	Sep (174)	Oct (126)	Nov (126)	Dec (79)
2010	Jan (109)	Feb (83)	Mar (139)	Apr (91)	May (79)	Jun (164)	Jul (184)	Aug (146)	Sep (163)	Oct (128)	Nov (70)	Dec (73)
2011	Jan (235)	Feb (165)	Mar (147)	Apr (86)	May (74)	Jun (118)	Jul (65)	Aug (75)	Sep (162)	Oct (94)	Nov (48)	Dec (44)
2012	Jan (49)	Feb (40)	Mar (88)	Apr (35)	May (52)	Jun (69)	Jul (90)	Aug (123)	Sep (112)	Oct (120)	Nov (105)	Dec (116)
2013	Jan (76)	Feb (26)	Mar (78)	Apr (43)	May (61)	Jun (53)	Jul (147)	Aug (85)	Sep (83)	Oct (122)	Nov (18)	Dec (27)
2014	Jan (58)	Feb (25)	Mar (49)	Apr (17)	May (29)	Jun (39)	Jul (53)	Aug (52)	Sep (35)	Oct (47)	Nov (110)	Dec (27)
2015	Jan (50)	Feb (93)	Mar (96)	Apr (30)	May (55)	Jun (83)	Jul (44)	Aug (8)	Sep (5)	Oct	Nov (1)	Dec (1)
2016	Jan	Feb	Mar (1)	Apr	May	Jun (2)	Jul	Aug (3)	Sep (1)	Oct (3)	Nov	Dec
2017	Jan	Feb (5)	Mar	Apr	May	Jun	Jul (3)	Aug	Sep (7)	Oct	Nov	Dec
2018	Jan	Feb	Mar	Apr	May	Jun	Jul (2)	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 77 78 79 80 81 .. 554 > >> (Page 79 of 554)

Re: [matplotlib-devel] Experiments in removing/replacing PyCXX

From: Jason G. <jas...@cr...> - 2012-11-30 14:14:01

On 11/29/12 10:59 AM, Michael Droettboom wrote:
> I've not had
> much luck with Cython for this kind of thing in the past, but I know it
> is popular.

I'm curious about what problems you've run into and how long it was.  In 
the past, Cython hasn't supported C++ very well, but the situation has 
greatly improved recently.  See 
http://docs.cython.org/src/userguide/wrapping_CPlusPlus.html for some 
details.

Thanks,

Jason

Re: [matplotlib-devel] Experiments in removing/replacing PyCXX

From: Michael D. <md...@st...> - 2012-11-30 14:07:09

Thanks, Michiel.

If you read between the lines of what I was saying, that is basically 
where I fall as well.  There seems to be a lot of desire to use Cython 
to make the code more accessible, however, and I'm willing to consider 
it if it can be shown to be superior to the raw C/API for this task -- 
I'm not sure it is -- I always seem to end up with things that are more 
lines of code with more obscure workarounds than just coding in C directly.

Cheers,
Mike

On 11/29/2012 08:47 PM, Michiel de Hoon wrote:
> Hi,
>
> The Mac OS X backend is entirely written in C (with some Objective-C elements where necessary). AFAICT, this is the largest C/C++ code in matplotlib. This backend was written from scratch without using Cython, SWIG, or Boost.Python. From my experience, I would prefer to write such extensions in C directly rather than relying on Cython, SWIG, or Boost.Python, because those approaches would lead to another dependency (for developers at least), and requires developers to learn how to code in them. Which may not be very hard, but we may as well avoid that if possible.
>
> I'd be happy to help out with the conversion of the other extensions from CXX to C. I would need some help though to use github appropriately.
>
> Best,
> -Michiel.
>
>
> --- On Thu, 11/29/12, Michael Droettboom <md...@st...> wrote:
>
>> From: Michael Droettboom <md...@st...>
>> Subject: [matplotlib-devel] Experiments in removing/replacing PyCXX
>> To: "mat...@li..." <mat...@li...>
>> Date: Thursday, November 29, 2012, 11:59 AM
>> Given the slow pace of development on
>> PyCXX, I know it has been the
>> desire of some here to remove our dependency on it.
>>
>> I thought a helpful starting point to evaluate the
>> alternatives would be
>> to restructure one of our extensions to not use PyCXX
>> anymore.  I've
>> taken the PNG extension, which is reasonably straightforward
>> in that it
>> doesn't define any custom types, but does have some low
>> level C-wrapping
>> challenges, and separated out the Python-specific parts from
>> the
>> libpng-specific parts.  The Python-specific parts are
>> now written using
>> the "raw" Python C/API. The other part still uses C++ (not
>> C) and does
>> throw exceptions, but doesn't use classes or templates or
>> anything else
>> that can be difficult to wrap.  All of this is on my
>> "no_cxx" branch.
>>
>> Now here's the challenge: can we do better than this using
>> any of the
>> available wrapping tools?  Cython, SWIG, Boost.Python
>> etc.? I've not had
>> much luck with Cython for this kind of thing in the past,
>> but I know it
>> is popular.  Perhaps someone with more Cython
>> experience would want to
>> take a crack at this and then we could have something
>> concrete to compare...
>>
>> Cheers,
>> Mike
>>
>> ------------------------------------------------------------------------------
>> Keep yourself connected to Go Parallel:
>> VERIFY Test and improve your parallel project with help from
>> experts
>> and peers. http://goparallel.sourceforge.net
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>

Re: [matplotlib-devel] Use of meta on Artist

From: Jae-Joon L. <lee...@gm...> - 2012-11-30 13:49:56

Note that we already use a decorator for a similar purpose
(allow_rasterization).

Also, please note that the "draw" method is not just for drawing things.
There are other things being done within the draw method, and I think some
of them still need to be done even though the artist is invisible.

My personal inclination on this issue is to refactor the "draw" method, the
only method being called during the drawing time. But, yes there are
sideeffects.

Regards,

-JJ



On Tue, Nov 27, 2012 at 3:40 AM, Ryan May <rm...@gm...> wrote:

> On Mon, Nov 26, 2012 at 12:23 PM, Eric Firing <ef...@ha...> wrote:
>
>> On 2012/11/26 7:12 AM, Michael Droettboom wrote:
>> > The problem is that I don't think we can do this for all artists.  Some
>> > may need to create groupings, or push and pop state even if they are
>> > "invisible".  For instance, this is used in the SVG backend to create
>> > named groupings (possibly empty) that are referenced from Javascript to
>> > provide interactivity.  I think I'd rather keep this to the contained
>> > solution in the PR and not try to generalize it beyond that.
>> >
>> > If we did want to generalize, this would only apply to "leaf node"
>> > artists, and not artists that simply exist to contain other artists --
>> > and conceivably we could implement that using either a decorator or
>> > explicit chaining to a base class, but in any event it would have to be
>> > a manual process to determine which artists this would apply to.  We
>> > could insert a class in the heirarchy of "ConcreteArtist" (or somesuch)
>> > to handle this.
>>
>> I think we should be rather conservative about this sort of thing.
>> Sometimes it is better to just explicitly put the two lines in each
>> method than to come up with machinery to do it for you.  Each level of
>> depth in an inheritance hierarchy or "meta" chain is an additional level
>> of complexity for someone reading the code.  And if someone forgets to
>> put in those lines, the penalty is typically from small to nil; but if
>> they are put in automatically by fancy methods, and they are not really
>> wanted or something else goes wrong, it can make debugging painful.
>
>
> I think you and Mike are skirting around a key point here. You can always
> add the line if you need it, but if you don't need it (or can't use it), by
> use of a metaclass, there's no way to "opt out" so to speak.
>
> I'll also add that we don't need to add any more indirection (i.e. another
> Python function call) to our drawing stack--we really need to be doing
> everything possible to take every last millisecond out of the call to
> draw().
>
> Ryan
>
> --
> Ryan May
> Graduate Research Assistant
> School of Meteorology
> University of Oklahoma
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Re: [matplotlib-devel] Experiments in removing/replacing PyCXX

From: Michiel de H. <mjl...@ya...> - 2012-11-30 01:47:49

Hi,

The Mac OS X backend is entirely written in C (with some Objective-C elements where necessary). AFAICT, this is the largest C/C++ code in matplotlib. This backend was written from scratch without using Cython, SWIG, or Boost.Python. From my experience, I would prefer to write such extensions in C directly rather than relying on Cython, SWIG, or Boost.Python, because those approaches would lead to another dependency (for developers at least), and requires developers to learn how to code in them. Which may not be very hard, but we may as well avoid that if possible.

I'd be happy to help out with the conversion of the other extensions from CXX to C. I would need some help though to use github appropriately.

Best,
-Michiel.


--- On Thu, 11/29/12, Michael Droettboom <md...@st...> wrote:

> From: Michael Droettboom <md...@st...>
> Subject: [matplotlib-devel] Experiments in removing/replacing PyCXX
> To: "mat...@li..." <mat...@li...>
> Date: Thursday, November 29, 2012, 11:59 AM
> Given the slow pace of development on
> PyCXX, I know it has been the 
> desire of some here to remove our dependency on it.
> 
> I thought a helpful starting point to evaluate the
> alternatives would be 
> to restructure one of our extensions to not use PyCXX
> anymore.  I've 
> taken the PNG extension, which is reasonably straightforward
> in that it 
> doesn't define any custom types, but does have some low
> level C-wrapping 
> challenges, and separated out the Python-specific parts from
> the 
> libpng-specific parts.  The Python-specific parts are
> now written using 
> the "raw" Python C/API. The other part still uses C++ (not
> C) and does 
> throw exceptions, but doesn't use classes or templates or
> anything else 
> that can be difficult to wrap.  All of this is on my
> "no_cxx" branch.
> 
> Now here's the challenge: can we do better than this using
> any of the 
> available wrapping tools?  Cython, SWIG, Boost.Python
> etc.? I've not had 
> much luck with Cython for this kind of thing in the past,
> but I know it 
> is popular.  Perhaps someone with more Cython
> experience would want to 
> take a crack at this and then we could have something
> concrete to compare...
> 
> Cheers,
> Mike
> 
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel: 
> VERIFY Test and improve your parallel project with help from
> experts 
> and peers. http://goparallel.sourceforge.net
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

[matplotlib-devel] Experiments in removing/replacing PyCXX

From: Michael D. <md...@st...> - 2012-11-29 17:00:09

Given the slow pace of development on PyCXX, I know it has been the 
desire of some here to remove our dependency on it.

I thought a helpful starting point to evaluate the alternatives would be 
to restructure one of our extensions to not use PyCXX anymore.  I've 
taken the PNG extension, which is reasonably straightforward in that it 
doesn't define any custom types, but does have some low level C-wrapping 
challenges, and separated out the Python-specific parts from the 
libpng-specific parts.  The Python-specific parts are now written using 
the "raw" Python C/API. The other part still uses C++ (not C) and does 
throw exceptions, but doesn't use classes or templates or anything else 
that can be difficult to wrap.  All of this is on my "no_cxx" branch.

Now here's the challenge: can we do better than this using any of the 
available wrapping tools?  Cython, SWIG, Boost.Python etc.? I've not had 
much luck with Cython for this kind of thing in the past, but I know it 
is popular.  Perhaps someone with more Cython experience would want to 
take a crack at this and then we could have something concrete to compare...

Cheers,
Mike

Re: [matplotlib-devel] Issues with building Matplotlib 1.2.0 on RHEL5

From: Tejashri K. <tej...@gm...> - 2012-11-29 06:40:25

Hi,

Yes, I am trying to build against custom-built libraries.
and thanks for the suggestion about LDFLAGS, but that didn't work too.

It still picks up system versions of the libraries.
What has pkg-config got to do with this? (I havent worked extensively with
linux so not much idea)

I think I should also mention that I am trying to build matplotlib against
Python 3.2.3.

Regards,
Tej

On Tue, Nov 27, 2012 at 10:49 PM, Michael Droettboom <md...@st...>wrote:

> You can try setting LDFLAGS to "-L/path/to/your/libraries".

[matplotlib-devel] Fwd: Mpl mailing list archive and other sourceforge related problems

From: Phil E. <pel...@gm...> - 2012-11-28 12:56:11

I've just submitted a PR which changes the link we provide for the web
archiving of our mpl mailing lists (
https://github.com/matplotlib/matplotlib/pull/1540) as it appears that the
sourceforge archiving stopped updating in July...

Given that the mailinglists are provided/hosted by sourceforge in the first
place, I find it concerning that the sourceforge archiving is in this
state. Their addition of advertising on our mailinglist posts makes me even
less enamoured with the service we receive.

It makes me wonder whether we should consider alternative service providers
for our mailing lists? I notice the ipython/numpy/scipy mailinglists are
all hosted via scipy.org and wonder if we should consider asking to have
our mpl mailinglists hosted there too?

Thoughts?

Cheers,

Phil

Re: [matplotlib-devel] Issues with building Matplotlib 1.2.0 on RHEL5

From: Michael D. <md...@st...> - 2012-11-27 17:49:41

If I understand it correctly, you are trying to build against 
custom-built copies of these libraries in a non-default location?

You can try setting LDFLAGS to "-L/path/to/your/libraries".

Mike

On 11/26/2012 12:47 AM, Tejashri Kandolkar wrote:
> Hi,
>
> I am trying to build matplotlib 1.2.0 from source on my RHEL6 machine.
> I am using freetype 2.4.2 and libpng 1.2.42
>
> I am using basedirlist (from setup.cfg) to mention the location of the 
> include folder (for all headers), I am not sure though where I should 
> mention the location of the .so files of these 3rd party libraries.
>
> During build of matplotlib it picks up system installed versions of 
> freetype and libpng.(build log attached)
>
> Is there any other place where I need to set the location of these 
> third party libraries?
>
> Regards,
> Tej
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Use of meta on Artist

From: Ryan M. <rm...@gm...> - 2012-11-26 18:40:35

On Mon, Nov 26, 2012 at 12:23 PM, Eric Firing <ef...@ha...> wrote:

> On 2012/11/26 7:12 AM, Michael Droettboom wrote:
> > The problem is that I don't think we can do this for all artists.  Some
> > may need to create groupings, or push and pop state even if they are
> > "invisible".  For instance, this is used in the SVG backend to create
> > named groupings (possibly empty) that are referenced from Javascript to
> > provide interactivity.  I think I'd rather keep this to the contained
> > solution in the PR and not try to generalize it beyond that.
> >
> > If we did want to generalize, this would only apply to "leaf node"
> > artists, and not artists that simply exist to contain other artists --
> > and conceivably we could implement that using either a decorator or
> > explicit chaining to a base class, but in any event it would have to be
> > a manual process to determine which artists this would apply to.  We
> > could insert a class in the heirarchy of "ConcreteArtist" (or somesuch)
> > to handle this.
>
> I think we should be rather conservative about this sort of thing.
> Sometimes it is better to just explicitly put the two lines in each
> method than to come up with machinery to do it for you.  Each level of
> depth in an inheritance hierarchy or "meta" chain is an additional level
> of complexity for someone reading the code.  And if someone forgets to
> put in those lines, the penalty is typically from small to nil; but if
> they are put in automatically by fancy methods, and they are not really
> wanted or something else goes wrong, it can make debugging painful.


I think you and Mike are skirting around a key point here. You can always
add the line if you need it, but if you don't need it (or can't use it), by
use of a metaclass, there's no way to "opt out" so to speak.

I'll also add that we don't need to add any more indirection (i.e. another
Python function call) to our drawing stack--we really need to be doing
everything possible to take every last millisecond out of the call to
draw().

Ryan

-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Re: [matplotlib-devel] Use of meta on Artist

From: Eric F. <ef...@ha...> - 2012-11-26 18:23:29

On 2012/11/26 7:12 AM, Michael Droettboom wrote:
> The problem is that I don't think we can do this for all artists.  Some
> may need to create groupings, or push and pop state even if they are
> "invisible".  For instance, this is used in the SVG backend to create
> named groupings (possibly empty) that are referenced from Javascript to
> provide interactivity.  I think I'd rather keep this to the contained
> solution in the PR and not try to generalize it beyond that.
>
> If we did want to generalize, this would only apply to "leaf node"
> artists, and not artists that simply exist to contain other artists --
> and conceivably we could implement that using either a decorator or
> explicit chaining to a base class, but in any event it would have to be
> a manual process to determine which artists this would apply to.  We
> could insert a class in the heirarchy of "ConcreteArtist" (or somesuch)
> to handle this.

I think we should be rather conservative about this sort of thing. 
Sometimes it is better to just explicitly put the two lines in each 
method than to come up with machinery to do it for you.  Each level of 
depth in an inheritance hierarchy or "meta" chain is an additional level 
of complexity for someone reading the code.  And if someone forgets to 
put in those lines, the penalty is typically from small to nil; but if 
they are put in automatically by fancy methods, and they are not really 
wanted or something else goes wrong, it can make debugging painful.

Eric


>
> Mike
>
> On 11/26/2012 06:17 AM, Phil Elson wrote:
>> I've just been reviewing a really useful PR
>> (https://github.com/matplotlib/matplotlib/pull/1531) from Pierre
>> Haessig which speeds up the drawing of non-visible artists by bringing
>> the following line to the top of the LineArtist's draw method:
>>
>>     if self.get_visible() is False:
>>         return
>>
>> This *does* fix the problem (and will fix the problem for all other
>> artists if applied in the same way), but it relies on a developer
>> remembering the rule of thumb that they must always start their draw
>> method with these two (simple) lines. Additionally, testing this
>> functionality is actually quite hard without resorting to timing the
>> execution.
>>
>> It made we wonder if there was a better approach to fixing this.
>> Having a decorator to do this for you is a good idea, except that a
>> developer would need to remember to decorate their subclass' draw
>> method, so the next level up is to use a metaclass to *always* wrap
>> the draw method with the "if visible" lines.
>>
>> An example of implementing this (apologies if the code doesn't come
>> out well in the email):
>>
>>
>> class ArtistMeta(type):
>>     def __new__(cls, classname, bases, class_dict):
>>         # replace the draw method with one which short-circuits if
>> self.visible is False
>>         draw_method = class_dict['draw']
>>         def draw(self, *args, **kwargs):
>>             if self.visible is False:
>>                 print 'draw **not** called with
>> visible={}'.format(self.visible)
>>                 return
>>             else:
>>                 return draw_method(self, *args, **kwargs)
>>         class_dict['draw'] = draw
>>
>>         return  type.__new__(cls, classname, bases, class_dict)
>>
>>
>> class Artist(object):
>>     __metaclass__ = ArtistMeta
>>
>>     def __init__(self, visible=True):
>>         self.visible = visible
>>
>>     def draw(self, renderer=None):
>>         print 'draw called with visible={}'.format(self.visible)
>>         return 'foobar'
>>
>>
>> class SubArtist(Artist):
>>     def draw(self, renderer=None):
>>         print "subclass' draw method"
>>         return Artist.draw(self, renderer=renderer)
>>
>>
>>
>>
>> With the following results:
>>
>>
>> >>> a = Artist().draw('wibble')
>> draw called with visible=True
>>
>> >>> b = Artist(False).draw('wibble')
>> draw **not** called with visible=False
>>
>> >>> c = SubArtist(True).draw('wibble')
>> subclass' draw method
>> draw called with visible=True
>>
>> >>> d = SubArtist(False).draw('wibble')
>> draw **not** called with visible=False
>>
>>
>>
>> In my eyes this makes testing the functionality possible without
>> timing (and is therefore an improvement), but I wanted to know how
>> others felt about the approach, and in particular, using more
>> metaclasses in matplotlib (a simple tutorial which I found useful:
>> http://www.voidspace.org.uk/python/articles/metaclasses.shtml).
>>
>>
>> Cheers,
>>
>> Phil

Re: [matplotlib-devel] Use of meta on Artist

From: Michael D. <md...@st...> - 2012-11-26 17:12:52

The problem is that I don't think we can do this for all artists.  Some 
may need to create groupings, or push and pop state even if they are 
"invisible".  For instance, this is used in the SVG backend to create 
named groupings (possibly empty) that are referenced from Javascript to 
provide interactivity.  I think I'd rather keep this to the contained 
solution in the PR and not try to generalize it beyond that.

If we did want to generalize, this would only apply to "leaf node" 
artists, and not artists that simply exist to contain other artists -- 
and conceivably we could implement that using either a decorator or 
explicit chaining to a base class, but in any event it would have to be 
a manual process to determine which artists this would apply to.  We 
could insert a class in the heirarchy of "ConcreteArtist" (or somesuch) 
to handle this.

Mike

On 11/26/2012 06:17 AM, Phil Elson wrote:
> I've just been reviewing a really useful PR 
> (https://github.com/matplotlib/matplotlib/pull/1531) from Pierre 
> Haessig which speeds up the drawing of non-visible artists by bringing 
> the following line to the top of the LineArtist's draw method:
>
>     if self.get_visible() is False:
>         return
>
> This *does* fix the problem (and will fix the problem for all other 
> artists if applied in the same way), but it relies on a developer 
> remembering the rule of thumb that they must always start their draw 
> method with these two (simple) lines. Additionally, testing this 
> functionality is actually quite hard without resorting to timing the 
> execution.
>
> It made we wonder if there was a better approach to fixing this. 
> Having a decorator to do this for you is a good idea, except that a 
> developer would need to remember to decorate their subclass' draw 
> method, so the next level up is to use a metaclass to *always* wrap 
> the draw method with the "if visible" lines.
>
> An example of implementing this (apologies if the code doesn't come 
> out well in the email):
>
>
> class ArtistMeta(type):
>     def __new__(cls, classname, bases, class_dict):
>         # replace the draw method with one which short-circuits if 
> self.visible is False
>         draw_method = class_dict['draw']
>         def draw(self, *args, **kwargs):
>             if self.visible is False:
>                 print 'draw **not** called with 
> visible={}'.format(self.visible)
>                 return
>             else:
>                 return draw_method(self, *args, **kwargs)
>         class_dict['draw'] = draw
>
>         return  type.__new__(cls, classname, bases, class_dict)
>
>
> class Artist(object):
>     __metaclass__ = ArtistMeta
>
>     def __init__(self, visible=True):
>         self.visible = visible
>
>     def draw(self, renderer=None):
>         print 'draw called with visible={}'.format(self.visible)
>         return 'foobar'
>
>
> class SubArtist(Artist):
>     def draw(self, renderer=None):
>         print "subclass' draw method"
>         return Artist.draw(self, renderer=renderer)
>
>
>
>
> With the following results:
>
>
> >>> a = Artist().draw('wibble')
> draw called with visible=True
>
> >>> b = Artist(False).draw('wibble')
> draw **not** called with visible=False
>
> >>> c = SubArtist(True).draw('wibble')
> subclass' draw method
> draw called with visible=True
>
> >>> d = SubArtist(False).draw('wibble')
> draw **not** called with visible=False
>
>
>
> In my eyes this makes testing the functionality possible without 
> timing (and is therefore an improvement), but I wanted to know how 
> others felt about the approach, and in particular, using more 
> metaclasses in matplotlib (a simple tutorial which I found useful: 
> http://www.voidspace.org.uk/python/articles/metaclasses.shtml).
>
>
> Cheers,
>
> Phil
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] [PATCH] gtkagg backend leaks gc's.

From: Damon M. <dam...@gm...> - 2012-11-26 16:33:51

On Sun, Nov 11, 2012 at 4:23 PM, Benjamin Root <ben...@ou...> wrote:
>
>
> On Thursday, November 8, 2012, Carl Michal wrote:
>>
>> Hello,
>>
>> I noticed that a program I had that uses canvas.blit() to do animated
>> graphs
>> with the gtkagg backend was leaking memory.
>>
>> I tracked this down to gtk gc's being allocated in agg_to_gtk_drawable
>> with
>> gdk_gc_new(), but never being destroyed.
>>
>> The leak can be seen using the 'Animating selected plot elements' example
>> from:
>>
>> http://www.scipy.org/Cookbook/Matplotlib/Animations
>>
>> (if it is modified to run forever, rather than just 50 plots and also
>> changing numerix to numpy). After a few minutes, it is clear from ps that
>> the
>> memory usage is slowly but steadily climbing.
>>
>> Patch below (against matplotlib-1.1.1.) fixes it.
>>
>> Carl
>>
>> --- _gtkagg.cpp~        2012-06-30 12:37:00.000000000 -0700
>> +++ _gtkagg.cpp 2012-11-08 14:30:23.000000000 -0800
>> @@ -121,6 +121,7 @@
>>                                   destbuffer,
>>                                   deststride);
>>
>> +       gdk_gc_destroy(gc);
>>             if (needfree)
>>             {
>>                 delete [] destbuffer;
>>
>>
>>
>
> If you are willing, would you like to file a PR against the v1.2.x branch?
>
> Ben Root

Decided to follow-up on this and it looks like this patch has already
been applied.

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

[matplotlib-devel] Use of meta on Artist

From: Phil E. <pel...@gm...> - 2012-11-26 11:17:54

I've just been reviewing a really useful PR (
https://github.com/matplotlib/matplotlib/pull/1531) from Pierre Haessig
which speeds up the drawing of non-visible artists by bringing the
following line to the top of the LineArtist's draw method:

    if self.get_visible() is False:
        return

This *does* fix the problem (and will fix the problem for all other artists
if applied in the same way), but it relies on a developer remembering the
rule of thumb that they must always start their draw method with these two
(simple) lines. Additionally, testing this functionality is actually quite
hard without resorting to timing the execution.

It made we wonder if there was a better approach to fixing this. Having a
decorator to do this for you is a good idea, except that a developer would
need to remember to decorate their subclass' draw method, so the next level
up is to use a metaclass to *always* wrap the draw method with the "if
visible" lines.

An example of implementing this (apologies if the code doesn't come out
well in the email):


class ArtistMeta(type):
    def __new__(cls, classname, bases, class_dict):
        # replace the draw method with one which short-circuits if
self.visible is False
        draw_method = class_dict['draw']
        def draw(self, *args, **kwargs):
            if self.visible is False:
                print 'draw **not** called with
visible={}'.format(self.visible)
                return
            else:
                return draw_method(self, *args, **kwargs)
        class_dict['draw'] = draw

        return  type.__new__(cls, classname, bases, class_dict)


class Artist(object):
    __metaclass__ = ArtistMeta

    def __init__(self, visible=True):
        self.visible = visible

    def draw(self, renderer=None):
        print 'draw called with visible={}'.format(self.visible)
        return 'foobar'


class SubArtist(Artist):
    def draw(self, renderer=None):
        print "subclass' draw method"
        return Artist.draw(self, renderer=renderer)




With the following results:


>>> a = Artist().draw('wibble')
draw called with visible=True

>>> b = Artist(False).draw('wibble')
draw **not** called with visible=False

>>> c = SubArtist(True).draw('wibble')
subclass' draw method
draw called with visible=True

>>> d = SubArtist(False).draw('wibble')
draw **not** called with visible=False



In my eyes this makes testing the functionality possible without timing
(and is therefore an improvement), but I wanted to know how others felt
about the approach, and in particular, using more metaclasses in matplotlib
(a simple tutorial which I found useful:
http://www.voidspace.org.uk/python/articles/metaclasses.shtml).


Cheers,

Phil

[matplotlib-devel] Issues with building Matplotlib 1.2.0 on RHEL5

From: Tejashri K. <tej...@gm...> - 2012-11-26 05:47:39

basedirlist is: ['/user/tkandolkar/Desktop/installers/BuildFolder/']
============================================================================
BUILDING MATPLOTLIB
            matplotlib: 1.2.0
                python: 3.2.3 (default, Oct 11 2012, 11:32:11)  [GCC 4.1.2
                        20071124 (Red Hat 4.1.2-42)]
              platform: linux2

REQUIRED DEPENDENCIES
                 numpy: 1.5.1
             freetype2: 9.10.3

OPTIONAL BACKEND DEPENDENCIES
                libpng: 1.2.10
               Tkinter: no
                        * TKAgg requires Tkinter
                  Gtk+: no
                        * Building for Gtk+ requires pygtk; you must be able
                        * to "import gtk" in your build/install environment
       Mac OS X native: no
                    Qt: no
                   Qt4: no
                PySide: Qt: 4.7.1, PySide: 1.1.2
                 Cairo: no

OPTIONAL DATE/TIMEZONE DEPENDENCIES
              dateutil: matplotlib will provide
                  pytz: matplotlib will provide
                   six: matplotlib will provide

OPTIONAL USETEX DEPENDENCIES
                dvipng: no
           ghostscript: 8.15.2
                 latex: no
               pdftops: 3.00

[Edit setup.cfg to suppress the above messages]
============================================================================
pymods ['pylab', 'six']
packages ['matplotlib', 'matplotlib.backends', 'matplotlib.backends.qt4_editor', 'matplotlib.projections', 'matplotlib.testing', 'matplotlib.testing.jpl_units', 'matplotlib.tests', 'mpl_toolkits', 'mpl_toolkits.mplot3d', 'mpl_toolkits.axes_grid', 'mpl_toolkits.axes_grid1', 'mpl_toolkits.axisartist', 'matplotlib.sphinxext', 'matplotlib.tri', 'matplotlib.delaunay', 'pytz', 'dateutil', 'dateutil.zoneinfo']
running build
running build_py
copying lib/matplotlib/mpl-data/matplotlibrc -> build/lib.linux-x86_64-3.2/matplotlib/mpl-data

running build_ext
building 'matplotlib.ft2font' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/ft2font.cpp -o build/temp.linux-x86_64-3.2/src/ft2font.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/mplutils.cpp -o build/temp.linux-x86_64-3.2/src/mplutils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/src/ft2font.o build/temp.linux-x86_64-3.2/src/mplutils.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o -L/user/aghuwalewala/python-3_2_3/release/lib -lfreetype -lz -lstdc++ -lm -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/ft2font.cpython-32m.so
building 'matplotlib.ttconv' extension
creating build/temp.linux-x86_64-3.2/ttconv
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/_ttconv.cpp -o build/temp.linux-x86_64-3.2/src/_ttconv.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c ttconv/pprdrv_tt.cpp -o build/temp.linux-x86_64-3.2/ttconv/pprdrv_tt.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c ttconv/pprdrv_tt2.cpp -o build/temp.linux-x86_64-3.2/ttconv/pprdrv_tt2.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c ttconv/ttutil.cpp -o build/temp.linux-x86_64-3.2/ttconv/ttutil.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/src/_ttconv.o build/temp.linux-x86_64-3.2/ttconv/pprdrv_tt.o build/temp.linux-x86_64-3.2/ttconv/pprdrv_tt2.o build/temp.linux-x86_64-3.2/ttconv/ttutil.o -L/user/aghuwalewala/python-3_2_3/release/lib -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/ttconv.cpython-32m.so
building 'matplotlib._cntr' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/cntr.c -o build/temp.linux-x86_64-3.2/src/cntr.o
gcc -pthread -shared -L. build/temp.linux-x86_64-3.2/src/cntr.o -L/user/aghuwalewala/python-3_2_3/release/lib -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_cntr.cpython-32m.so
building 'matplotlib._delaunay' extension
creating build/temp.linux-x86_64-3.2/lib
creating build/temp.linux-x86_64-3.2/lib/matplotlib
creating build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c lib/matplotlib/delaunay/_delaunay.cpp -o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/_delaunay.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c lib/matplotlib/delaunay/VoronoiDiagramGenerator.cpp -o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/VoronoiDiagramGenerator.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c lib/matplotlib/delaunay/delaunay_utils.cpp -o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/delaunay_utils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c lib/matplotlib/delaunay/natneighbors.cpp -o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/natneighbors.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/_delaunay.o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/VoronoiDiagramGenerator.o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/delaunay_utils.o build/temp.linux-x86_64-3.2/lib/matplotlib/delaunay/natneighbors.o -L/user/aghuwalewala/python-3_2_3/release/lib -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_delaunay.cpython-32m.so
building 'matplotlib._path' extension
creating build/temp.linux-x86_64-3.2/agg24
creating build/temp.linux-x86_64-3.2/agg24/src
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_vcgen_contour.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_contour.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_curves.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_curves.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_bezier_arc.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_trans_affine.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_vcgen_stroke.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_stroke.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/agg_py_transforms.cpp -o build/temp.linux-x86_64-3.2/src/agg_py_transforms.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/path_cleanup.cpp -o build/temp.linux-x86_64-3.2/src/path_cleanup.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/path.cpp -o build/temp.linux-x86_64-3.2/src/path.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_contour.o build/temp.linux-x86_64-3.2/agg24/src/agg_curves.o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_stroke.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o build/temp.linux-x86_64-3.2/src/agg_py_transforms.o build/temp.linux-x86_64-3.2/src/path_cleanup.o build/temp.linux-x86_64-3.2/src/path.o -L/user/aghuwalewala/python-3_2_3/release/lib -lstdc++ -lm -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_path.cpython-32m.so
building 'matplotlib._tri' extension
creating build/temp.linux-x86_64-3.2/lib/matplotlib/tri
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c lib/matplotlib/tri/_tri.cpp -o build/temp.linux-x86_64-3.2/lib/matplotlib/tri/_tri.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/mplutils.cpp -o build/temp.linux-x86_64-3.2/src/mplutils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/lib/matplotlib/tri/_tri.o build/temp.linux-x86_64-3.2/src/mplutils.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o -L/user/aghuwalewala/python-3_2_3/release/lib -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_tri.cpython-32m.so
building 'matplotlib.backends._backend_agg' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_trans_affine.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_bezier_arc.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_curves.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_curves.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_vcgen_dash.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_dash.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_vcgen_stroke.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_stroke.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_image_filters.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_image_filters.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/mplutils.cpp -o build/temp.linux-x86_64-3.2/src/mplutils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/agg_py_transforms.cpp -o build/temp.linux-x86_64-3.2/src/agg_py_transforms.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/usr/include/freetype2 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/backend_agg.cpp -o build/temp.linux-x86_64-3.2/src/backend_agg.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o build/temp.linux-x86_64-3.2/agg24/src/agg_curves.o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_dash.o build/temp.linux-x86_64-3.2/agg24/src/agg_vcgen_stroke.o build/temp.linux-x86_64-3.2/agg24/src/agg_image_filters.o build/temp.linux-x86_64-3.2/src/mplutils.o build/temp.linux-x86_64-3.2/src/agg_py_transforms.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o build/temp.linux-x86_64-3.2/src/backend_agg.o -L/user/aghuwalewala/python-3_2_3/release/lib -lstdc++ -lm -lfreetype -lz -lstdc++ -lm -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/backends/_backend_agg.cpython-32m.so
building 'matplotlib._image' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/image.cpp -o build/temp.linux-x86_64-3.2/src/image.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/mplutils.cpp -o build/temp.linux-x86_64-3.2/src/mplutils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_trans_affine.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_image_filters.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_image_filters.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c agg24/src/agg_bezier_arc.cpp -o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -Isrc -Iagg24/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/src/image.o build/temp.linux-x86_64-3.2/src/mplutils.o build/temp.linux-x86_64-3.2/agg24/src/agg_trans_affine.o build/temp.linux-x86_64-3.2/agg24/src/agg_image_filters.o build/temp.linux-x86_64-3.2/agg24/src/agg_bezier_arc.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o -L/user/aghuwalewala/python-3_2_3/release/lib -lstdc++ -lm -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_image.cpython-32m.so
building 'matplotlib._png' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/_png.cpp -o build/temp.linux-x86_64-3.2/src/_png.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c src/mplutils.cpp -o build/temp.linux-x86_64-3.2/src/mplutils.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxsupport.cxx -o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxx_extensions.cxx -o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 -DPYCXX_PYTHON_2TO3=1 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I/usr/include/libpng12 -I/user/tkandolkar/Desktop/installers/BuildFolder/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/lib/python3.2/site-packages/numpy/core/include -I. -I/disk/ve/dev/tkandolkar/install/p4streams/dotrox_integration/linux-amd64-gcc_4_1-release/include/python3.2m -c CXX/cxxextensions.c -o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o
g++ -pthread -shared -L. build/temp.linux-x86_64-3.2/src/_png.o build/temp.linux-x86_64-3.2/src/mplutils.o build/temp.linux-x86_64-3.2/CXX/cxxsupport.o build/temp.linux-x86_64-3.2/CXX/cxx_extensions.o build/temp.linux-x86_64-3.2/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-3.2/CXX/cxxextensions.o -L/user/aghuwalewala/python-3_2_3/release/lib -lpng12 -lz -lstdc++ -lm -lpython3.2m -o build/lib.linux-x86_64-3.2/matplotlib/_png.cpython-32m.so

Re: [matplotlib-devel] Matplotlib 'testing' page link broken

From: Damon M. <dam...@gm...> - 2012-11-22 14:10:34

On Thu, Nov 22, 2012 at 6:23 AM, Phil Elson <pel...@gm...> wrote:
> Mike working his magic:
> https://github.com/matplotlib/matplotlib.github.com/commits/master

+1 for Mike magic.

Happy Turkey Day to all my American friends!

>
>
> On 22 November 2012 03:21, Paul Ivanov <piv...@gm...> wrote:
>>
>>
>> On Tue, Nov 20, 2012 at 2:21 PM, Damon McDougall
>> <dam...@gm...> wrote:
>>>
>>> http://matplotlib.org/devel/coding_guide.html
>>>
>>> Scroll down to 'Testing'. Click 'Testing'. Boom.
>>
>>
>> seems to have been fixed now. The "Testing" link over at
>> http://matplotlib.org/devel/coding_guide.html#testing takes me to
>> http://matplotlib.org/devel/testing.html#testing
>>
>> --
>> Paul Ivanov
>> 314 address only used for lists,  off-list direct email at:
>> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Re: [matplotlib-devel] Matplotlib 'testing' page link broken

From: Phil E. <pel...@gm...> - 2012-11-22 11:23:23

Mike working his magic:
https://github.com/matplotlib/matplotlib.github.com/commits/master


On 22 November 2012 03:21, Paul Ivanov <piv...@gm...> wrote:

>
> On Tue, Nov 20, 2012 at 2:21 PM, Damon McDougall <
> dam...@gm...> wrote:
>
>> http://matplotlib.org/devel/coding_guide.html
>>
>> Scroll down to 'Testing'. Click 'Testing'. Boom.
>>
>
> seems to have been fixed now. The "Testing" link over at
> http://matplotlib.org/devel/coding_guide.html#testing takes me to
> http://matplotlib.org/devel/testing.html#testing
>
> --
> Paul Ivanov
> 314 address only used for lists,  off-list direct email at:
> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Re: [matplotlib-devel] Matplotlib 'testing' page link broken

From: Paul I. <piv...@gm...> - 2012-11-22 03:21:40

On Tue, Nov 20, 2012 at 2:21 PM, Damon McDougall
<dam...@gm...>wrote:

> http://matplotlib.org/devel/coding_guide.html
>
> Scroll down to 'Testing'. Click 'Testing'. Boom.
>

seems to have been fixed now. The "Testing" link over at
http://matplotlib.org/devel/coding_guide.html#testing takes me to
http://matplotlib.org/devel/testing.html#testing

-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

[matplotlib-devel] Getting setup.py to find TKInter headers during build

From: Fred P. <fre...@gm...> - 2012-11-21 12:22:39

Thanks to the response to my previous message, I have managed to get
matplotlib to compile, but unfortunately without the TKAgg backend,
because when I attempt to build, I get the following message:

Tkinter:  no
             *  Tkinter present, but header files are not found.
             *  You may need to install development packages

Looking at setupext.py, this looks like it can't find tk.h in any of
the include directories.  But in my win32_static\include folder, I
have got a tk.h.  I've tried various locations for the tk headers, but
it still seems to struggle.  I even tried setting the basedir setting
in setupext.py to point directly at my tcl;tk library leftover from my
Python compile.

Anyone got any thoughts - this is the last thing I need before I can
actually use matplotlib in my application!

Kind regards
Fred

Re: [matplotlib-devel] scalebars

From: Matěj T. <mat...@gm...> - 2012-11-21 12:12:25

Thank you for your fast reply,
you are right, AnchoredSizeBar has indeed almost all features I would
like. Or it definitely has the most important ones.
I have stumbled upon the page you refer, but I must have overlooked it.
An actual documentation of the function wouldn't hurt

Anyway, these features seem to be missing:
  - Bar styles (bar width, bar endings wouldn't hurt either).
  - Colors (bar, text, background).

I would like to look into it, but it is usually more efficient if more
experienced persons provide some pointers. So if you think that I should
know something before attempting to add the functionality, please let me
know.
For instance, do you think that the enhancements I have proposed make
sense and should be integrated into AnchoredSizeBar?

Matej

On 11/18/2012 06:32 PM, Joe Kington wrote:
> Have you had a look at "AnchoredSizeBar" from 
> mpl_toolkits.axes_grid1.anchored_artists?
>
> http://matplotlib.org/1.1.1/mpl_toolkits/axes_grid/users/overview.html#anchoredartists
>
> It provides essentially all of the features you mention.  I'd agree it 
> could use a few enhancements, but it's a good start on this.
>
> As a quick example of using it as you describe:
>
> import matplotlib.pyplot as plt
> import numpy as np
> from mpl_toolkits.axes_grid1.anchored_artists import AnchoredSizeBar
>
> fig, ax = plt.subplots()
> ax.imshow(np.random.random((10,10)))
>
> bar = AnchoredSizeBar(ax.transData, 2, '2 Units',
> pad=0.5, loc=8, sep=5, borderpad=0.5, frameon=True)
> bar.patch.set(alpha=0.5, boxstyle='round')
> ax.add_artist(bar)
>
> plt.show()
>
>
> Note that this is very similar to your example.  The main things it's 
> missing are ends on the scalebar.
>
> I'd certainly agree that it could use some enhancements (e.g. 
> different styles of scalebars and better documentation), but perhaps 
> it's best to start with AnchoredSizeBar instead of recreating it from 
> scratch?
>
> Just my thoughts, anyway.
> -Joe
>
>
> On Sun, Nov 18, 2012 at 8:16 AM, Matěj Týč <mat...@gm... 
> <mailto:mat...@gm...>> wrote:
>
>     Dear developers,
>     I use Matplotlib to process and display images acquired by
>     microscopes.
>     It is quite common to indicate dimensions by displaying scale bar
>     in the
>     image rather than using axes with labels. Although axes enable you to
>     refer to specific location in the image, they take up space around the
>     image, so if you only need to show the scale, scale bar is better.
>
>     What is needed:
>      - The scale bar of given dimension (data units), possibly with
>     bars at
>     its ends.
>      - Text (presumably centered under the bar), text size as well as
>     vertical offset in physical units (= units reflecting the actual image
>     size, like the font size)
>      - Semi-transparent rectangle, so the scale and label are more
>     readable
>      - Dark/bright theme might be a good idea.
>     I have made an svg file in Inkscape, so you can see what I mean.
>
>     First of all, I tried to implement the stuff myself, but later I have
>     found out that there is something on github. I have forked it,
>     made some
>     minor modifications, and I think that it is "almost done".
>     https://gist.github.com/4100881 (the add_scalebar function there is
>     broken ATM)
>     I also attach the test code for your convenience. You need to run it
>     with scalebars.py in the same directory.
>     You are supposed to see a tiny bright scalebar at the bottom right
>     corner.
>
>     There are some outstanding issues, though:
>
>      - I have a feeling that bars at the end of the scale bar should be
>     related to the font size, as well as the actual width of the scale
>     bar.
>     How to achieve this?
>      - How to make the semi-transparent background for the bar and
>     label in
>     a smart way?
>
>     Could you help me with those? I would like this to appear in
>     matplotlib
>     since it is IMO a useful feature, what needs to be done?
>     Regards,
>     Matěj Týč
>
>     ------------------------------------------------------------------------------
>     Monitor your physical, virtual and cloud infrastructure from a single
>     web console. Get in-depth insight into apps, servers, databases,
>     vmware,
>     SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>     Pricing starts from $795 for 25 servers or applications!
>     http://p.sf.net/sfu/zoho_dev2dev_nov
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

[matplotlib-devel] Matplotlib 'testing' page link broken

From: Damon M. <dam...@gm...> - 2012-11-20 22:22:05

http://matplotlib.org/devel/coding_guide.html

Scroll down to 'Testing'. Click 'Testing'. Boom.

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Re: [matplotlib-devel] Matplotlib Binary Dependencies compiled against VS2010

From: Christoph G. <cg...@uc...> - 2012-11-20 18:24:54

On 11/20/2012 5:55 AM, Fred Pollard wrote:
> I'm in the process of completing an application with an embedded
> Python 2.7.3 interpreter - but it all has to be compiled against
> VS2010.
>
> Have managed Python and it's dependencies, as well as numpy 1.6.2, but
> struggling with matplotlib because I can't get the dependencies to
> compile properly - mainly libpng, which seems to demand .lib and .dll
> files that a compilation of zlib from source does not produce (e.g.
> zdll.lib, zlib.lib, etc.).  I know Christophe Gohlke has kindly
> produced a set of dependencies up to VS2008.  Does anyone know of an
> existing similar set compiled for VS 2010?
>
> Many thanks,
> Fred
>

Hi Fred,

I updated "matplotlib-1.x-windows-link-libraries.zip" with dependencies 
compiled for VS 2010. Let me know if anything is missing.

Christoph

[matplotlib-devel] Matplotlib Binary Dependencies compiled against VS2010

From: Fred P. <fre...@gm...> - 2012-11-20 13:56:00

I'm in the process of completing an application with an embedded
Python 2.7.3 interpreter - but it all has to be compiled against
VS2010.

Have managed Python and it's dependencies, as well as numpy 1.6.2, but
struggling with matplotlib because I can't get the dependencies to
compile properly - mainly libpng, which seems to demand .lib and .dll
files that a compilation of zlib from source does not produce (e.g.
zdll.lib, zlib.lib, etc.).  I know Christophe Gohlke has kindly
produced a set of dependencies up to VS2008.  Does anyone know of an
existing similar set compiled for VS 2010?

Many thanks,
Fred

[matplotlib-devel] aspect ratio bug?

From: <sa...@ns...> - 2012-11-20 00:47:58

I just sent this to the matplotlib-users list, but noticed it's been abandoned, or at least unused since August.  I'm reposting here and adding the info I forgot on the other list.  Sorry if you get this twice.


This is running matplotlib 1.1.1 installed with pip on
Linux savoie 2.6.32.59-0.7-default #1 SMP 2012-07-13 15:50:56 +0200 x86_64 x86_64 x86_64 GNU/Linux

(But I also tested with MPL:1.2)




Hi there, 

I've boiled down a problem and while the following my look useless, I need to understand why matplotlib is behaving like it is.

Below is code showing my issue.  I don't believe the issue is with the "bbox_inches='tight'", if you leave that off, my image is indeed, 800x1400, but the last row is a row of transparent pixels(on linux/not mac).  It's difficult to see unless you use the imagemagik command display.

The basic problem is that when my data has an aspect ratio very close to 1.75, the image gets changed to one with an aspect of 1.74875.

Correct figure info 8x14@100dpi = 800x1400 => 1.75 Aspect Ratio.
Incorrect figure info => 800x1399 => 1.74875

Data that works aspect ratio: 1.7499999999999998
Data that fails aspect ratio: 1.7499999999999996
--->   Srsly?!  -------------------------------^

It would be great if someone could explain to me what's happening if this is indeed working as expected.  If it's not, it would be great if someone could fix it.

Thanks in advance.
Matt


import matplotlib.pyplot as plt

def create_image():
    # I want an 800x1400 image (aspect = 1400/800 = 1.75.
    fig = plt.figure(1, figsize=(8, 14), frameon=False, dpi=100)

    # Use the whole figure and fill with a patch.
    fig.add_axes([0, 0, 1, 1])
    ax = plt.gca()
    limb = ax.axesPatch
    limb.set_facecolor('#6587ad')

    # Set some bounds with Aspects very close to the desired aspect ratios.
    x1 = 0.0
    y1 = 0.0
    x2 = 16.

    # If you un-comment out this line (and comment the one below). I get an image I expect
    # y2 = 27.999999999999994671   # produces 800 x 1400 image
    # aspect = 1.7499999999999998 works

    # Use this line and I get and image the wrong size (or with transparent pixels.)
    y2 = 27.999999999999994670   # produces (wrong?) 800 x 1399 image
    # aspect = 1.7499999999999996 Fails? wat?

    corners = ((x1, y1), (x2, y2))
    ax.update_datalim(corners)
    ax.set_xlim((x1, x2))
    ax.set_ylim((y1, y2))

    ax.set_aspect('equal', anchor='C')
    ax.set_xticks([])
    ax.set_yticks([])

    plt.savefig('rectangle.png', pad_inches=0.0, bbox_inches='tight')

    # If you use this below, the file size is correct, but there is a single
    # line transparent pixels along the bottom of the image

    #  plt.savefig('rectangle.png', pad_inches=0.0)


if __name__ == '__main__':
    create_image()

[matplotlib-devel] scalebars

From: Matěj T. <mat...@gm...> - 2012-11-18 14:16:45

Attachments: sbars-test.py scalebars.svg

Dear developers,
I use Matplotlib to process and display images acquired by microscopes.
It is quite common to indicate dimensions by displaying scale bar in the
image rather than using axes with labels. Although axes enable you to
refer to specific location in the image, they take up space around the
image, so if you only need to show the scale, scale bar is better.

What is needed:
 - The scale bar of given dimension (data units), possibly with bars at
its ends.
 - Text (presumably centered under the bar), text size as well as
vertical offset in physical units (= units reflecting the actual image
size, like the font size)
 - Semi-transparent rectangle, so the scale and label are more readable
 - Dark/bright theme might be a good idea.
I have made an svg file in Inkscape, so you can see what I mean.

First of all, I tried to implement the stuff myself, but later I have
found out that there is something on github. I have forked it, made some
minor modifications, and I think that it is "almost done". 
https://gist.github.com/4100881 (the add_scalebar function there is
broken ATM)
I also attach the test code for your convenience. You need to run it
with scalebars.py in the same directory.
You are supposed to see a tiny bright scalebar at the bottom right
corner.

There are some outstanding issues, though:

 - I have a feeling that bars at the end of the scale bar should be
related to the font size, as well as the actual width of the scale bar.
How to achieve this?
 - How to make the semi-transparent background for the bar and label in
a smart way?

Could you help me with those? I would like this to appear in matplotlib
since it is IMO a useful feature, what needs to be done?
Regards,
Matěj Týč

Re: [matplotlib-devel] OpenGL backend with Galry

From: Fernando P. <fpe...@gm...> - 2012-11-18 04:09:21

On Sat, Nov 17, 2012 at 4:07 PM, Cyrille Rossant
<cyr...@gm...> wrote:
> OK so I now have a very experimental proof of concept of how integrating
> Galry in the IPython notebook. There's a short demo here:
> http://www.youtube.com/watch?v=taN4TobRS-E
>
> I'll put the code on github but there's of course much more to do.
>
> I'll also work on a basic matplotlib-like high-level interface that will
> work in both standard python/ipython consoles, and in the IPython notebook.

Awesome!  This is really great to see, before long we'll sort out
these APIs so all this can be made available easily to end users.

Great job!

Cheers,

f

127 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 .. 77 78 79 80 81 .. 554 > >> (Page 79 of 554)