From morph at debian.org  Wed Jun  1 01:48:25 2016
From: morph at debian.org (Sandro Tosi)
Date: Wed, 1 Jun 2016 06:48:25 +0100
Subject: [Matplotlib-devel] REL: v1.5.2rc2
In-Reply-To: <CAB4XWXw2CFEFu=ywkfij7zCQf-pBj-BjDOwG6kmPDA+3OTdQ+A@mail.gmail.com>
References: <CAA48SF9ETavB3Q3ms3d5C2OdiOKtAZWHR17i+zaoOEw86VJ0SA@mail.gmail.com>
 <CAB4XWXx9YCAT3-Uy1XzGtNJ0j_2mJFeiVzogOYLx7ndAPgy4HQ@mail.gmail.com>
 <CAA48SF9To5x+=PRzS3BiDgihddb_M6evgYRfeF37t2eUocdtwQ@mail.gmail.com>
 <CAB4XWXw2CFEFu=ywkfij7zCQf-pBj-BjDOwG6kmPDA+3OTdQ+A@mail.gmail.com>
Message-ID: <CAB4XWXzEoCtqqAsOQ6Z1aUThq5WkdAUvxC_=59iU7XxzPgVW5w@mail.gmail.com>

it built just fine on all the archs except on mips (but it is usually
a slow build architecture and might take other several days there) so
if you were holding on this for releasing 1.5.2 final and nothing else
came up in the meantime, then i think we're good to go

On Tue, May 31, 2016 at 6:17 AM, Sandro Tosi <morph at debian.org> wrote:
> on almost all architectures, it has already built or building right
> now (you can see its progress at
> https://buildd.debian.org/status/package.php?p=matplotlib) so I expect
> within today we'll have most (if not all) of the archs will be done
>
> On Mon, May 30, 2016 at 9:44 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
>> How long does that tend to take to run?  We should probably hold off on a
>> 1.5.2 final until we hear back.
>>
>> Tom
>>
>> On Mon, May 30, 2016 at 4:34 PM Sandro Tosi <morph at debian.org> wrote:
>>>
>>> Hey Thomas & mpl developer,
>>> I just pushed 1.5.2rc2 to debian, let's see if some of the weirdest
>>> archs complain - I will report here if they do
>>>
>>> On Fri, May 27, 2016 at 3:44 AM, Thomas Caswell <tcaswell at gmail.com>
>>> wrote:
>>> > Hey folks,
>>> >
>>> > I just tagged rc2.
>>> >
>>> > This includes a some-what aggressive backport of the reworking of how we
>>> > link into Tk to decouple from the exact version of tk we are compiled
>>> > against (https://github.com/matplotlib/matplotlib/pull/6442)
>>> >
>>> > As such, please try to build this on your your systems and verify that
>>> > mpl
>>> > builds and works correctly with the tkagg backend.
>>> >
>>> > A major motivation for including this in the 1.5.2 release is that we
>>> > can
>>> > now release wheels for all of the major platforms.  Much of the credit
>>> > for
>>> > this should go to the tireless Matthew Brett.
>>> >
>>> > The new rc (and the old one) should be available (assuming the CI
>>> > passes)
>>> > for conda via
>>> >
>>> >    conda install -c conda-forge/channel/rc matplotlib
>>> >
>>> > Tom
>>> >
>>> > _______________________________________________
>>> > Matplotlib-devel mailing list
>>> > Matplotlib-devel at python.org
>>> > https://mail.python.org/mailman/listinfo/matplotlib-devel
>>> >
>>>
>>>
>>>
>>> --
>>> Sandro "morph" Tosi
>>> My website: http://sandrotosi.me/
>>> Me at Debian: http://wiki.debian.org/SandroTosi
>>> G+: https://plus.google.com/u/0/+SandroTosi
>
>
>
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> G+: https://plus.google.com/u/0/+SandroTosi



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

From matthew.brett at gmail.com  Wed Jun  1 13:39:10 2016
From: matthew.brett at gmail.com (Matthew Brett)
Date: Wed, 1 Jun 2016 10:39:10 -0700
Subject: [Matplotlib-devel] Should we add manylinux wheels for previous
 versions of matplotlib?
In-Reply-To: <CAH6Pt5q6S1kUknS1SA0a=xnTug8CKBds=NY1gf-UGLnuKMvJWg@mail.gmail.com>
References: <CAH6Pt5ruu5UFSG5yjyh=Vc=oBs6quGjZ8ifbjhiqSx4+EY=8Tw@mail.gmail.com>
 <CAPJVwBmCF-4ajoBfkq+tYBP-6RTiSM2gZVqDm68nH2Cj-FdXyw@mail.gmail.com>
 <CAH6Pt5q6S1kUknS1SA0a=xnTug8CKBds=NY1gf-UGLnuKMvJWg@mail.gmail.com>
Message-ID: <CAH6Pt5pC16j5LwxkDZ_3B1Qos3VFRiHsjD3dWnziKL1J8MXO1Q@mail.gmail.com>

On Mon, May 30, 2016 at 5:08 PM, Matthew Brett <matthew.brett at gmail.com> wrote:
> On Mon, May 30, 2016 at 4:47 PM, Nathaniel Smith <njs at pobox.com> wrote:
>> Just to check, I assume that these wheels would need a backport of:
>>   https://github.com/matplotlib/matplotlib/pull/6442
>> ?
>
> Yes, that's already done over at :
> https://github.com/matthew-brett/manylinux-builds/blob/master/build_matplotlibs.sh

To see what you'd get if we did upload the wheels, try:

python -m pip install --upgrade pip  # Upgrade to latest pip
pip install -f https://nipy.bic.berkeley.edu/manylinux matplotlib==1.4.0

etc.

Cheers,

Matthew

From ndbecker2 at gmail.com  Thu Jun  2 11:12:04 2016
From: ndbecker2 at gmail.com (Neal Becker)
Date: Thu, 02 Jun 2016 11:12:04 -0400
Subject: [Matplotlib-devel] mpl2.0b title of subplot overprinting
Message-ID: <nipic5$ptd$1@ger.gmane.org>

This was produced with all default settings

,----[ /home/nbecker/anaconda3/envs/py35/interference/test_mpl.py ]
| #!/usr/bin/python3
| import numpy as np
| import matplotlib.pyplot as plt
| #import seaborn
| fig, axs = plt.subplots (2, 1)
| 
| x = np.arange (-1, 1, 0.1)
| axs[0].plot (x, x**2)
| axs[0].set_title ('y1')
| 
| axs[1].plot (x, -x**2)
| axs[1].set_title ('spectrum of product')
| 
| plt.suptitle (r'${E_s/N_0}_1=%g, {E_s/N_0}_2=%g$'%(100,100))
| # axs[0].grid()
| # axs[1].grid()
| #plt.tight_layout()
| plt.show()
`----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: figure_1.pdf
Type: application/pdf
Size: 12620 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160602/41895c7e/attachment.pdf>

From ndbecker2 at gmail.com  Thu Jun  2 11:13:44 2016
From: ndbecker2 at gmail.com (Neal Becker)
Date: Thu, 02 Jun 2016 11:13:44 -0400
Subject: [Matplotlib-devel] mpl2.0b title of subplot overprinting
References: <nipic5$ptd$1@ger.gmane.org>
Message-ID: <nipif8$ptd$2@ger.gmane.org>

Neal Becker wrote:

> This was produced with all default settings
> 
> ,----[ /home/nbecker/anaconda3/envs/py35/interference/test_mpl.py ]
> | #!/usr/bin/python3
> | import numpy as np
> | import matplotlib.pyplot as plt
> | #import seaborn
> | fig, axs = plt.subplots (2, 1)
> | 
> | x = np.arange (-1, 1, 0.1)
> | axs[0].plot (x, x**2)
> | axs[0].set_title ('y1')
> | 
> | axs[1].plot (x, -x**2)
> | axs[1].set_title ('spectrum of product')
> | 
> | plt.suptitle (r'${E_s/N_0}_1=%g, {E_s/N_0}_2=%g$'%(100,100))
> | # axs[0].grid()
> | # axs[1].grid()
> | #plt.tight_layout()
> | plt.show()
> `----

Adding plt.tight_layout() makes the axs[0] title overprint the suptitle


From daniel.mcneela at gmail.com  Sun Jun  5 17:15:48 2016
From: daniel.mcneela at gmail.com (Daniel McNeela)
Date: Sun, 5 Jun 2016 14:15:48 -0700
Subject: [Matplotlib-devel] (no subject)
Message-ID: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>

Hi All,

I'm currently developing a Python package built on top of Matplotlib, and
I'd like to add custom functionality to the Axes class while still
retaining all of the default Matplotlib syntax and commands. To do this,
I'd like to subclass matplotlib.axes.Axes (or possibly
matplotlib.axes._base._AxesBase) and add additional class attributes and
methods. Ideally, I'd like to do this without forking Matplotlib and
directly editing the source so as to maintain compatibility with future
Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
optional FigureClass argument which I could use to pass a custom subclass
of Figure. I was thinking I could subclass Figure such that the subclass
overrides methods such as Figure.add_subplot() by calling the superclass's
method and passing my custom Axes subclass in as an optional argument. But
I'm not sure which methods I'd have to override, or how deep the rabbit
hole goes, as Axes objects seem to be generated in a number of places
throughout the Matplotlib source.

If anyone who is familiar with the code base might be able to suggest a
simple way in which I could accomplish this desired behavior, I would
greatly appreciate it! Right now, I'm adding the desired functionality via
a function that accepts Matplotlib Axes instances and binds custom
attributes/methods to these instances via Python's type.MethodType, but
this seems like a rather clunky and un-Pythonic approach to building what
will likely be an extensive application.

Thank you in advance for your help!

Best,

Daniel McNeela
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160605/daa6517a/attachment.html>

From Hubert.Holin at free.fr  Sun Jun  5 20:02:51 2016
From: Hubert.Holin at free.fr (Hubert Holin)
Date: Mon, 6 Jun 2016 02:02:51 +0200
Subject: [Matplotlib-devel] [matplotlib-devel] Ternary or triangle plots
In-Reply-To: <021ADB6F-6951-447A-83DF-6968A5D591CB@free.fr>
References: <4E78FF22.1050207@gmail.com>
 <021ADB6F-6951-447A-83DF-6968A5D591CB@free.fr>
Message-ID: <BFD59AF0-3CF2-4629-8A23-2642B59860D9@free.fr>

Paris (U.E.), le 06/06/2016

	Bonsoir

		Nearly five years have gone by? I now find myself needing the code for triangle plots I wrote way back then for the article I mentioned and is now about finished. I the mean time, I see that your submission has grown quite nicely. There are still some differences between the two. Would my offer of contributing some additional functionality, or some variant appearance, still be of interest to the community?

	Merci

			Hubert Holin



> On 21 Sep 2011, at 00:20, Hubert Holin <hubert.holin at free.fr> wrote:
> 
> Paris (U.E.), le 21/09/2011
> 
> 	Bonsoir
> 
> 		I have been working in my infinitesimally small spare time for the last few months on triangle plots. Attached bellow are a few output examples (bulky because I chose the Tiff format for ?historical? reasons). I still have quite a few variations I want to code (and perhaps an article to write dealing with triangle plots and some densities). I have not made anything public yet (bad habit, I know?), but it would be a shame if we duplicated work. Would you be interested in merging our work?
> 
> 	Hubert Holin
> 
> <test_baseline_trigridcontour.tif>
> <test_baseline_trigridscatter.tif>
> 
> 
> On 20 sept. 2011, at 23:01, Kevin Davies wrote:
> 
>> Hello,
>> I'm attaching two demo plots of a class that creates ternary or triangle plots.  I've done the best I can, but I don't think the code is ready for prime time.  I think it needs help from an expert on matplotlib projections.  I've created a branch with the ternary.py file:
>> https://github.com/kdavies4/matplotlib/compare/master...ternary <https://github.com/kdavies4/matplotlib/compare/master...ternary>
>> 
>> Kevin
>> <ternary1.png><ternary2.png>------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________ <http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________>
>> Matplotlib-devel mailing list
>> Matplotlib-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/cd448478/attachment.html>

From tcaswell at gmail.com  Sun Jun  5 20:31:07 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 06 Jun 2016 00:31:07 +0000
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
Message-ID: <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>

Simply sub-classing any of those classes in your code would reasonable.

I am curious about what sort of extensions you are adding?  I think in many
cases writing functions that take in `Axes` (or `Figure` if that is the
right scope) objects and operate on them.

An example of a project that is sub-classing `Axes` is
https://github.com/scls19fr/windrose .

Tom

On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com>
wrote:

> Hi All,
>
> I'm currently developing a Python package built on top of Matplotlib, and
> I'd like to add custom functionality to the Axes class while still
> retaining all of the default Matplotlib syntax and commands. To do this,
> I'd like to subclass matplotlib.axes.Axes (or possibly
> matplotlib.axes._base._AxesBase) and add additional class attributes and
> methods. Ideally, I'd like to do this without forking Matplotlib and
> directly editing the source so as to maintain compatibility with future
> Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
> optional FigureClass argument which I could use to pass a custom subclass
> of Figure. I was thinking I could subclass Figure such that the subclass
> overrides methods such as Figure.add_subplot() by calling the superclass's
> method and passing my custom Axes subclass in as an optional argument. But
> I'm not sure which methods I'd have to override, or how deep the rabbit
> hole goes, as Axes objects seem to be generated in a number of places
> throughout the Matplotlib source.
>
> If anyone who is familiar with the code base might be able to suggest a
> simple way in which I could accomplish this desired behavior, I would
> greatly appreciate it! Right now, I'm adding the desired functionality via
> a function that accepts Matplotlib Axes instances and binds custom
> attributes/methods to these instances via Python's type.MethodType, but
> this seems like a rather clunky and un-Pythonic approach to building what
> will likely be an extensive application.
>
> Thank you in advance for your help!
>
> Best,
>
> Daniel McNeela
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/099cf503/attachment-0001.html>

From tcaswell at gmail.com  Sun Jun  5 20:58:19 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 06 Jun 2016 00:58:19 +0000
Subject: [Matplotlib-devel] [matplotlib-devel] Ternary or triangle plots
In-Reply-To: <BFD59AF0-3CF2-4629-8A23-2642B59860D9@free.fr>
References: <4E78FF22.1050207@gmail.com>
 <021ADB6F-6951-447A-83DF-6968A5D591CB@free.fr>
 <BFD59AF0-3CF2-4629-8A23-2642B59860D9@free.fr>
Message-ID: <CAA48SF-gn5OZ=kS3dGbBEXmEs1702Mz8pK0gu2xDvjkNTBT=Hg@mail.gmail.com>

Yes, I think we are still interested, either in main-line or as a
stand-alone package under the matplotlib gh organization.

There is an open PR with a version of this code:
https://github.com/matplotlib/matplotlib/pull/3828 that needs some
attention.

Tom

On Sun, Jun 5, 2016 at 8:11 PM Hubert Holin <Hubert.Holin at free.fr> wrote:

> Paris (U.E.), le 06/06/2016
>
> Bonsoir
>
> Nearly five years have gone by? I now find myself needing the code for
> triangle plots I wrote way back then for the article I mentioned and is now
> about finished. I the mean time, I see that your submission has grown quite
> nicely. There are still some differences between the two. Would my offer of
> contributing some additional functionality, or some variant appearance,
> still be of interest to the community?
>
> Merci
>
> Hubert Holin
>
>
>
> On 21 Sep 2011, at 00:20, Hubert Holin <hubert.holin at free.fr> wrote:
>
> Paris (U.E.), le 21/09/2011
>
> Bonsoir
>
> I have been working in my infinitesimally small spare time for the last
> few months on triangle plots. Attached bellow are a few output examples
> (bulky because I chose the Tiff format for ?historical? reasons). I still
> have quite a few variations I want to code (and perhaps an article to write
> dealing with triangle plots and some densities). I have not made anything
> public yet (bad habit, I know?), but it would be a shame if we duplicated
> work. Would you be interested in merging our work?
>
> Hubert Holin
>
> <test_baseline_trigridcontour.tif>
> <test_baseline_trigridscatter.tif>
>
>
> On 20 sept. 2011, at 23:01, Kevin Davies wrote:
>
> Hello,
> I'm attaching two demo plots of a class that creates ternary or triangle
> plots.  I've done the best I can, but I don't think the code is ready for
> prime time.  I think it needs help from an expert on matplotlib
> projections.  I've created a branch with the ternary.py file:
> https://github.com/kdavies4/matplotlib/compare/master...ternary
>
> Kevin
> <ternary1.png><ternary2.png>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
>
> http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/fe11b65d/attachment.html>

From daniel.mcneela at gmail.com  Sun Jun  5 22:37:35 2016
From: daniel.mcneela at gmail.com (Daniel McNeela)
Date: Sun, 5 Jun 2016 19:37:35 -0700
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
 <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
Message-ID: <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>

Basically I'm adding a "layer" construct to the Axes model that allows
users to define groups of Matplotlib artists that can be manipulated,
hidden, displayed, styled, etc. in tandem without affecting those artists
which are on other layers. It's sort of analogous to the way in which
layers work in Photoshop.

The issue with simply subclassing the Matplotlib Axes is that I want my
subclass to fully integrate with pyplot and other modules. For example, if
a user has my module imported and runs

>>> fig = plt.figure()
>>> subplot = plt.subplot(111)

I'd like for subplot to be an instance of my subclassed Axes rather than of
the default one provided by Matplotlib.

On Sun, Jun 5, 2016 at 5:31 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Simply sub-classing any of those classes in your code would reasonable.
>
> I am curious about what sort of extensions you are adding?  I think in
> many cases writing functions that take in `Axes` (or `Figure` if that is
> the right scope) objects and operate on them.
>
> An example of a project that is sub-classing `Axes` is
> https://github.com/scls19fr/windrose .
>
> Tom
>
> On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com>
> wrote:
>
>> Hi All,
>>
>> I'm currently developing a Python package built on top of Matplotlib, and
>> I'd like to add custom functionality to the Axes class while still
>> retaining all of the default Matplotlib syntax and commands. To do this,
>> I'd like to subclass matplotlib.axes.Axes (or possibly
>> matplotlib.axes._base._AxesBase) and add additional class attributes and
>> methods. Ideally, I'd like to do this without forking Matplotlib and
>> directly editing the source so as to maintain compatibility with future
>> Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
>> optional FigureClass argument which I could use to pass a custom subclass
>> of Figure. I was thinking I could subclass Figure such that the subclass
>> overrides methods such as Figure.add_subplot() by calling the superclass's
>> method and passing my custom Axes subclass in as an optional argument. But
>> I'm not sure which methods I'd have to override, or how deep the rabbit
>> hole goes, as Axes objects seem to be generated in a number of places
>> throughout the Matplotlib source.
>>
>> If anyone who is familiar with the code base might be able to suggest a
>> simple way in which I could accomplish this desired behavior, I would
>> greatly appreciate it! Right now, I'm adding the desired functionality via
>> a function that accepts Matplotlib Axes instances and binds custom
>> attributes/methods to these instances via Python's type.MethodType, but
>> this seems like a rather clunky and un-Pythonic approach to building what
>> will likely be an extensive application.
>>
>> Thank you in advance for your help!
>>
>> Best,
>>
>> Daniel McNeela
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160605/6622ff79/attachment.html>

From ariza.federico at gmail.com  Mon Jun  6 06:19:19 2016
From: ariza.federico at gmail.com (Federico Ariza)
Date: Mon, 6 Jun 2016 06:19:19 -0400
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
 <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
 <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>
Message-ID: <CAA5CsYf55LgYc4bJj7JStB9=YoUgirWDOtL+TghGXZaQDxCn5A@mail.gmail.com>

I have done similar things (hiding groups of artists) using the tool
manager and custom build tools.

In general I just use the gid property of each artist to keep track of
different groups and on trigger I hide a specific group.

Also I use it to pop-up an artist-styler to change colors, linestyle etc...

It is indirect but allows to perform operations without touching base
classes.

I know this is not what you asked but hope it helps

Federico
On Jun 5, 2016 10:38 PM, "Daniel McNeela" <daniel.mcneela at gmail.com> wrote:

> Basically I'm adding a "layer" construct to the Axes model that allows
> users to define groups of Matplotlib artists that can be manipulated,
> hidden, displayed, styled, etc. in tandem without affecting those artists
> which are on other layers. It's sort of analogous to the way in which
> layers work in Photoshop.
>
> The issue with simply subclassing the Matplotlib Axes is that I want my
> subclass to fully integrate with pyplot and other modules. For example, if
> a user has my module imported and runs
>
> >>> fig = plt.figure()
> >>> subplot = plt.subplot(111)
>
> I'd like for subplot to be an instance of my subclassed Axes rather than
> of the default one provided by Matplotlib.
>
> On Sun, Jun 5, 2016 at 5:31 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
>
>> Simply sub-classing any of those classes in your code would reasonable.
>>
>> I am curious about what sort of extensions you are adding?  I think in
>> many cases writing functions that take in `Axes` (or `Figure` if that is
>> the right scope) objects and operate on them.
>>
>> An example of a project that is sub-classing `Axes` is
>> https://github.com/scls19fr/windrose .
>>
>> Tom
>>
>> On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> I'm currently developing a Python package built on top of Matplotlib,
>>> and I'd like to add custom functionality to the Axes class while still
>>> retaining all of the default Matplotlib syntax and commands. To do this,
>>> I'd like to subclass matplotlib.axes.Axes (or possibly
>>> matplotlib.axes._base._AxesBase) and add additional class attributes and
>>> methods. Ideally, I'd like to do this without forking Matplotlib and
>>> directly editing the source so as to maintain compatibility with future
>>> Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
>>> optional FigureClass argument which I could use to pass a custom subclass
>>> of Figure. I was thinking I could subclass Figure such that the subclass
>>> overrides methods such as Figure.add_subplot() by calling the superclass's
>>> method and passing my custom Axes subclass in as an optional argument. But
>>> I'm not sure which methods I'd have to override, or how deep the rabbit
>>> hole goes, as Axes objects seem to be generated in a number of places
>>> throughout the Matplotlib source.
>>>
>>> If anyone who is familiar with the code base might be able to suggest a
>>> simple way in which I could accomplish this desired behavior, I would
>>> greatly appreciate it! Right now, I'm adding the desired functionality via
>>> a function that accepts Matplotlib Axes instances and binds custom
>>> attributes/methods to these instances via Python's type.MethodType, but
>>> this seems like a rather clunky and un-Pythonic approach to building what
>>> will likely be an extensive application.
>>>
>>> Thank you in advance for your help!
>>>
>>> Best,
>>>
>>> Daniel McNeela
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/459a8a1a/attachment-0001.html>

From juichenieder-nabb at yahoo.co.uk  Mon Jun  6 08:34:57 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Mon, 6 Jun 2016 12:34:57 +0000 (UTC)
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <CAA5CsYf55LgYc4bJj7JStB9=YoUgirWDOtL+TghGXZaQDxCn5A@mail.gmail.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
 <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
 <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>
 <CAA5CsYf55LgYc4bJj7JStB9=YoUgirWDOtL+TghGXZaQDxCn5A@mail.gmail.com>
Message-ID: <1933965871.9130247.1465216497110.JavaMail.yahoo@mail.yahoo.com>

Hi Daniel,I like your ideas.? As Fedrico said, the group part has already exists, see http://matplotlib.org/examples/user_interfaces/toolmanager.html for an example of this, the toolmanager part we still consider as experimental until at least 2.1 when we hope to have gotten it working with all backends together with http://matplotlib.org/devel/MEP/MEP27.html, refactoring the FigureManager so as to decouple pyplot from the backends, a project that I have been working on.
The other parts, http://matplotlib.org/devel/MEP/MEP26.html which looks at creating Cascading Artist Style Sheets, based upon the CSS language spec for websites.? I don't think anyone has started working on this, and may need some more definition and working out; then I started creating another MEP to figure out how to refactor the Axes and related classes into a more coherent and readably understandable structure, you can see the limited progress i have made at defining the document here... https://github.com/matplotlib/matplotlib/pull/5029 I have a few more ideas I want to put into this, just needing to find time to get back to it, probably once we have the backend refactor finished.
Of course, matplotlib works as a fully opensource project, fully collaborative, so any source code changes you would like to see, make them in a fork, and PR them back to the matplotlib (or as I got started, forking Federico's toolmanager fork, and PRing back to him and his PR before merging into master, as part of MEP22).? And of course, feel free to get involved in any of this stuff if you like it, the more the merrier :).
Best,OceanWolf

      From: Federico Ariza <ariza.federico at gmail.com>
 To: Daniel McNeela <daniel.mcneela at gmail.com> 
Cc: matplotlib development list <matplotlib-devel at python.org>
 Sent: Monday, 6 June 2016, 12:19
 Subject: Re: [Matplotlib-devel] (no subject)
   
I have done similar things (hiding groups of artists) using the tool manager and custom build tools.In general I just use the gid property of each artist to keep track of different groups and on trigger I hide a specific group.Also I use it to pop-up an artist-styler to change colors, linestyle etc...It is indirect but allows to perform operations without touching base classes.I know this is not what you asked but hope it helpsFedericoOn Jun 5, 2016 10:38 PM, "Daniel McNeela" <daniel.mcneela at gmail.com> wrote:

Basically I'm adding a "layer" construct to the Axes model that allows users to define groups of Matplotlib artists that can be manipulated, hidden, displayed, styled, etc. in tandem without affecting those artists which are on other layers. It's sort of analogous to the way in which layers work in Photoshop.
The issue with simply subclassing the Matplotlib Axes is that I want my subclass to fully integrate with pyplot and other modules. For example, if a user has my module imported and runs
>>> fig = plt.figure()>>> subplot = plt.subplot(111)
I'd like for subplot to be an instance of my subclassed Axes rather than of the default one provided by Matplotlib.
On Sun, Jun 5, 2016 at 5:31 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

Simply sub-classing any of those classes in your code would reasonable.
I am curious about what sort of extensions you are adding?? I think in many cases writing functions that take in `Axes` (or `Figure` if that is the right scope) objects and operate on them.
An example of a project that is sub-classing `Axes` is?https://github.com/scls19fr/windrose?.
Tom
On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com> wrote:

Hi All,
I'm currently developing a Python package built on top of Matplotlib, and I'd like to add custom functionality to the Axes class while still retaining all of the default Matplotlib syntax and commands. To do this, I'd like to subclass matplotlib.axes.Axes (or possibly matplotlib.axes._base._AxesBase) and add additional class attributes and methods. Ideally, I'd like to do this without forking Matplotlib and directly editing the source so as to maintain compatibility with future Matplotlib releases. I see that in pyplot.py, calls to figure() accept an optional FigureClass argument which I could use to pass a custom subclass of Figure. I was thinking I could subclass Figure such that the subclass overrides methods such as Figure.add_subplot() by calling the superclass's method and passing my custom Axes subclass in as an optional argument. But I'm not sure which methods I'd have to override, or how deep the rabbit hole goes, as Axes objects seem to be generated in a number of places throughout the Matplotlib source.
If anyone who is familiar with the code base might be able to suggest a simple way in which I could accomplish this desired behavior, I would greatly appreciate it! Right now, I'm adding the desired functionality via a function that accepts Matplotlib Axes instances and binds custom attributes/methods to these instances via Python's type.MethodType, but this seems like a rather clunky and un-Pythonic approach to building what will likely be an extensive application.
Thank you in advance for your help!
Best,
Daniel McNeela_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel




_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel



_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/b537cfee/attachment.html>

From daniel.mcneela at gmail.com  Mon Jun  6 14:01:25 2016
From: daniel.mcneela at gmail.com (Daniel McNeela)
Date: Mon, 6 Jun 2016 11:01:25 -0700
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <1933965871.9130247.1465216497110.JavaMail.yahoo@mail.yahoo.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
 <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
 <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>
 <CAA5CsYf55LgYc4bJj7JStB9=YoUgirWDOtL+TghGXZaQDxCn5A@mail.gmail.com>
 <1933965871.9130247.1465216497110.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <CAOPhMLj9er0XV7Ww-5NLPP9Nu-X8pGGd5MF_=VH-tytn4zirNg@mail.gmail.com>

Thank you OceanWolf and Federico. I was previously unaware of the gid
property of Artists and the new ToolManager classes, and it looks like what
I have been doing is pretty similar to what is contained therein. You can
take a look at my progress here:

https://github.com/mcneela/Retina/tree/master/retina

(The code is a bit messy as I haven't gotten around to cleaning it up yet.)

Basically I just have a layer dictionary associated with each axes in which
I can update, set, and delete properties. If you interactively run the two
examples included in that folder, you can type in commands at the Python
interpreter and watch the plots change in response. For example, with the
basic_layer_demo, you could run the following

>>> subplots.hide("cubic")    # Hides the 'cubic' layer while keeping the
'quadratic' layer displayed

>>> subplots.show("cubic")    # Redisplays the "cubic" layer

>>> subplots.set_style("cubic", 'ro')    # Changes the style of the cubic
layer
>>> subplots.build_layers()         # Rebuilds the layers so that the new
styling takes effect

Is this something that you think would have utility if directly
incorporated into Matplotlib's axes class, or is better to just have it
built out on top as is done with the ToolManager classes?

On Mon, Jun 6, 2016 at 5:34 AM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
wrote:

> Hi Daniel,
> I like your ideas.  As Fedrico said, the group part has already exists,
> see http://matplotlib.org/examples/user_interfaces/toolmanager.html for
> an example of this, the toolmanager part we still consider as experimental
> until at least 2.1 when we hope to have gotten it working with all backends
> together with http://matplotlib.org/devel/MEP/MEP27.html, refactoring the
> FigureManager so as to decouple pyplot from the backends, a project that I
> have been working on.
>
> The other parts, http://matplotlib.org/devel/MEP/MEP26.html which looks
> at creating Cascading Artist Style Sheets, based upon the CSS language spec
> for websites.  I don't think anyone has started working on this, and may
> need some more definition and working out; then I started creating another
> MEP to figure out how to refactor the Axes and related classes into a more
> coherent and readably understandable structure, you can see the limited
> progress i have made at defining the document here...
> https://github.com/matplotlib/matplotlib/pull/5029 I have a few more
> ideas I want to put into this, just needing to find time to get back to it,
> probably once we have the backend refactor finished.
>
> Of course, matplotlib works as a fully opensource project, fully
> collaborative, so any source code changes you would like to see, make them
> in a fork, and PR them back to the matplotlib (or as I got started, forking
> Federico's toolmanager fork, and PRing back to him and his PR before
> merging into master, as part of MEP22).  And of course, feel free to get
> involved in any of this stuff if you like it, the more the merrier :).
>
> Best,
> OceanWolf
>
> ------------------------------
> *From:* Federico Ariza <ariza.federico at gmail.com>
> *To:* Daniel McNeela <daniel.mcneela at gmail.com>
> *Cc:* matplotlib development list <matplotlib-devel at python.org>
> *Sent:* Monday, 6 June 2016, 12:19
> *Subject:* Re: [Matplotlib-devel] (no subject)
>
> I have done similar things (hiding groups of artists) using the tool
> manager and custom build tools.
> In general I just use the gid property of each artist to keep track of
> different groups and on trigger I hide a specific group.
> Also I use it to pop-up an artist-styler to change colors, linestyle etc...
> It is indirect but allows to perform operations without touching base
> classes.
> I know this is not what you asked but hope it helps
> Federico
> On Jun 5, 2016 10:38 PM, "Daniel McNeela" <daniel.mcneela at gmail.com>
> wrote:
>
> Basically I'm adding a "layer" construct to the Axes model that allows
> users to define groups of Matplotlib artists that can be manipulated,
> hidden, displayed, styled, etc. in tandem without affecting those artists
> which are on other layers. It's sort of analogous to the way in which
> layers work in Photoshop.
>
> The issue with simply subclassing the Matplotlib Axes is that I want my
> subclass to fully integrate with pyplot and other modules. For example, if
> a user has my module imported and runs
>
> >>> fig = plt.figure()
> >>> subplot = plt.subplot(111)
>
> I'd like for subplot to be an instance of my subclassed Axes rather than
> of the default one provided by Matplotlib.
>
> On Sun, Jun 5, 2016 at 5:31 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
>
> Simply sub-classing any of those classes in your code would reasonable.
>
> I am curious about what sort of extensions you are adding?  I think in
> many cases writing functions that take in `Axes` (or `Figure` if that is
> the right scope) objects and operate on them.
>
> An example of a project that is sub-classing `Axes` is
> https://github.com/scls19fr/windrose .
>
> Tom
>
> On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com>
> wrote:
>
> Hi All,
>
> I'm currently developing a Python package built on top of Matplotlib, and
> I'd like to add custom functionality to the Axes class while still
> retaining all of the default Matplotlib syntax and commands. To do this,
> I'd like to subclass matplotlib.axes.Axes (or possibly
> matplotlib.axes._base._AxesBase) and add additional class attributes and
> methods. Ideally, I'd like to do this without forking Matplotlib and
> directly editing the source so as to maintain compatibility with future
> Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
> optional FigureClass argument which I could use to pass a custom subclass
> of Figure. I was thinking I could subclass Figure such that the subclass
> overrides methods such as Figure.add_subplot() by calling the superclass's
> method and passing my custom Axes subclass in as an optional argument. But
> I'm not sure which methods I'd have to override, or how deep the rabbit
> hole goes, as Axes objects seem to be generated in a number of places
> throughout the Matplotlib source.
>
> If anyone who is familiar with the code base might be able to suggest a
> simple way in which I could accomplish this desired behavior, I would
> greatly appreciate it! Right now, I'm adding the desired functionality via
> a function that accepts Matplotlib Axes instances and binds custom
> attributes/methods to these instances via Python's type.MethodType, but
> this seems like a rather clunky and un-Pythonic approach to building what
> will likely be an extensive application.
>
> Thank you in advance for your help!
>
> Best,
>
> Daniel McNeela
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160606/99157587/attachment.html>

From daniel.mcneela at gmail.com  Tue Jun  7 03:22:12 2016
From: daniel.mcneela at gmail.com (Daniel McNeela)
Date: Tue, 7 Jun 2016 00:22:12 -0700
Subject: [Matplotlib-devel] (no subject)
In-Reply-To: <CAOPhMLj9er0XV7Ww-5NLPP9Nu-X8pGGd5MF_=VH-tytn4zirNg@mail.gmail.com>
References: <CAOPhMLgBPuP3MNPhRb+v6_vxV5FK4gLY6YYb9ghbM6eREgemzQ@mail.gmail.com>
 <CAA48SF-ygsWQarAkRx0LCmZWCY6TZQ6SP6DvuiU3OUqY=yU_Jg@mail.gmail.com>
 <CAOPhMLi=OAOAu=nU+dWYhmGfvsSoZAzTjaJOH1pZFgDm919BSg@mail.gmail.com>
 <CAA5CsYf55LgYc4bJj7JStB9=YoUgirWDOtL+TghGXZaQDxCn5A@mail.gmail.com>
 <1933965871.9130247.1465216497110.JavaMail.yahoo@mail.yahoo.com>
 <CAOPhMLj9er0XV7Ww-5NLPP9Nu-X8pGGd5MF_=VH-tytn4zirNg@mail.gmail.com>
Message-ID: <CAOPhMLgZ3mTw-j=9YC53TYa50MLg3XZ-KBoqYgSs=4dgOksScg@mail.gmail.com>

I actually was able to achieve the desired behavior by creating my own
projection based on my modified Axes class and adding that projection to
the projection registry.

On Mon, Jun 6, 2016 at 11:01 AM, Daniel McNeela <daniel.mcneela at gmail.com>
wrote:

> Thank you OceanWolf and Federico. I was previously unaware of the gid
> property of Artists and the new ToolManager classes, and it looks like what
> I have been doing is pretty similar to what is contained therein. You can
> take a look at my progress here:
>
> https://github.com/mcneela/Retina/tree/master/retina
>
> (The code is a bit messy as I haven't gotten around to cleaning it up yet.)
>
> Basically I just have a layer dictionary associated with each axes in
> which I can update, set, and delete properties. If you interactively run
> the two examples included in that folder, you can type in commands at the
> Python interpreter and watch the plots change in response. For example,
> with the basic_layer_demo, you could run the following
>
> >>> subplots.hide("cubic")    # Hides the 'cubic' layer while keeping the
> 'quadratic' layer displayed
>
> >>> subplots.show("cubic")    # Redisplays the "cubic" layer
>
> >>> subplots.set_style("cubic", 'ro')    # Changes the style of the cubic
> layer
> >>> subplots.build_layers()         # Rebuilds the layers so that the new
> styling takes effect
>
> Is this something that you think would have utility if directly
> incorporated into Matplotlib's axes class, or is better to just have it
> built out on top as is done with the ToolManager classes?
>
> On Mon, Jun 6, 2016 at 5:34 AM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
> wrote:
>
>> Hi Daniel,
>> I like your ideas.  As Fedrico said, the group part has already exists,
>> see http://matplotlib.org/examples/user_interfaces/toolmanager.html for
>> an example of this, the toolmanager part we still consider as experimental
>> until at least 2.1 when we hope to have gotten it working with all backends
>> together with http://matplotlib.org/devel/MEP/MEP27.html, refactoring
>> the FigureManager so as to decouple pyplot from the backends, a project
>> that I have been working on.
>>
>> The other parts, http://matplotlib.org/devel/MEP/MEP26.html which looks
>> at creating Cascading Artist Style Sheets, based upon the CSS language spec
>> for websites.  I don't think anyone has started working on this, and may
>> need some more definition and working out; then I started creating another
>> MEP to figure out how to refactor the Axes and related classes into a more
>> coherent and readably understandable structure, you can see the limited
>> progress i have made at defining the document here...
>> https://github.com/matplotlib/matplotlib/pull/5029 I have a few more
>> ideas I want to put into this, just needing to find time to get back to it,
>> probably once we have the backend refactor finished.
>>
>> Of course, matplotlib works as a fully opensource project, fully
>> collaborative, so any source code changes you would like to see, make them
>> in a fork, and PR them back to the matplotlib (or as I got started, forking
>> Federico's toolmanager fork, and PRing back to him and his PR before
>> merging into master, as part of MEP22).  And of course, feel free to get
>> involved in any of this stuff if you like it, the more the merrier :).
>>
>> Best,
>> OceanWolf
>>
>> ------------------------------
>> *From:* Federico Ariza <ariza.federico at gmail.com>
>> *To:* Daniel McNeela <daniel.mcneela at gmail.com>
>> *Cc:* matplotlib development list <matplotlib-devel at python.org>
>> *Sent:* Monday, 6 June 2016, 12:19
>> *Subject:* Re: [Matplotlib-devel] (no subject)
>>
>> I have done similar things (hiding groups of artists) using the tool
>> manager and custom build tools.
>> In general I just use the gid property of each artist to keep track of
>> different groups and on trigger I hide a specific group.
>> Also I use it to pop-up an artist-styler to change colors, linestyle
>> etc...
>> It is indirect but allows to perform operations without touching base
>> classes.
>> I know this is not what you asked but hope it helps
>> Federico
>> On Jun 5, 2016 10:38 PM, "Daniel McNeela" <daniel.mcneela at gmail.com>
>> wrote:
>>
>> Basically I'm adding a "layer" construct to the Axes model that allows
>> users to define groups of Matplotlib artists that can be manipulated,
>> hidden, displayed, styled, etc. in tandem without affecting those artists
>> which are on other layers. It's sort of analogous to the way in which
>> layers work in Photoshop.
>>
>> The issue with simply subclassing the Matplotlib Axes is that I want my
>> subclass to fully integrate with pyplot and other modules. For example, if
>> a user has my module imported and runs
>>
>> >>> fig = plt.figure()
>> >>> subplot = plt.subplot(111)
>>
>> I'd like for subplot to be an instance of my subclassed Axes rather than
>> of the default one provided by Matplotlib.
>>
>> On Sun, Jun 5, 2016 at 5:31 PM, Thomas Caswell <tcaswell at gmail.com>
>> wrote:
>>
>> Simply sub-classing any of those classes in your code would reasonable.
>>
>> I am curious about what sort of extensions you are adding?  I think in
>> many cases writing functions that take in `Axes` (or `Figure` if that is
>> the right scope) objects and operate on them.
>>
>> An example of a project that is sub-classing `Axes` is
>> https://github.com/scls19fr/windrose .
>>
>> Tom
>>
>> On Sun, Jun 5, 2016 at 5:16 PM Daniel McNeela <daniel.mcneela at gmail.com>
>> wrote:
>>
>> Hi All,
>>
>> I'm currently developing a Python package built on top of Matplotlib, and
>> I'd like to add custom functionality to the Axes class while still
>> retaining all of the default Matplotlib syntax and commands. To do this,
>> I'd like to subclass matplotlib.axes.Axes (or possibly
>> matplotlib.axes._base._AxesBase) and add additional class attributes and
>> methods. Ideally, I'd like to do this without forking Matplotlib and
>> directly editing the source so as to maintain compatibility with future
>> Matplotlib releases. I see that in pyplot.py, calls to figure() accept an
>> optional FigureClass argument which I could use to pass a custom subclass
>> of Figure. I was thinking I could subclass Figure such that the subclass
>> overrides methods such as Figure.add_subplot() by calling the superclass's
>> method and passing my custom Axes subclass in as an optional argument. But
>> I'm not sure which methods I'd have to override, or how deep the rabbit
>> hole goes, as Axes objects seem to be generated in a number of places
>> throughout the Matplotlib source.
>>
>> If anyone who is familiar with the code base might be able to suggest a
>> simple way in which I could accomplish this desired behavior, I would
>> greatly appreciate it! Right now, I'm adding the desired functionality via
>> a function that accepts Matplotlib Axes instances and binds custom
>> attributes/methods to these instances via Python's type.MethodType, but
>> this seems like a rather clunky and un-Pythonic approach to building what
>> will likely be an extensive application.
>>
>> Thank you in advance for your help!
>>
>> Best,
>>
>> Daniel McNeela
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160607/b7fa0a37/attachment-0001.html>

From Hubert.Holin at free.fr  Tue Jun  7 19:31:26 2016
From: Hubert.Holin at free.fr (Hubert Holin)
Date: Wed, 8 Jun 2016 01:31:26 +0200
Subject: [Matplotlib-devel] [matplotlib-devel] Ternary or triangle plots
In-Reply-To: <CAA48SF-gn5OZ=kS3dGbBEXmEs1702Mz8pK0gu2xDvjkNTBT=Hg@mail.gmail.com>
References: <4E78FF22.1050207@gmail.com>
 <021ADB6F-6951-447A-83DF-6968A5D591CB@free.fr>
 <BFD59AF0-3CF2-4629-8A23-2642B59860D9@free.fr>
 <CAA48SF-gn5OZ=kS3dGbBEXmEs1702Mz8pK0gu2xDvjkNTBT=Hg@mail.gmail.com>
Message-ID: <A1BBE16E-39C0-4505-9595-AB2D855FD355@free.fr>

Paris (U.E.), le 08/06/2016

	Bonsoir

		Thank you for the good feedback. I will clean up my code, ensure that it works with the current version of matplotlib (I noticed I still use a deprecated version of Delaunay, among other things) and with Python 3.5 (which I now use), and present it. I understand the fork/branch/PR procedure, having experienced it (once?) already, but I am not familiar with what you refer as the "matplotlib gh organization?, which I understand are protected branches on GitHub. Could you please elaborate? Is there somewhere where this is detailed?

		As for the PR about the current (Kevin Davies?) implementation, I am afraid I have never actually looked at the code, so I would prefer to finish polishing up my version before trying to fix that problem. But I will definitely take a look then.

		As well, looking at that PR, I noticed that joferkington also has an implementation. It would be interesting, if he were so inclined, that he published his code as well. I believe we would all benefit if we all put forward our approaches and worked towards a satisfactory, for all, solution.

	Merci

			Hubert Holin


> On 06 Jun 2016, at 02:58, Thomas Caswell <tcaswell at gmail.com> wrote:
> 
> Yes, I think we are still interested, either in main-line or as a stand-alone package under the matplotlib gh organization.
> 
> There is an open PR with a version of this code: https://github.com/matplotlib/matplotlib/pull/3828 that needs some attention.
> 
> Tom
> 
> On Sun, Jun 5, 2016 at 8:11 PM Hubert Holin <Hubert.Holin at free.fr> wrote:
> Paris (U.E.), le 06/06/2016
> 
> 	Bonsoir
> 
> 		Nearly five years have gone by? I now find myself needing the code for triangle plots I wrote way back then for the article I mentioned and is now about finished. I the mean time, I see that your submission has grown quite nicely. There are still some differences between the two. Would my offer of contributing some additional functionality, or some variant appearance, still be of interest to the community?
> 
> 	Merci
> 
> 			Hubert Holin
> 
> 
> 
>> On 21 Sep 2011, at 00:20, Hubert Holin <hubert.holin at free.fr> wrote:
>> 
>> Paris (U.E.), le 21/09/2011
>> 
>> 	Bonsoir
>> 
>> 		I have been working in my infinitesimally small spare time for the last few months on triangle plots. Attached bellow are a few output examples (bulky because I chose the Tiff format for ?historical? reasons). I still have quite a few variations I want to code (and perhaps an article to write dealing with triangle plots and some densities). I have not made anything public yet (bad habit, I know?), but it would be a shame if we duplicated work. Would you be interested in merging our work?
>> 
>> 	Hubert Holin
>> 
>> <test_baseline_trigridcontour.tif>
>> <test_baseline_trigridscatter.tif>
>> 
>> 
>> On 20 sept. 2011, at 23:01, Kevin Davies wrote:
>> 
>>> Hello,
>>> I'm attaching two demo plots of a class that creates ternary or triangle plots.  I've done the best I can, but I don't think the code is ready for prime time.  I think it needs help from an expert on matplotlib projections.  I've created a branch with the ternary.py file:
>>> https://github.com/kdavies4/matplotlib/compare/master...ternary
>>> 
>>> Kevin
>>> <ternary1.png><ternary2.png>------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure contains a
>>> definitive record of customers, application performance, security
>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>> sense of it. Business sense. IT sense. Common sense.
>>> http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel


From rob.clewley at gmail.com  Thu Jun  9 23:28:54 2016
From: rob.clewley at gmail.com (Rob Clewley)
Date: Thu, 9 Jun 2016 23:28:54 -0400
Subject: [Matplotlib-devel] Status of toolbar/toolmanager changes (not
 working for me)?
Message-ID: <CA+7tCyQOMfJZE6SxQrHX4vdOowiaJzpLp7jn445_B6451jMD_Q@mail.gmail.com>

I'm using v1.5.1 with python 2.7.5 and I was reading the discussion on
https://github.com/matplotlib/matplotlib/pull/3652

and trying to reproduce the toolbar manipulation shown at

https://github.com/fariza/pycon2015/blob/master/ToolDemo.ipynb

I can't get it to work from either regular python or ipython
(console), at least not with my WXagg, GTKagg or GTKCairo backends.

In my matplotlibrc I have set toolbar to be toolmanager.

After successfully getting a figure window with fig, ax =
plt.subplots(), I find that fig.canvas.manager.toolbar is None and
there is no toolmanager attribute in the manager.

Did I miss something that has changed, because the pull seemed to
apply to 1.5.1?

Thanks,
Rob

From ariza.federico at gmail.com  Fri Jun 10 06:59:00 2016
From: ariza.federico at gmail.com (Federico Ariza)
Date: Fri, 10 Jun 2016 06:59:00 -0400
Subject: [Matplotlib-devel] Status of toolbar/toolmanager changes (not
 working for me)?
In-Reply-To: <CA+7tCyQOMfJZE6SxQrHX4vdOowiaJzpLp7jn445_B6451jMD_Q@mail.gmail.com>
References: <CA+7tCyQOMfJZE6SxQrHX4vdOowiaJzpLp7jn445_B6451jMD_Q@mail.gmail.com>
Message-ID: <CAA5CsYdQx57gP-kKmGsOTPwwAxu-2Ud7fRDkSW_MVsXBubQqrw@mail.gmail.com>

Hi

The main problem is that the new Toolbar has been implemented only for Gtk3
and Tk

Try running the example in examples/user_interfaces/toolmanager.py if it
fails please report it.

Why we haven't finished the job on other backends? We are working on MEP27
that will offer substantial benefits when implementing the changes needed
for ToolManager to work.

Every small change has to be ported to all the backends, we decided it is
more efficient for us, to try to iron all the problems with just two
backends before changing all the others.

If you need any help getting it to run please let me know and I'll do my
best to help you.

Federico
On Jun 9, 2016 11:29 PM, "Rob Clewley" <rob.clewley at gmail.com> wrote:

> I'm using v1.5.1 with python 2.7.5 and I was reading the discussion on
> https://github.com/matplotlib/matplotlib/pull/3652
>
> and trying to reproduce the toolbar manipulation shown at
>
> https://github.com/fariza/pycon2015/blob/master/ToolDemo.ipynb
>
> I can't get it to work from either regular python or ipython
> (console), at least not with my WXagg, GTKagg or GTKCairo backends.
>
> In my matplotlibrc I have set toolbar to be toolmanager.
>
> After successfully getting a figure window with fig, ax =
> plt.subplots(), I find that fig.canvas.manager.toolbar is None and
> there is no toolmanager attribute in the manager.
>
> Did I miss something that has changed, because the pull seemed to
> apply to 1.5.1?
>
> Thanks,
> Rob
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160610/393142c8/attachment.html>

From alessandro.bardelli at henesis.eu  Fri Jun 10 14:40:20 2016
From: alessandro.bardelli at henesis.eu (Alessandro Pietro Bardelli)
Date: Fri, 10 Jun 2016 20:40:20 +0200
Subject: [Matplotlib-devel] Fwd: Re: [matplotlib-devel] update x axis of a
 subplot according to the y axis of another one in python/matplotlib
In-Reply-To: <575A6A2B.1030301@henesis.eu>
References: <575A6A2B.1030301@henesis.eu>
Message-ID: <575B0994.5050909@henesis.eu>

Forwarded from the old mailing list


Hello Benjamin,
last weekend (after more than a year... :-[ ) I found some spare time to 
refactor a bit the solution I implemented to solve the axis synchronisation.
I have answered my own question on stackoverflow 
(http://stackoverflow.com/questions/28239054/update-the-x-axis-of-a-matplotlib-subplot-according-to-the-y-axis-of-a-different/37265661#37265661)
and I have shared on github 
(https://github.com/apbard/OrthogonalProjection) a simple class that 
allows to easily make orthogonal projections plots with full axis 
synchronisation and support for different basic plot types.
Thanks again for the hint and sorry for the delay...

Alessandro

On 12/02/2015 19:58, Alessandro Pietro Bardelli wrote:
> thanks for your answer.
> I have played a bit with the callbacks and seems very promising.
> i'll work on it in the weekend and drop an email as soon as I have 
> tested it properly :)
> thanks again
>
> Alessandro
>
> On 12/02/2015 15:35, Benjamin Root wrote:
>> Sharing the same axis across subplots is implemented via matplotlib's 
>> interactive framework, and is available by default. Glue is built on 
>> top of matplotlib, extending its interactive framework with many 
>> additional tools. Yes, it might be overkill for this singular task, 
>> but implementing orthogonal axis sharing isn't trivial, either, so 
>> suggesting a pre-packaged solution is merely pragmatic.
>>
>> Essentially, one would have to register callbacks for changes in each 
>> of the parent subplot's axis. This, in of itself, isn't really all 
>> that difficult once one learns the event framework. I think what 
>> might be very tricky is doing it for the 3d axes. As the de facto 
>> maintainer of mplot3d, I have never really tested axis sharing for 
>> mplot3d. I suspect that it would work exactly as you'd expect for the 
>> x and y axes, but the z axis may prove to be quirky. I don't know, I 
>> haven't ever tried it out. In general, the z-axis implementation is a 
>> bit of a kludge, so things tend to be different for it...
>>
>> Here is an example of how to register callbacks to changes in a 
>> particular axis. Hopefully, it can give you a nice leg up on the 
>> problem. Let me know if you have problems with the z-axis, I might be 
>> able to help sort it out. If you can get this to work, I would 
>> certainly love to include it in the gallery.
>> http://matplotlib.org/examples/event_handling/viewlims.html
>>
>> Cheers!
>> Ben Root
>>
>>
>> On Thu, Feb 12, 2015 at 4:32 AM, Alessandro Pietro Bardelli 
>> <alessandro.bardelli at henesis.eu> wrote:
>>
>>     Thanks for the answer.
>>     Glue seems a quite cool project but it is also a bit overkill for
>>     this specific task, isn't it?
>>     Basically I just would like tell sharex to point the Yaxis of the
>>     axes object.
>>     Isn't there a way to do this within matplotlib?
>>     thanks
>>
>>     Alessandro
>>
>>     On 11/02/2015 16:41, Benjamin Root wrote:
>>>     Sounds to me like you want to use glue:
>>>     http://www.glueviz.org/en/stable/
>>>
>>>
>>>     On Wed, Feb 11, 2015 at 3:15 AM, Alessandro Pietro Bardelli
>>>     <alessandro.bardelli at henesis.eu> wrote:
>>>
>>>         I would like to plot an orthogonal projection (like this one
>>>         http://i.stack.imgur.com/DnNds.jpg) using matplotlib
>>>         possibly including also the 3D subplot. All the pictures
>>>         should share common axes.
>>>
>>>         |fig =plt.figure()ax =fig.add_subplot(221,title="XZ")bx
>>>         =fig.add_subplot(222,title="YZ",sharey=ax)cx
>>>         =fig.add_subplot(223,title="XY",sharex=ax,sharey=[something
>>>         like bx.Xaxis])dx
>>>         =fig.add_subplot(224,title="XYZ",projection="3d",sharex=ax,sharey=bx,sharez=[something
>>>         like bx.Yaxis]|
>>>
>>>         The problem is that I have to "link" on X axis of a plot
>>>         with the Y one of another and
>>>         Is there a way to accomplish this?
>>>
>>>         Thanks
>>>
>>>         Alessandro
>>>
>>>         p.s. i have posted this question also on StackOverflow:
>>>         http://stackoverflow.com/questions/28239054/update-x-axis-of-a-subplot-according-to-the-y-axis-of-another-one-in-python-matp
>>>
>>>
>>>         ------------------------------------------------------------------------------
>>>         Dive into the World of Parallel Programming. The Go Parallel
>>>         Website,
>>>         sponsored by Intel and developed in partnership with
>>>         Slashdot Media, is your
>>>         hub for all things parallel software development, from
>>>         weekly thought
>>>         leadership blogs to news, videos, case studies, tutorials
>>>         and more. Take a
>>>         look and join the conversation now.
>>>         http://goparallel.sourceforge.net/
>>>         _______________________________________________
>>>         Matplotlib-devel mailing list
>>>         Matplotlib-devel at lists.sourceforge.net
>>>         <mailto:Matplotlib-devel at lists.sourceforge.net>
>>>         https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>>
>>
>>     -- 
>>
>>     ----------------------------------
>>     Alessandro Pietro Bardelli
>>
>>     HENESIS s.r.l.
>>     P.IVA (VAT. N.) IT02280660354
>>     Viale dei Mille, 108
>>     43125 PARMA (IT)
>>
>>     Email: alessandro.bardelli at henesis.eu
>>     <mailto:alessandro.bardelli at henesis.eu>
>>
>>     Tel: (+39)05211854211 <tel:%28%2B39%2905211854211>
>>     Fax: (+39)05211854515 <tel:%28%2B39%2905211854515>
>>     SkypeID: henesis_srl
>>     Web: www.henesis.eu <http://www.henesis.eu>
>>     ----------------------------------
>>
>>
>
> -- 
>
> ----------------------------------
> Alessandro Pietro Bardelli
>
> HENESIS s.r.l.
> P.IVA (VAT. N.) IT02280660354
> Viale dei Mille, 108
> 43125 PARMA (IT)
>
> Email: alessandro.bardelli at henesis.eu
>
> Tel: (+39)05211854211
> Fax: (+39)05211854515
> SkypeID: henesis_srl
> Web: www.henesis.eu
> ----------------------------------

-- 

----------------------------------
Alessandro Pietro Bardelli

Camlin Italy S.r.l - part of Camlin group
P.IVA (VAT. N.) IT02280660354
Strada Budellungo, 2
43123 PARMA (IT)

Email: alessandro.bardelli at henesis.eu

Tel: (+39)05211854211 (extension 14)
Fax: (+39)05211854515
Web: www.henesis.eu
----------------------------------






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160610/887a692e/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
-------------- next part --------------
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


From morph at debian.org  Sat Jun 11 15:12:02 2016
From: morph at debian.org (Sandro Tosi)
Date: Sat, 11 Jun 2016 20:12:02 +0100
Subject: [Matplotlib-devel] [Matplotlib-announce] matplotlib v2.0.0b1
In-Reply-To: <CAA48SF-Yir9CVDD7hnWd9tKom5usDd6LjjO00_TTt=Naj7LHkg@mail.gmail.com>
References: <CAA48SF-Yir9CVDD7hnWd9tKom5usDd6LjjO00_TTt=Naj7LHkg@mail.gmail.com>
Message-ID: <CAB4XWXwhgm5zK8WU7VW2Jb6VDAkKk1mPX5O7snU3qv_8yKCBjw@mail.gmail.com>

On Tue, May 31, 2016 at 5:01 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
> We tagged the first beta for v2.0.0 tonight.  Please check out the new
> defaults!

Nice! sorry to arrive late at the party, but do you already have an
idea of how the distributions should handle the migration to the new
version? should we keep both 1.x and 2.x available or migrate to 2.x
as if it was "just" a new version (the latter is my preferred
solution)?

As for Debian, for now I will plan to keep 1.5.x in unstable, and
upload 2.x to experimental, but targetting to include 2.x in the next
stable release (we are still months away from the freeze, but time
flies :) )

let me know of any suggestions/concerns

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

From matthew.brett at gmail.com  Sat Jun 11 17:57:48 2016
From: matthew.brett at gmail.com (Matthew Brett)
Date: Sat, 11 Jun 2016 14:57:48 -0700
Subject: [Matplotlib-devel] Should we add manylinux wheels for previous
 versions of matplotlib?
In-Reply-To: <CAH6Pt5pC16j5LwxkDZ_3B1Qos3VFRiHsjD3dWnziKL1J8MXO1Q@mail.gmail.com>
References: <CAH6Pt5ruu5UFSG5yjyh=Vc=oBs6quGjZ8ifbjhiqSx4+EY=8Tw@mail.gmail.com>
 <CAPJVwBmCF-4ajoBfkq+tYBP-6RTiSM2gZVqDm68nH2Cj-FdXyw@mail.gmail.com>
 <CAH6Pt5q6S1kUknS1SA0a=xnTug8CKBds=NY1gf-UGLnuKMvJWg@mail.gmail.com>
 <CAH6Pt5pC16j5LwxkDZ_3B1Qos3VFRiHsjD3dWnziKL1J8MXO1Q@mail.gmail.com>
Message-ID: <CAH6Pt5pGdaGVNtX64W6dQc_=JURgaqvgq5=YbL82orxuvrebrA@mail.gmail.com>

Hi,

On Wed, Jun 1, 2016 at 10:39 AM, Matthew Brett <matthew.brett at gmail.com> wrote:
> On Mon, May 30, 2016 at 5:08 PM, Matthew Brett <matthew.brett at gmail.com> wrote:
>> On Mon, May 30, 2016 at 4:47 PM, Nathaniel Smith <njs at pobox.com> wrote:
>>> Just to check, I assume that these wheels would need a backport of:
>>>   https://github.com/matplotlib/matplotlib/pull/6442
>>> ?
>>
>> Yes, that's already done over at :
>> https://github.com/matthew-brett/manylinux-builds/blob/master/build_matplotlibs.sh
>
> To see what you'd get if we did upload the wheels, try:
>
> python -m pip install --upgrade pip  # Upgrade to latest pip
> pip install -f https://nipy.bic.berkeley.edu/manylinux matplotlib==1.4.0

Has anyone had a chance to test these wheels?  Any problems?

Cheers,

Matthew

From tcaswell at gmail.com  Sun Jun 12 19:03:39 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 12 Jun 2016 23:03:39 +0000
Subject: [Matplotlib-devel] [Matplotlib-announce] matplotlib v2.0.0b1
In-Reply-To: <CAB4XWXwhgm5zK8WU7VW2Jb6VDAkKk1mPX5O7snU3qv_8yKCBjw@mail.gmail.com>
References: <CAA48SF-Yir9CVDD7hnWd9tKom5usDd6LjjO00_TTt=Naj7LHkg@mail.gmail.com>
 <CAB4XWXwhgm5zK8WU7VW2Jb6VDAkKk1mPX5O7snU3qv_8yKCBjw@mail.gmail.com>
Message-ID: <CAA48SF-m+pd2SbKPq6gvw3f39EQ7_W7HOaCQNmJ1=fX5jwNQ5A@mail.gmail.com>

I think that distributions should just adopt 2.0 as the next version.
There are no more functionality breaks than in a typical minor release.

Tom

On Sat, Jun 11, 2016, 15:12 Sandro Tosi <morph at debian.org> wrote:

> On Tue, May 31, 2016 at 5:01 AM, Thomas Caswell <tcaswell at gmail.com>
> wrote:
> > We tagged the first beta for v2.0.0 tonight.  Please check out the new
> > defaults!
>
> Nice! sorry to arrive late at the party, but do you already have an
> idea of how the distributions should handle the migration to the new
> version? should we keep both 1.x and 2.x available or migrate to 2.x
> as if it was "just" a new version (the latter is my preferred
> solution)?
>
> As for Debian, for now I will plan to keep 1.5.x in unstable, and
> upload 2.x to experimental, but targetting to include 2.x in the next
> stable release (we are still months away from the freeze, but time
> flies :) )
>
> let me know of any suggestions/concerns
>
> Cheers,
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> G+: https://plus.google.com/u/0/+SandroTosi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160612/ad0ffa70/attachment.html>

From tcaswell at gmail.com  Wed Jun 22 21:50:35 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 23 Jun 2016 01:50:35 +0000
Subject: [Matplotlib-devel] macOS compatibility question
Message-ID: <CAA48SF_HN3W3nTjfpR0G51LQVeNuAg_3SH1m+qUSEW_kmDrToA@mail.gmail.com>

Folks,

We have a report that we have compatibility issues with macOS (aka the
newest version of OSX) https://github.com/matplotlib/matplotlib/issues/6613

Can anyone who has a mac + has a preview of the new OS follow up on this
bug report?

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/cf8ae677/attachment.html>

From flyxiaoyu at gmail.com  Wed Jun 22 22:43:33 2016
From: flyxiaoyu at gmail.com (Frank Yu)
Date: Thu, 23 Jun 2016 10:43:33 +0800
Subject: [Matplotlib-devel] fail to build matplotlib on smartos(like open
 solaris) system
Message-ID: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>

Hi there,

I am trying build matplotlib on smartos(like open solaris) system. but
failed with error. I am build the latest matplotlib. steps as below:


# git describe

v2.0.0b1-1699-g4b3350d

# python setup.py install

============================================================================

Edit setup.cfg to change the build options


BUILDING MATPLOTLIB

            matplotlib: yes [2.0.0b1+1699.g4b3350d]

                python: yes [2.7.11 (default, Jan 11 2016, 23:16:55)  [GCC

                        4.9.3]]

              platform: yes [sunos5]


REQUIRED DEPENDENCIES AND EXTENSIONS

                 numpy: yes [version 1.11.0]

                   six: yes [The installed version of six is 1.9.0 but a the

                        minimum required version is 1.10. pip/easy install

                        will attempt to install a newer version.]

              dateutil: yes [using dateutil version 2.4.0]

           functools32: yes [using functools32]

                  pytz: yes [using pytz version 2014.10]

                cycler: yes [using cycler version 0.10.0]

               tornado: yes [using tornado version 4.3]

             pyparsing: yes [using pyparsing version 2.0.2]

                libagg: yes [pkg-config information for 'libagg' could not

                        be found. Using local copy.]

              freetype: yes [version 2.5.5]

                   png: yes [version 1.6.17]

                 qhull: yes [pkg-config information for 'qhull' could not be

                        found. Using local copy.]


OPTIONAL SUBPACKAGES

           sample_data: yes [installing]

              toolkits: yes [installing]

                 tests: yes [using nose version 1.3.7 / mock is required to

                        run the matplotlib test suite. Please install it

                        with pip or your preferred tool to run the test

                        suite]

        toolkits_tests: yes [using nose version 1.3.7 / mock is required to

                        run the matplotlib test suite. Please install it

                        with pip or your preferred tool to run the test

                        suite]


OPTIONAL BACKEND EXTENSIONS

                macosx: no  [Mac OS-X only]

                qt5agg: no  [PySide2 not found; PyQt5 not found]

                qt4agg: no  [PySide not found; PyQt4 not found]

               gtk3agg: no  [Requires pygobject to be installed.]

             gtk3cairo: no  [Requires pygobject to be installed.]

                gtkagg: no  [Requires pygtk]

                 tkagg: yes [installing; run-time loading from Python Tcl /

                        Tk]

                 wxagg: no  [requires wxPython]

                   gtk: no  [Requires pygtk]

                   agg: yes [installing]

                 cairo: yes [installing, pycairo version 1.10.0]

             windowing: no  [Microsoft Windows only]


OPTIONAL LATEX DEPENDENCIES

                dvipng: no

           ghostscript: no

                 latex: no

               pdftops: no


OPTIONAL PACKAGE DATA

                  dlls: no  [skipping due to configuration]


running install

running bdist_egg

running egg_info

creating lib/matplotlib.egg-info

writing requirements to lib/matplotlib.egg-info/requires.txt

writing lib/matplotlib.egg-info/PKG-INFO

writing namespace_packages to lib/matplotlib.egg-info/namespace_packages.txt

writing top-level names to lib/matplotlib.egg-info/top_level.txt

writing dependency_links to lib/matplotlib.egg-info/dependency_links.txt

writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'

reading manifest file 'lib/matplotlib.egg-info/SOURCES.txt'

reading manifest template 'MANIFEST.in'

writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'

installing library code to build/bdist.solaris-2.11-i86pc.64bit/egg

running install_lib

running build_py

creating build

creating build/lib.solaris-2.11-i86pc.64bit-2.7

copying lib/pylab.py -> build/lib.solaris-2.11-i86pc.64bit-2.7

creating build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib

copying lib/matplotlib/_version.py ->
build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
?............

?running build_ext

building 'matplotlib.ft2font' extension

creating build/temp.solaris-2.11-i86pc.64bit-2.7

creating build/temp.solaris-2.11-i86pc.64bit-2.7/src

gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
-I/usr/include -I/opt/local/include -I/opt/local/include/db4
-I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
-DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
-I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
-DFREETYPE_BUILD_TYPE=system
-DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
-DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
-I/opt/local/lib/python2.7/site-packages/numpy/core/include
-I/opt/local/include/libpng16 -I/opt/local/include
-I/opt/local/include/freetype2 -I/usr/local/include -I.
-I/opt/local/include/python2.7 -c src/ft2font.cpp -o
build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font.o

gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
-I/usr/include -I/opt/local/include -I/opt/local/include/db4
-I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
-DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
-I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
-DFREETYPE_BUILD_TYPE=system
-DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
-DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
-I/opt/local/lib/python2.7/site-packages/numpy/core/include
-I/opt/local/include/libpng16 -I/opt/local/include
-I/opt/local/include/freetype2 -I/usr/local/include -I.
-I/opt/local/include/python2.7 -c src/ft2font_wrapper.cpp -o
build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font_wrapper.o

In file included from /opt/local/include/python2.7/Python.h:44:0,

                 from src/mplutils.h:21,

                 from src/ft2font_wrapper.cpp:1:

/usr/include/unistd.h:521:75: error: declaration of C function 'void
swab(const void*, void*, ssize_t)' conflicts with

In file included from /opt/local/include/python2.7/Python.h:42:0,

                 from src/mplutils.h:21,

                 from src/ft2font_wrapper.cpp:1:

/usr/include/stdlib.h:170:13: error: previous declaration 'void swab(const
char*, char*, ssize_t)' here

error: command 'gcc' failed with exit status 1

?The error is clear, swab was declared twice in both unistd.h and stdlib.h

# sed -n 519,522p /usr/include/unistd.h

#if defined(_XPG4)

/* __EXTENSIONS__ makes the SVID Third Edition prototype in stdlib.h
visible */

extern void swab(const void *_RESTRICT_KYWD, void *_RESTRICT_KYWD, ssize_t);

#endif /* defined(_XPG4) */

# sed -n 170p /usr/include/stdlib.h
extern void swab(const char *, char *, ssize_t);?


# sed -n 158,171p /usr/include/stdlib.h

#if (defined(__EXTENSIONS__) || \

(!defined(_STRICT_STDC__) && !defined(_POSIX_C_SOURCE))) && \

(!defined(_XOPEN_SOURCE) || (defined(_XPG3) && !defined(_XPG4)))

#ifndef _SSIZE_T

#define _SSIZE_T

#if defined(_LP64) || defined(_I32LPx)

typedef long ssize_t; /* size of something in bytes or -1 */

#else

typedef int ssize_t; /* (historical version) */

#endif

#endif /* !_SSIZE_T */


extern void swab(const char *, char *, ssize_t);

#endif /* defined(__EXTENSIONS__) || !defined(_STRICT_STDC) ... */


?I saw someone has asked this question, but can't get a proper answer.

?

-- 
Regards
Frank Yu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/9ee5c739/attachment-0001.html>

From tcaswell at gmail.com  Wed Jun 22 22:51:22 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 23 Jun 2016 02:51:22 +0000
Subject: [Matplotlib-devel] fail to build matplotlib on smartos(like
 open solaris) system
In-Reply-To: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
References: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
Message-ID: <CAA48SF8jaSdO+D59pkOta5rwVSYXiL8q8+-mu7B2W_fwRXQbAA@mail.gmail.com>

xref: https://github.com/matplotlib/matplotlib/issues/6528  which has a
more readable version of the error.

The question I asked in the other thread still stands, can you build _any_
c program that includes `Python.h`?

Tom

On Wed, Jun 22, 2016 at 10:43 PM Frank Yu <flyxiaoyu at gmail.com> wrote:

> Hi there,
>
> I am trying build matplotlib on smartos(like open solaris) system. but
> failed with error. I am build the latest matplotlib. steps as below:
>
>
> # git describe
>
> v2.0.0b1-1699-g4b3350d
>
> # python setup.py install
>
>
> ============================================================================
>
> Edit setup.cfg to change the build options
>
>
> BUILDING MATPLOTLIB
>
>             matplotlib: yes [2.0.0b1+1699.g4b3350d]
>
>                 python: yes [2.7.11 (default, Jan 11 2016, 23:16:55)  [GCC
>
>                         4.9.3]]
>
>               platform: yes [sunos5]
>
>
> REQUIRED DEPENDENCIES AND EXTENSIONS
>
>                  numpy: yes [version 1.11.0]
>
>                    six: yes [The installed version of six is 1.9.0 but a
> the
>
>                         minimum required version is 1.10. pip/easy install
>
>                         will attempt to install a newer version.]
>
>               dateutil: yes [using dateutil version 2.4.0]
>
>            functools32: yes [using functools32]
>
>                   pytz: yes [using pytz version 2014.10]
>
>                 cycler: yes [using cycler version 0.10.0]
>
>                tornado: yes [using tornado version 4.3]
>
>              pyparsing: yes [using pyparsing version 2.0.2]
>
>                 libagg: yes [pkg-config information for 'libagg' could not
>
>                         be found. Using local copy.]
>
>               freetype: yes [version 2.5.5]
>
>                    png: yes [version 1.6.17]
>
>                  qhull: yes [pkg-config information for 'qhull' could not
> be
>
>                         found. Using local copy.]
>
>
> OPTIONAL SUBPACKAGES
>
>            sample_data: yes [installing]
>
>               toolkits: yes [installing]
>
>                  tests: yes [using nose version 1.3.7 / mock is required to
>
>                         run the matplotlib test suite. Please install it
>
>                         with pip or your preferred tool to run the test
>
>                         suite]
>
>         toolkits_tests: yes [using nose version 1.3.7 / mock is required to
>
>                         run the matplotlib test suite. Please install it
>
>                         with pip or your preferred tool to run the test
>
>                         suite]
>
>
> OPTIONAL BACKEND EXTENSIONS
>
>                 macosx: no  [Mac OS-X only]
>
>                 qt5agg: no  [PySide2 not found; PyQt5 not found]
>
>                 qt4agg: no  [PySide not found; PyQt4 not found]
>
>                gtk3agg: no  [Requires pygobject to be installed.]
>
>              gtk3cairo: no  [Requires pygobject to be installed.]
>
>                 gtkagg: no  [Requires pygtk]
>
>                  tkagg: yes [installing; run-time loading from Python Tcl /
>
>                         Tk]
>
>                  wxagg: no  [requires wxPython]
>
>                    gtk: no  [Requires pygtk]
>
>                    agg: yes [installing]
>
>                  cairo: yes [installing, pycairo version 1.10.0]
>
>              windowing: no  [Microsoft Windows only]
>
>
> OPTIONAL LATEX DEPENDENCIES
>
>                 dvipng: no
>
>            ghostscript: no
>
>                  latex: no
>
>                pdftops: no
>
>
> OPTIONAL PACKAGE DATA
>
>                   dlls: no  [skipping due to configuration]
>
>
> running install
>
> running bdist_egg
>
> running egg_info
>
> creating lib/matplotlib.egg-info
>
> writing requirements to lib/matplotlib.egg-info/requires.txt
>
> writing lib/matplotlib.egg-info/PKG-INFO
>
> writing namespace_packages to
> lib/matplotlib.egg-info/namespace_packages.txt
>
> writing top-level names to lib/matplotlib.egg-info/top_level.txt
>
> writing dependency_links to lib/matplotlib.egg-info/dependency_links.txt
>
> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>
> reading manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>
> reading manifest template 'MANIFEST.in'
>
> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>
> installing library code to build/bdist.solaris-2.11-i86pc.64bit/egg
>
> running install_lib
>
> running build_py
>
> creating build
>
> creating build/lib.solaris-2.11-i86pc.64bit-2.7
>
> copying lib/pylab.py -> build/lib.solaris-2.11-i86pc.64bit-2.7
>
> creating build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
>
> copying lib/matplotlib/_version.py ->
> build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
> ?............
>
> ?running build_ext
>
> building 'matplotlib.ft2font' extension
>
> creating build/temp.solaris-2.11-i86pc.64bit-2.7
>
> creating build/temp.solaris-2.11-i86pc.64bit-2.7/src
>
> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
> -I/usr/include -I/opt/local/include -I/opt/local/include/db4
> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
> -DFREETYPE_BUILD_TYPE=system
> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
> -I/opt/local/include/libpng16 -I/opt/local/include
> -I/opt/local/include/freetype2 -I/usr/local/include -I.
> -I/opt/local/include/python2.7 -c src/ft2font.cpp -o
> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font.o
>
> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
> -I/usr/include -I/opt/local/include -I/opt/local/include/db4
> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
> -DFREETYPE_BUILD_TYPE=system
> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
> -I/opt/local/include/libpng16 -I/opt/local/include
> -I/opt/local/include/freetype2 -I/usr/local/include -I.
> -I/opt/local/include/python2.7 -c src/ft2font_wrapper.cpp -o
> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font_wrapper.o
>
> In file included from /opt/local/include/python2.7/Python.h:44:0,
>
>                  from src/mplutils.h:21,
>
>                  from src/ft2font_wrapper.cpp:1:
>
> /usr/include/unistd.h:521:75: error: declaration of C function 'void
> swab(const void*, void*, ssize_t)' conflicts with
>
> In file included from /opt/local/include/python2.7/Python.h:42:0,
>
>                  from src/mplutils.h:21,
>
>                  from src/ft2font_wrapper.cpp:1:
>
> /usr/include/stdlib.h:170:13: error: previous declaration 'void swab(const
> char*, char*, ssize_t)' here
>
> error: command 'gcc' failed with exit status 1
>
> ?The error is clear, swab was declared twice in both unistd.h and stdlib.h
>
> # sed -n 519,522p /usr/include/unistd.h
>
> #if defined(_XPG4)
>
> /* __EXTENSIONS__ makes the SVID Third Edition prototype in stdlib.h
> visible */
>
> extern void swab(const void *_RESTRICT_KYWD, void *_RESTRICT_KYWD,
> ssize_t);
>
> #endif /* defined(_XPG4) */
>
> # sed -n 170p /usr/include/stdlib.h
> extern void swab(const char *, char *, ssize_t);?
>
>
> # sed -n 158,171p /usr/include/stdlib.h
>
> #if (defined(__EXTENSIONS__) || \
>
> (!defined(_STRICT_STDC__) && !defined(_POSIX_C_SOURCE))) && \
>
> (!defined(_XOPEN_SOURCE) || (defined(_XPG3) && !defined(_XPG4)))
>
> #ifndef _SSIZE_T
>
> #define _SSIZE_T
>
> #if defined(_LP64) || defined(_I32LPx)
>
> typedef long ssize_t; /* size of something in bytes or -1 */
>
> #else
>
> typedef int ssize_t; /* (historical version) */
>
> #endif
>
> #endif /* !_SSIZE_T */
>
>
> extern void swab(const char *, char *, ssize_t);
>
> #endif /* defined(__EXTENSIONS__) || !defined(_STRICT_STDC) ... */
>
>
> ?I saw someone has asked this question, but can't get a proper answer.
>
> ?
>
> --
> Regards
> Frank Yu
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/0ca7ca1a/attachment-0001.html>

From njs at pobox.com  Wed Jun 22 22:58:37 2016
From: njs at pobox.com (Nathaniel Smith)
Date: Wed, 22 Jun 2016 19:58:37 -0700
Subject: [Matplotlib-devel] fail to build matplotlib on smartos(like
 open solaris) system
In-Reply-To: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
References: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
Message-ID: <CAPJVwBmNKgDPpxbqf33-QkJVFESZZV3Lg-BVAv7wDcL4TxJHfg@mail.gmail.com>

On Jun 22, 2016 7:43 PM, "Frank Yu" <flyxiaoyu at gmail.com> wrote:
[...]
> ?The error is clear, swab was declared twice in both unistd.h and stdlib.h

I agree with this interpretation of the error messages.

I don't think matplotlib can do much about this, though -- those are both
standard files that are part of your operating system (or maybe compiler),
and they're broken. This means that your c compiler can't actually compile
ordinary c programs. It sounds like you should be filing a bug with either
your OS maintainers or whoever supplied the compiler.

-n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160622/9f6203c9/attachment.html>

From flyxiaoyu at gmail.com  Wed Jun 22 23:07:40 2016
From: flyxiaoyu at gmail.com (Frank Yu)
Date: Thu, 23 Jun 2016 11:07:40 +0800
Subject: [Matplotlib-devel] fail to build matplotlib on smartos(like
 open solaris) system
In-Reply-To: <CAA48SF8jaSdO+D59pkOta5rwVSYXiL8q8+-mu7B2W_fwRXQbAA@mail.gmail.com>
References: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
 <CAA48SF8jaSdO+D59pkOta5rwVSYXiL8q8+-mu7B2W_fwRXQbAA@mail.gmail.com>
Message-ID: <CAKXD-H45_V6AVPZ_YFe6A+MS7Se3tjgHw4pD7nz42u343i=vWw@mail.gmail.com>

Hi Thomas,

Sorry for ask again, and yes, I can build c program which include
'Python.h'.
I close the issues 6528 because I install it from
https://pkgsrc.joyent.com/packages/SmartOS/2015Q2/x86_64/All/py27-matplotlib-1.3.1nb1.tgz.
but it doesn't work well.  So I try to build from source to see what
happened.


2016-06-23 10:51 GMT+08:00 Thomas Caswell <tcaswell at gmail.com>:

> xref: https://github.com/matplotlib/matplotlib/issues/6528  which has a
> more readable version of the error.
>
> The question I asked in the other thread still stands, can you build _any_
> c program that includes `Python.h`?
>
> Tom
>
> On Wed, Jun 22, 2016 at 10:43 PM Frank Yu <flyxiaoyu at gmail.com> wrote:
>
>> Hi there,
>>
>> I am trying build matplotlib on smartos(like open solaris) system. but
>> failed with error. I am build the latest matplotlib. steps as below:
>>
>>
>> # git describe
>>
>> v2.0.0b1-1699-g4b3350d
>>
>> # python setup.py install
>>
>>
>> ============================================================================
>>
>> Edit setup.cfg to change the build options
>>
>>
>> BUILDING MATPLOTLIB
>>
>>             matplotlib: yes [2.0.0b1+1699.g4b3350d]
>>
>>                 python: yes [2.7.11 (default, Jan 11 2016, 23:16:55)  [GCC
>>
>>                         4.9.3]]
>>
>>               platform: yes [sunos5]
>>
>>
>> REQUIRED DEPENDENCIES AND EXTENSIONS
>>
>>                  numpy: yes [version 1.11.0]
>>
>>                    six: yes [The installed version of six is 1.9.0 but a
>> the
>>
>>                         minimum required version is 1.10. pip/easy install
>>
>>                         will attempt to install a newer version.]
>>
>>               dateutil: yes [using dateutil version 2.4.0]
>>
>>            functools32: yes [using functools32]
>>
>>                   pytz: yes [using pytz version 2014.10]
>>
>>                 cycler: yes [using cycler version 0.10.0]
>>
>>                tornado: yes [using tornado version 4.3]
>>
>>              pyparsing: yes [using pyparsing version 2.0.2]
>>
>>                 libagg: yes [pkg-config information for 'libagg' could not
>>
>>                         be found. Using local copy.]
>>
>>               freetype: yes [version 2.5.5]
>>
>>                    png: yes [version 1.6.17]
>>
>>                  qhull: yes [pkg-config information for 'qhull' could not
>> be
>>
>>                         found. Using local copy.]
>>
>>
>> OPTIONAL SUBPACKAGES
>>
>>            sample_data: yes [installing]
>>
>>               toolkits: yes [installing]
>>
>>                  tests: yes [using nose version 1.3.7 / mock is required
>> to
>>
>>                         run the matplotlib test suite. Please install it
>>
>>                         with pip or your preferred tool to run the test
>>
>>                         suite]
>>
>>         toolkits_tests: yes [using nose version 1.3.7 / mock is required
>> to
>>
>>                         run the matplotlib test suite. Please install it
>>
>>                         with pip or your preferred tool to run the test
>>
>>                         suite]
>>
>>
>> OPTIONAL BACKEND EXTENSIONS
>>
>>                 macosx: no  [Mac OS-X only]
>>
>>                 qt5agg: no  [PySide2 not found; PyQt5 not found]
>>
>>                 qt4agg: no  [PySide not found; PyQt4 not found]
>>
>>                gtk3agg: no  [Requires pygobject to be installed.]
>>
>>              gtk3cairo: no  [Requires pygobject to be installed.]
>>
>>                 gtkagg: no  [Requires pygtk]
>>
>>                  tkagg: yes [installing; run-time loading from Python Tcl
>> /
>>
>>                         Tk]
>>
>>                  wxagg: no  [requires wxPython]
>>
>>                    gtk: no  [Requires pygtk]
>>
>>                    agg: yes [installing]
>>
>>                  cairo: yes [installing, pycairo version 1.10.0]
>>
>>              windowing: no  [Microsoft Windows only]
>>
>>
>> OPTIONAL LATEX DEPENDENCIES
>>
>>                 dvipng: no
>>
>>            ghostscript: no
>>
>>                  latex: no
>>
>>                pdftops: no
>>
>>
>> OPTIONAL PACKAGE DATA
>>
>>                   dlls: no  [skipping due to configuration]
>>
>>
>> running install
>>
>> running bdist_egg
>>
>> running egg_info
>>
>> creating lib/matplotlib.egg-info
>>
>> writing requirements to lib/matplotlib.egg-info/requires.txt
>>
>> writing lib/matplotlib.egg-info/PKG-INFO
>>
>> writing namespace_packages to
>> lib/matplotlib.egg-info/namespace_packages.txt
>>
>> writing top-level names to lib/matplotlib.egg-info/top_level.txt
>>
>> writing dependency_links to lib/matplotlib.egg-info/dependency_links.txt
>>
>> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>
>> reading manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>
>> reading manifest template 'MANIFEST.in'
>>
>> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>
>> installing library code to build/bdist.solaris-2.11-i86pc.64bit/egg
>>
>> running install_lib
>>
>> running build_py
>>
>> creating build
>>
>> creating build/lib.solaris-2.11-i86pc.64bit-2.7
>>
>> copying lib/pylab.py -> build/lib.solaris-2.11-i86pc.64bit-2.7
>>
>> creating build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
>>
>> copying lib/matplotlib/_version.py ->
>> build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
>> ?............
>>
>> ?running build_ext
>>
>> building 'matplotlib.ft2font' extension
>>
>> creating build/temp.solaris-2.11-i86pc.64bit-2.7
>>
>> creating build/temp.solaris-2.11-i86pc.64bit-2.7/src
>>
>> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
>> -I/usr/include -I/opt/local/include -I/opt/local/include/db4
>> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
>> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
>> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
>> -DFREETYPE_BUILD_TYPE=system
>> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
>> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
>> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
>> -I/opt/local/include/libpng16 -I/opt/local/include
>> -I/opt/local/include/freetype2 -I/usr/local/include -I.
>> -I/opt/local/include/python2.7 -c src/ft2font.cpp -o
>> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font.o
>>
>> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H -pthread
>> -I/usr/include -I/opt/local/include -I/opt/local/include/db4
>> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
>> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
>> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
>> -DFREETYPE_BUILD_TYPE=system
>> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
>> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
>> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
>> -I/opt/local/include/libpng16 -I/opt/local/include
>> -I/opt/local/include/freetype2 -I/usr/local/include -I.
>> -I/opt/local/include/python2.7 -c src/ft2font_wrapper.cpp -o
>> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font_wrapper.o
>>
>> In file included from /opt/local/include/python2.7/Python.h:44:0,
>>
>>                  from src/mplutils.h:21,
>>
>>                  from src/ft2font_wrapper.cpp:1:
>>
>> /usr/include/unistd.h:521:75: error: declaration of C function 'void
>> swab(const void*, void*, ssize_t)' conflicts with
>>
>> In file included from /opt/local/include/python2.7/Python.h:42:0,
>>
>>                  from src/mplutils.h:21,
>>
>>                  from src/ft2font_wrapper.cpp:1:
>>
>> /usr/include/stdlib.h:170:13: error: previous declaration 'void
>> swab(const char*, char*, ssize_t)' here
>>
>> error: command 'gcc' failed with exit status 1
>>
>> ?The error is clear, swab was declared twice in both unistd.h and stdlib.h
>>
>> # sed -n 519,522p /usr/include/unistd.h
>>
>> #if defined(_XPG4)
>>
>> /* __EXTENSIONS__ makes the SVID Third Edition prototype in stdlib.h
>> visible */
>>
>> extern void swab(const void *_RESTRICT_KYWD, void *_RESTRICT_KYWD,
>> ssize_t);
>>
>> #endif /* defined(_XPG4) */
>>
>> # sed -n 170p /usr/include/stdlib.h
>> extern void swab(const char *, char *, ssize_t);?
>>
>>
>> # sed -n 158,171p /usr/include/stdlib.h
>>
>> #if (defined(__EXTENSIONS__) || \
>>
>> (!defined(_STRICT_STDC__) && !defined(_POSIX_C_SOURCE))) && \
>>
>> (!defined(_XOPEN_SOURCE) || (defined(_XPG3) && !defined(_XPG4)))
>>
>> #ifndef _SSIZE_T
>>
>> #define _SSIZE_T
>>
>> #if defined(_LP64) || defined(_I32LPx)
>>
>> typedef long ssize_t; /* size of something in bytes or -1 */
>>
>> #else
>>
>> typedef int ssize_t; /* (historical version) */
>>
>> #endif
>>
>> #endif /* !_SSIZE_T */
>>
>>
>> extern void swab(const char *, char *, ssize_t);
>>
>> #endif /* defined(__EXTENSIONS__) || !defined(_STRICT_STDC) ... */
>>
>>
>> ?I saw someone has asked this question, but can't get a proper answer.
>>
>> ?
>>
>> --
>> Regards
>> Frank Yu
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>


-- 
Regards
Frank Yu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/9c1936b1/attachment-0001.html>

From flyxiaoyu at gmail.com  Thu Jun 23 00:47:54 2016
From: flyxiaoyu at gmail.com (Frank Yu)
Date: Thu, 23 Jun 2016 12:47:54 +0800
Subject: [Matplotlib-devel] fail to build matplotlib on smartos(like
 open solaris) system
In-Reply-To: <CAKXD-H45_V6AVPZ_YFe6A+MS7Se3tjgHw4pD7nz42u343i=vWw@mail.gmail.com>
References: <CAKXD-H6oVu8_9vnKT2vdRdquecH9MzVZ91Z==uCwqLy7kOah+A@mail.gmail.com>
 <CAA48SF8jaSdO+D59pkOta5rwVSYXiL8q8+-mu7B2W_fwRXQbAA@mail.gmail.com>
 <CAKXD-H45_V6AVPZ_YFe6A+MS7Se3tjgHw4pD7nz42u343i=vWw@mail.gmail.com>
Message-ID: <CAKXD-H7i+7fi-J-+nAQyWMDVnZE5GoQdLNG7_gNLPHeAbcDPkg@mail.gmail.com>

Hi,

I have install matplotlib after a small tweak. but when I try to run test,
I met core dumped.

# pip list|grep matplotlib

matplotlib (2.0.0b1+1704.gf8ea2c5.dirty)

# python tests.py

/opt/local/lib/python2.7/site-packages/matplotlib-2.0.0b1+1704.gf8ea2c5.dirty-py2.7-solaris-2.11-i86pc.64bit.egg/matplotlib/__init__.py:1563:
UserWarning: matplotlib is not built with the correct FreeType version to
run tests.  Set local_freetype=True in setup.cfg and rebuild. Expect many
image comparison failures below.

  "matplotlib is not built with the correct FreeType version to run "

......KKKKKK.KK....Abort (core dumped)

What I did is:

# git diff

diff --git a/src/mplutils.h b/src/mplutils.h

index 8d4ae70..0cc9644 100644

--- a/src/mplutils.h

+++ b/src/mplutils.h

@@ -18,6 +18,12 @@ typedef unsigned __int8   uint8_t;

 #    undef _XOPEN_SOURCE

 #endif



+#if defined(__sun) || defined(sun)

+#if defined(_XPG4)

+#undef _XPG4

+#endif

+#endif

+

 #include <Python.h>



 #if PY_MAJOR_VERSION >= 3

diff --git a/src/numpy_cpp.h b/src/numpy_cpp.h

index 887ffe4..af18b5c 100644

--- a/src/numpy_cpp.h

+++ b/src/numpy_cpp.h

@@ -25,6 +25,12 @@

 #    undef _XOPEN_SOURCE

 #endif



+#if defined(__sun) || defined(sun)

+#if defined(_XPG4)

+#undef _XPG4

+#endif

+#endif

+

 #include <Python.h>

 #include <numpy/ndarrayobject.h>



2016-06-23 11:07 GMT+08:00 Frank Yu <flyxiaoyu at gmail.com>:

> Hi Thomas,
>
> Sorry for ask again, and yes, I can build c program which include
> 'Python.h'.
> I close the issues 6528 because I install it from
> https://pkgsrc.joyent.com/packages/SmartOS/2015Q2/x86_64/All/py27-matplotlib-1.3.1nb1.tgz.
> but it doesn't work well.  So I try to build from source to see what
> happened.
>
>
> 2016-06-23 10:51 GMT+08:00 Thomas Caswell <tcaswell at gmail.com>:
>
>> xref: https://github.com/matplotlib/matplotlib/issues/6528  which has a
>> more readable version of the error.
>>
>> The question I asked in the other thread still stands, can you build
>> _any_ c program that includes `Python.h`?
>>
>> Tom
>>
>> On Wed, Jun 22, 2016 at 10:43 PM Frank Yu <flyxiaoyu at gmail.com> wrote:
>>
>>> Hi there,
>>>
>>> I am trying build matplotlib on smartos(like open solaris) system. but
>>> failed with error. I am build the latest matplotlib. steps as below:
>>>
>>>
>>> # git describe
>>>
>>> v2.0.0b1-1699-g4b3350d
>>>
>>> # python setup.py install
>>>
>>>
>>> ============================================================================
>>>
>>> Edit setup.cfg to change the build options
>>>
>>>
>>> BUILDING MATPLOTLIB
>>>
>>>             matplotlib: yes [2.0.0b1+1699.g4b3350d]
>>>
>>>                 python: yes [2.7.11 (default, Jan 11 2016, 23:16:55)
>>> [GCC
>>>
>>>                         4.9.3]]
>>>
>>>               platform: yes [sunos5]
>>>
>>>
>>> REQUIRED DEPENDENCIES AND EXTENSIONS
>>>
>>>                  numpy: yes [version 1.11.0]
>>>
>>>                    six: yes [The installed version of six is 1.9.0 but a
>>> the
>>>
>>>                         minimum required version is 1.10. pip/easy
>>> install
>>>
>>>                         will attempt to install a newer version.]
>>>
>>>               dateutil: yes [using dateutil version 2.4.0]
>>>
>>>            functools32: yes [using functools32]
>>>
>>>                   pytz: yes [using pytz version 2014.10]
>>>
>>>                 cycler: yes [using cycler version 0.10.0]
>>>
>>>                tornado: yes [using tornado version 4.3]
>>>
>>>              pyparsing: yes [using pyparsing version 2.0.2]
>>>
>>>                 libagg: yes [pkg-config information for 'libagg' could
>>> not
>>>
>>>                         be found. Using local copy.]
>>>
>>>               freetype: yes [version 2.5.5]
>>>
>>>                    png: yes [version 1.6.17]
>>>
>>>                  qhull: yes [pkg-config information for 'qhull' could
>>> not be
>>>
>>>                         found. Using local copy.]
>>>
>>>
>>> OPTIONAL SUBPACKAGES
>>>
>>>            sample_data: yes [installing]
>>>
>>>               toolkits: yes [installing]
>>>
>>>                  tests: yes [using nose version 1.3.7 / mock is required
>>> to
>>>
>>>                         run the matplotlib test suite. Please install it
>>>
>>>                         with pip or your preferred tool to run the test
>>>
>>>                         suite]
>>>
>>>         toolkits_tests: yes [using nose version 1.3.7 / mock is required
>>> to
>>>
>>>                         run the matplotlib test suite. Please install it
>>>
>>>                         with pip or your preferred tool to run the test
>>>
>>>                         suite]
>>>
>>>
>>> OPTIONAL BACKEND EXTENSIONS
>>>
>>>                 macosx: no  [Mac OS-X only]
>>>
>>>                 qt5agg: no  [PySide2 not found; PyQt5 not found]
>>>
>>>                 qt4agg: no  [PySide not found; PyQt4 not found]
>>>
>>>                gtk3agg: no  [Requires pygobject to be installed.]
>>>
>>>              gtk3cairo: no  [Requires pygobject to be installed.]
>>>
>>>                 gtkagg: no  [Requires pygtk]
>>>
>>>                  tkagg: yes [installing; run-time loading from Python
>>> Tcl /
>>>
>>>                         Tk]
>>>
>>>                  wxagg: no  [requires wxPython]
>>>
>>>                    gtk: no  [Requires pygtk]
>>>
>>>                    agg: yes [installing]
>>>
>>>                  cairo: yes [installing, pycairo version 1.10.0]
>>>
>>>              windowing: no  [Microsoft Windows only]
>>>
>>>
>>> OPTIONAL LATEX DEPENDENCIES
>>>
>>>                 dvipng: no
>>>
>>>            ghostscript: no
>>>
>>>                  latex: no
>>>
>>>                pdftops: no
>>>
>>>
>>> OPTIONAL PACKAGE DATA
>>>
>>>                   dlls: no  [skipping due to configuration]
>>>
>>>
>>> running install
>>>
>>> running bdist_egg
>>>
>>> running egg_info
>>>
>>> creating lib/matplotlib.egg-info
>>>
>>> writing requirements to lib/matplotlib.egg-info/requires.txt
>>>
>>> writing lib/matplotlib.egg-info/PKG-INFO
>>>
>>> writing namespace_packages to
>>> lib/matplotlib.egg-info/namespace_packages.txt
>>>
>>> writing top-level names to lib/matplotlib.egg-info/top_level.txt
>>>
>>> writing dependency_links to lib/matplotlib.egg-info/dependency_links.txt
>>>
>>> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>>
>>> reading manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>>
>>> reading manifest template 'MANIFEST.in'
>>>
>>> writing manifest file 'lib/matplotlib.egg-info/SOURCES.txt'
>>>
>>> installing library code to build/bdist.solaris-2.11-i86pc.64bit/egg
>>>
>>> running install_lib
>>>
>>> running build_py
>>>
>>> creating build
>>>
>>> creating build/lib.solaris-2.11-i86pc.64bit-2.7
>>>
>>> copying lib/pylab.py -> build/lib.solaris-2.11-i86pc.64bit-2.7
>>>
>>> creating build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
>>>
>>> copying lib/matplotlib/_version.py ->
>>> build/lib.solaris-2.11-i86pc.64bit-2.7/matplotlib
>>> ?............
>>>
>>> ?running build_ext
>>>
>>> building 'matplotlib.ft2font' extension
>>>
>>> creating build/temp.solaris-2.11-i86pc.64bit-2.7
>>>
>>> creating build/temp.solaris-2.11-i86pc.64bit-2.7/src
>>>
>>> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H
>>> -pthread -I/usr/include -I/opt/local/include -I/opt/local/include/db4
>>> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
>>> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
>>> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
>>> -DFREETYPE_BUILD_TYPE=system
>>> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
>>> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
>>> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
>>> -I/opt/local/include/libpng16 -I/opt/local/include
>>> -I/opt/local/include/freetype2 -I/usr/local/include -I.
>>> -I/opt/local/include/python2.7 -c src/ft2font.cpp -o
>>> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font.o
>>>
>>> gcc -fno-strict-aliasing -O2 -pipe -O2 -gdwarf-2 -DHAVE_DB_185_H
>>> -pthread -I/usr/include -I/opt/local/include -I/opt/local/include/db4
>>> -I/opt/local/include/ncurses -DNDEBUG -O2 -pipe -O2 -gdwarf-2
>>> -DHAVE_DB_185_H -pthread -I/usr/include -I/opt/local/include
>>> -I/opt/local/include/db4 -I/opt/local/include/ncurses -fPIC
>>> -DFREETYPE_BUILD_TYPE=system
>>> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_ft2font_ARRAY_API
>>> -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION
>>> -I/opt/local/lib/python2.7/site-packages/numpy/core/include
>>> -I/opt/local/include/libpng16 -I/opt/local/include
>>> -I/opt/local/include/freetype2 -I/usr/local/include -I.
>>> -I/opt/local/include/python2.7 -c src/ft2font_wrapper.cpp -o
>>> build/temp.solaris-2.11-i86pc.64bit-2.7/src/ft2font_wrapper.o
>>>
>>> In file included from /opt/local/include/python2.7/Python.h:44:0,
>>>
>>>                  from src/mplutils.h:21,
>>>
>>>                  from src/ft2font_wrapper.cpp:1:
>>>
>>> /usr/include/unistd.h:521:75: error: declaration of C function 'void
>>> swab(const void*, void*, ssize_t)' conflicts with
>>>
>>> In file included from /opt/local/include/python2.7/Python.h:42:0,
>>>
>>>                  from src/mplutils.h:21,
>>>
>>>                  from src/ft2font_wrapper.cpp:1:
>>>
>>> /usr/include/stdlib.h:170:13: error: previous declaration 'void
>>> swab(const char*, char*, ssize_t)' here
>>>
>>> error: command 'gcc' failed with exit status 1
>>>
>>> ?The error is clear, swab was declared twice in both unistd.h and
>>> stdlib.h
>>>
>>> # sed -n 519,522p /usr/include/unistd.h
>>>
>>> #if defined(_XPG4)
>>>
>>> /* __EXTENSIONS__ makes the SVID Third Edition prototype in stdlib.h
>>> visible */
>>>
>>> extern void swab(const void *_RESTRICT_KYWD, void *_RESTRICT_KYWD,
>>> ssize_t);
>>>
>>> #endif /* defined(_XPG4) */
>>>
>>> # sed -n 170p /usr/include/stdlib.h
>>> extern void swab(const char *, char *, ssize_t);?
>>>
>>>
>>> # sed -n 158,171p /usr/include/stdlib.h
>>>
>>> #if (defined(__EXTENSIONS__) || \
>>>
>>> (!defined(_STRICT_STDC__) && !defined(_POSIX_C_SOURCE))) && \
>>>
>>> (!defined(_XOPEN_SOURCE) || (defined(_XPG3) && !defined(_XPG4)))
>>>
>>> #ifndef _SSIZE_T
>>>
>>> #define _SSIZE_T
>>>
>>> #if defined(_LP64) || defined(_I32LPx)
>>>
>>> typedef long ssize_t; /* size of something in bytes or -1 */
>>>
>>> #else
>>>
>>> typedef int ssize_t; /* (historical version) */
>>>
>>> #endif
>>>
>>> #endif /* !_SSIZE_T */
>>>
>>>
>>> extern void swab(const char *, char *, ssize_t);
>>>
>>> #endif /* defined(__EXTENSIONS__) || !defined(_STRICT_STDC) ... */
>>>
>>>
>>> ?I saw someone has asked this question, but can't get a proper answer.
>>>
>>> ?
>>>
>>> --
>>> Regards
>>> Frank Yu
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>
>
>
> --
> Regards
> Frank Yu
>



-- 
Regards
Frank Yu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/ee93891c/attachment-0001.html>

From efiring at hawaii.edu  Thu Jun 23 02:24:53 2016
From: efiring at hawaii.edu (Eric Firing)
Date: Wed, 22 Jun 2016 20:24:53 -1000
Subject: [Matplotlib-devel] macOS compatibility question
In-Reply-To: <CAA48SF_HN3W3nTjfpR0G51LQVeNuAg_3SH1m+qUSEW_kmDrToA@mail.gmail.com>
References: <CAA48SF_HN3W3nTjfpR0G51LQVeNuAg_3SH1m+qUSEW_kmDrToA@mail.gmail.com>
Message-ID: <e5cb1fea-9fce-8363-ebaa-5e7e6b383579@hawaii.edu>

On 2016/06/22 3:50 PM, Thomas Caswell wrote:
> Folks,
>
> We have a report that we have compatibility issues with macOS (aka the
> newest version of OSX) https://github.com/matplotlib/matplotlib/issues/6613
>
> Can anyone who has a mac + has a preview of the new OS follow up on this
> bug report?
>
> Tom

I'm still on 10.9.5.

Eric


From jenshnielsen at gmail.com  Thu Jun 23 04:52:47 2016
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Thu, 23 Jun 2016 08:52:47 +0000
Subject: [Matplotlib-devel] macOS compatibility question
In-Reply-To: <e5cb1fea-9fce-8363-ebaa-5e7e6b383579@hawaii.edu>
References: <CAA48SF_HN3W3nTjfpR0G51LQVeNuAg_3SH1m+qUSEW_kmDrToA@mail.gmail.com>
 <e5cb1fea-9fce-8363-ebaa-5e7e6b383579@hawaii.edu>
Message-ID: <CAM-Pw00HryxctKSVR0Go7EdU01OPrpns2W8X0Ur0FsHhu5ZVPA@mail.gmail.com>

I am not willing to upgrade to a beta release of OSX on my main working
machine and unfortunately running OSX in a VM is not that easy especially
for early betas. That being said I am happy to apply the suggested change
locally on my 10.11 box and try it out to verify that it doesn't break any
thing on the present release. I think Travis has Xcode 8 betas so we could
try to run it there too (but we have no tests of the osx backend as it is)

Jens




On Thu, 23 Jun 2016 at 07:25 Eric Firing <efiring at hawaii.edu> wrote:

> On 2016/06/22 3:50 PM, Thomas Caswell wrote:
> > Folks,
> >
> > We have a report that we have compatibility issues with macOS (aka the
> > newest version of OSX)
> https://github.com/matplotlib/matplotlib/issues/6613
> >
> > Can anyone who has a mac + has a preview of the new OS follow up on this
> > bug report?
> >
> > Tom
>
> I'm still on 10.9.5.
>
> Eric
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160623/34bbb4fe/attachment.html>

From matthew.brett at gmail.com  Sun Jun 26 17:43:49 2016
From: matthew.brett at gmail.com (Matthew Brett)
Date: Sun, 26 Jun 2016 14:43:49 -0700
Subject: [Matplotlib-devel] How's progress with 1.5.2?
Message-ID: <CAH6Pt5pdfaw-Ng=K3OH2p6PYt+aQuLk55da3ckdG+sGO5gBG2Q@mail.gmail.com>

Hi,

A friend of mine was just asking about 1.5.2 - he needs some fixes
that landed after 1.5.1 for his own software package.

What's the current ETA?  Any tasks we less-experienced matplotlibbers
can help with?

Cheers,

Matthew

From tcaswell at gmail.com  Mon Jun 27 21:16:19 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 28 Jun 2016 01:16:19 +0000
Subject: [Matplotlib-devel] How's progress with 1.5.2?
In-Reply-To: <CAH6Pt5pdfaw-Ng=K3OH2p6PYt+aQuLk55da3ckdG+sGO5gBG2Q@mail.gmail.com>
References: <CAH6Pt5pdfaw-Ng=K3OH2p6PYt+aQuLk55da3ckdG+sGO5gBG2Q@mail.gmail.com>
Message-ID: <CAA48SF8Botbocthnngn8qh4bhwgm4ZRbs7iNreqqp=d6ZSzc_w@mail.gmail.com>

The bottle neck is me doing the final release.  My current plan is to do
that July 2.

Tom

On Sun, Jun 26, 2016 at 5:44 PM Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> A friend of mine was just asking about 1.5.2 - he needs some fixes
> that landed after 1.5.1 for his own software package.
>
> What's the current ETA?  Any tasks we less-experienced matplotlibbers
> can help with?
>
> Cheers,
>
> Matthew
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160628/9785f8ca/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Tue Jun 28 05:02:14 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Tue, 28 Jun 2016 09:02:14 +0000 (UTC)
Subject: [Matplotlib-devel] How's progress with 1.5.2?
In-Reply-To: <CAA48SF8Botbocthnngn8qh4bhwgm4ZRbs7iNreqqp=d6ZSzc_w@mail.gmail.com>
References: <CAH6Pt5pdfaw-Ng=K3OH2p6PYt+aQuLk55da3ckdG+sGO5gBG2Q@mail.gmail.com>
 <CAA48SF8Botbocthnngn8qh4bhwgm4ZRbs7iNreqqp=d6ZSzc_w@mail.gmail.com>
Message-ID: <772873849.4352871.1467104534727.JavaMail.yahoo@mail.yahoo.com>

I still see 1 PR and 2 issues open for 1.5.2...
A problem?

      From: Thomas Caswell <tcaswell at gmail.com>
 To: Matthew Brett <matthew.brett at gmail.com>; matplotlib development list <matplotlib-devel at python.org> 
 Sent: Tuesday, 28 June 2016, 3:16
 Subject: Re: [Matplotlib-devel] How's progress with 1.5.2?
   
The bottle neck is me doing the final release.? My current plan is to do that July 2.
Tom
On Sun, Jun 26, 2016 at 5:44 PM Matthew Brett <matthew.brett at gmail.com> wrote:

Hi,

A friend of mine was just asking about 1.5.2 - he needs some fixes
that landed after 1.5.1 for his own software package.

What's the current ETA?? Any tasks we less-experienced matplotlibbers
can help with?

Cheers,

Matthew
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel


_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160628/6752b79b/attachment.html>

From jenshnielsen at gmail.com  Tue Jun 28 05:20:06 2016
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Tue, 28 Jun 2016 09:20:06 +0000
Subject: [Matplotlib-devel] How's progress with 1.5.2?
In-Reply-To: <772873849.4352871.1467104534727.JavaMail.yahoo@mail.yahoo.com>
References: <CAH6Pt5pdfaw-Ng=K3OH2p6PYt+aQuLk55da3ckdG+sGO5gBG2Q@mail.gmail.com>
 <CAA48SF8Botbocthnngn8qh4bhwgm4ZRbs7iNreqqp=d6ZSzc_w@mail.gmail.com>
 <772873849.4352871.1467104534727.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <CAM-Pw01n5YR3X0o61GLLff7sidauMC677SWgcYC7p53w1edNJw@mail.gmail.com>

Down to 1 issue now which is not strictly a 1.5.2 issue since it's about
providing manylinux  wheels for older versions

On Tue, 28 Jun 2016 at 10:04 OceanWolf via Matplotlib-devel <
matplotlib-devel at python.org> wrote:

> I still see 1 PR and 2 issues open for 1.5.2...
> A problem?
>
> ------------------------------
> *From:* Thomas Caswell <tcaswell at gmail.com>
> *To:* Matthew Brett <matthew.brett at gmail.com>; matplotlib development
> list <matplotlib-devel at python.org>
> *Sent:* Tuesday, 28 June 2016, 3:16
> *Subject:* Re: [Matplotlib-devel] How's progress with 1.5.2?
>
> The bottle neck is me doing the final release.  My current plan is to do
> that July 2.
>
> Tom
>
> On Sun, Jun 26, 2016 at 5:44 PM Matthew Brett <matthew.brett at gmail.com>
> wrote:
>
> Hi,
>
> A friend of mine was just asking about 1.5.2 - he needs some fixes
> that landed after 1.5.1 for his own software package.
>
> What's the current ETA?  Any tasks we less-experienced matplotlibbers
> can help with?
>
> Cheers,
>
> Matthew
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160628/c2027039/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Wed Jun 29 05:30:47 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Wed, 29 Jun 2016 09:30:47 +0000 (UTC)
Subject: [Matplotlib-devel] Fw: Table defaults (font-issue?)
In-Reply-To: <1979346555.6340101.1464883386504.JavaMail.yahoo@mail.yahoo.com>
References: <1979346555.6340101.1464883386504.JavaMail.yahoo.ref@mail.yahoo.com>
 <1979346555.6340101.1464883386504.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <703796934.5569080.1467192647274.JavaMail.yahoo@mail.yahoo.com>

Sent this message (see below) almost a month ago, but message too large.? I have just used pngcrush on the image which reduced the image from 34k to 26k so hopefully this will send now.

     
----- Forwarded Message -----
 From: OceanWolf <juichenieder-nabb at yahoo.co.uk>
 To: Matplotlib Development List <matplotlib-devel at python.org> 
 Sent: Thursday, 2 June 2016, 18:03
 Subject: Table defaults (font-issue?)
   
Sorry for the late comment, I have just reinstalled matploblib for python3, finally making that transition :D.
I have just taken a look at tables thinking I might quickly try to convert the legend to a table, but perhaps too late to make 2.0, but I thought I would give it a go anyway.

Anyway, tables, looking at http://matplotlib.org/devdocs/examples/pylab_examples/table_demo.html it just about okay here, but on my system I don't see a gap between the descender and the bottom of the table cell, I would expect the same padding around the bottom of the decender irrespective of the font used.? I would need to do a bit more investigation here to see if the table even shows the full descender, or whether it clips it.? I use the current master branch for my test.

Best,
OceanWolf


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160629/01401745/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: table_new_2.png
Type: image/png
Size: 25944 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160629/01401745/attachment-0001.png>

From tcaswell at gmail.com  Wed Jun 29 21:31:16 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 30 Jun 2016 01:31:16 +0000
Subject: [Matplotlib-devel] Fw: Table defaults (font-issue?)
In-Reply-To: <703796934.5569080.1467192647274.JavaMail.yahoo@mail.yahoo.com>
References: <1979346555.6340101.1464883386504.JavaMail.yahoo.ref@mail.yahoo.com>
 <1979346555.6340101.1464883386504.JavaMail.yahoo@mail.yahoo.com>
 <703796934.5569080.1467192647274.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <CAA48SF-HcxKO63pnpejqRU6xgDF2ShuXBbDCBCTSraK=G4kMnQ@mail.gmail.com>

What would be the upside of converting the legend to be a table instead of
the current implementation?

Tom

On Wed, Jun 29, 2016 at 5:33 AM OceanWolf via Matplotlib-devel <
matplotlib-devel at python.org> wrote:

> Sent this message (see below) almost a month ago, but message too large.
> I have just used pngcrush on the image which reduced the image from 34k to
> 26k so hopefully this will send now.
>
>
>
> ----- Forwarded Message -----
> *From:* OceanWolf <juichenieder-nabb at yahoo.co.uk>
> *To:* Matplotlib Development List <matplotlib-devel at python.org>
> *Sent:* Thursday, 2 June 2016, 18:03
> *Subject:* Table defaults (font-issue?)
>
> Sorry for the late comment, I have just reinstalled matploblib for
> python3, finally making that transition :D.
>
> I have just taken a look at tables thinking I might quickly try to convert
> the legend to a table, but perhaps too late to make 2.0, but I thought I
> would give it a go anyway.
>
> Anyway, tables, looking at
> http://matplotlib.org/devdocs/examples/pylab_examples/table_demo.html it
> just about okay here, but on my system I don't see a gap between the
> descender and the bottom of the table cell, I would expect the same padding
> around the bottom of the decender irrespective of the font used.  I would
> need to do a bit more investigation here to see if the table even shows the
> full descender, or whether it clips it.  I use the current master branch
> for my test.
>
> Best,
> OceanWolf
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160630/f1a40e8f/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Thu Jun 30 06:21:13 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Thu, 30 Jun 2016 10:21:13 +0000 (UTC)
Subject: [Matplotlib-devel] Fw: Table defaults (font-issue?)
In-Reply-To: <CAA48SF-HcxKO63pnpejqRU6xgDF2ShuXBbDCBCTSraK=G4kMnQ@mail.gmail.com>
References: <1979346555.6340101.1464883386504.JavaMail.yahoo.ref@mail.yahoo.com>
 <1979346555.6340101.1464883386504.JavaMail.yahoo@mail.yahoo.com>
 <703796934.5569080.1467192647274.JavaMail.yahoo@mail.yahoo.com>
 <CAA48SF-HcxKO63pnpejqRU6xgDF2ShuXBbDCBCTSraK=G4kMnQ@mail.gmail.com>
Message-ID: <2110984767.6747983.1467282073946.JavaMail.yahoo@mail.yahoo.com>

I see it as easier code to maintain and to visualise, I see the Legend class extending the Table class, i.e. an "is" relationship, rather than a "has" relationship which makes more sense to me.? Rather than have two pieces of code that lay things out in rows and columns we only have one, from an API perspective we ensure we use the same methods for both, methods like setting/getting column-width and row-width, etcetera.? By having it work like this, then any changes to the Table class automatically transfer to the Legend class, for example if were to implement a fancy-table style or something, then that would also apply to the legend, or any other table styling for that matter.
I imagine implementation-wise we should consider the key, value of the legend as a block occupying one table cell, rather then taking up two cells (two columns), and then have extra methods/properties to control within the key, value block, but not 100% as it makes it more complicated.
Anyway, the main issue for 2.0 lies with the inconsistency between machines (probably font based) for the table_demo image.

      From: Thomas Caswell <tcaswell at gmail.com>
 To: OceanWolf <juichenieder-nabb at yahoo.co.uk>; "matplotlib-devel at python.org" <matplotlib-devel at python.org> 
 Sent: Thursday, 30 June 2016, 3:31
 Subject: Re: [Matplotlib-devel] Fw: Table defaults (font-issue?)
   
What would be the upside of converting the legend to be a table instead of the current implementation?
Tom
On Wed, Jun 29, 2016 at 5:33 AM OceanWolf via Matplotlib-devel <matplotlib-devel at python.org> wrote:

Sent this message (see below) almost a month ago, but message too large.? I have just used pngcrush on the image which reduced the image from 34k to 26k so hopefully this will send now.

     
----- Forwarded Message -----
 From: OceanWolf <juichenieder-nabb at yahoo.co.uk>
 To: Matplotlib Development List <matplotlib-devel at python.org> 
 Sent: Thursday, 2 June 2016, 18:03
 Subject: Table defaults (font-issue?)
   
Sorry for the late comment, I have just reinstalled matploblib for python3, finally making that transition :D.
I have just taken a look at tables thinking I might quickly try to convert the legend to a table, but perhaps too late to make 2.0, but I thought I would give it a go anyway.

Anyway, tables, looking at http://matplotlib.org/devdocs/examples/pylab_examples/table_demo.html it just about okay here, but on my system I don't see a gap between the descender and the bottom of the table cell, I would expect the same padding around the bottom of the decender irrespective of the font used.? I would need to do a bit more investigation here to see if the table even shows the full descender, or whether it clips it.? I use the current master branch for my test.

Best,
OceanWolf


   _______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel



  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160630/1486551f/attachment.html>