matplotlib-devel Mailing List for matplotlib (Page 12)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Sorry, wrong reciever.

Ok. I'll wait for the MEP directory to start writing a proposal.
Here is a flavor of what I think could be done (to be seen using a fixed width font):

"AB":
┌────────┐┌────────┐
│ A      ││ B      │
│        ││        │
│        ││        │
└────────┘└────────┘

"ABB":
┌──────┐┌──────────┐
│ A    ││ B        │
│      ││          │
│      ││          │
└──────┘└──────────┘

"ABD"
"CCD":
┌───────┐┌───────┐┌───────┐
│ A     ││ B     ││ D     │
│       ││       ││       │
│       ││       ││       │
└───────┘└───────┘│       │
┌────────────────┐│       │
│ C              ││       │
│                ││       │
└────────────────┘└───────┘

"AaBb":
┌───────┐┌─┐┌───────┐┌─┐
│ A     ││ ││ B     ││ │
│       ││ ││       ││ │
│       ││ ││       ││ │
└───────┘└─┘└───────┘└─┘

"  b  "
"aABCc":
            ┌───────┐
            └───────┘
┌─┐┌───────┐┌───────┐┌───────┐┌─┐
│ ││ A     ││ B     ││ C     ││ │
│ ││       ││       ││       ││ │
│ ││       ││       ││       ││ │
└─┘└───────┘└───────┘└───────┘└─┘

> On 19 Mar 2015, at 15:34, Benjamin Root <ben...@ou...> wrote:
> 
> two problems with that: 1) that really doesn't make me want to use this approach, especially since I wouldn't know what ratios I would want in the first place. 2) it can't tell if I want a horizontal or vertical colorbar, whereas the lower-case notation could have some logic to auto-detect the user's intent (e.g., all lower-case letters in the last row indicates horizontal bars). It would also allow us to return the plotting axes separate from the colorbar axes, which is how axes_grid1 does it, and it is very nice that way.
> 
> On Thu, Mar 19, 2015 at 6:31 AM, Nicolas P. Rougier <Nic...@in...> wrote:
> 
> I think you could specify colorbars using: ["AAAAAAAAAB"]
> (B is a vertical colorbar, 1/10 of total width)
> 
> Nicolas
> 
> 
> 
> > On 18 Mar 2015, at 18:52, Eric Firing <ef...@ha...> wrote:
> >
> > On 2015/03/18 7:42 AM, Benjamin Root wrote:
> >> A thought... could this perhaps be extended somehow to specify colorbars
> >> in the layout?
> >
> > A lower-case letter could indicate a colorbar-size Axes:
> >
> > layout = ["ABc",
> >           "DE ",
> >           "ff "]
> >
> > would put a vertical think axes to the right of B, and a double-wide
> > hoizontal one below D and E.
> >
> > All of this seems like an alternative API for gridspec and axes_grid1.
> >
> > I am concerned about ending up with too many ways to do things, but with
> > subtle differences.
> >
> > How much control over spacing and sizing would be provided by kwargs or
> > other adjustment mechanisms?  How would this relate to subplot_params?
> >
> > Eric
> >
> >
> >
> > ------------------------------------------------------------------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 

two problems with that: 1) that really doesn't make me want to use this
approach, especially since I wouldn't know what ratios I would want in the
first place. 2) it can't tell if I want a horizontal or vertical colorbar,
whereas the lower-case notation could have some logic to auto-detect the
user's intent (e.g., all lower-case letters in the last row indicates
horizontal bars). It would also allow us to return the plotting axes
separate from the colorbar axes, which is how axes_grid1 does it, and it is
very nice that way.

On Thu, Mar 19, 2015 at 6:31 AM, Nicolas P. Rougier <
Nic...@in...> wrote:

>
> I think you could specify colorbars using: ["AAAAAAAAAB"]
> (B is a vertical colorbar, 1/10 of total width)
>
> Nicolas
>
>
>
> > On 18 Mar 2015, at 18:52, Eric Firing <ef...@ha...> wrote:
> >
> > On 2015/03/18 7:42 AM, Benjamin Root wrote:
> >> A thought... could this perhaps be extended somehow to specify colorbars
> >> in the layout?
> >
> > A lower-case letter could indicate a colorbar-size Axes:
> >
> > layout = ["ABc",
> >           "DE ",
> >           "ff "]
> >
> > would put a vertical think axes to the right of B, and a double-wide
> > hoizontal one below D and E.
> >
> > All of this seems like an alternative API for gridspec and axes_grid1.
> >
> > I am concerned about ending up with too many ways to do things, but with
> > subtle differences.
> >
> > How much control over spacing and sizing would be provided by kwargs or
> > other adjustment mechanisms?  How would this relate to subplot_params?
> >
> > Eric
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

I think you could specify colorbars using: ["AAAAAAAAAB"]
(B is a vertical colorbar, 1/10 of total width)

Nicolas

> On 18 Mar 2015, at 18:52, Eric Firing <ef...@ha...> wrote:
> 
> On 2015/03/18 7:42 AM, Benjamin Root wrote:
>> A thought... could this perhaps be extended somehow to specify colorbars
>> in the layout?
> 
> A lower-case letter could indicate a colorbar-size Axes:
> 
> layout = ["ABc",
>           "DE ",
>           "ff "]
> 
> would put a vertical think axes to the right of B, and a double-wide 
> hoizontal one below D and E.
> 
> All of this seems like an alternative API for gridspec and axes_grid1.
> 
> I am concerned about ending up with too many ways to do things, but with 
> subtle differences.
> 
> How much control over spacing and sizing would be provided by kwargs or 
> other adjustment mechanisms?  How would this relate to subplot_params?
> 
> Eric
> 
> 
> 
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

I love this layout spec idea! Gridspec is a pain in the ass. Bonus points for actually drawing the letter e.g. on the top left corner of each panel, so that the figures are ready for publication.

On Thu, Mar 19, 2015 at 5:04 AM, Benjamin Root <ben...@ou...> wrote:

> I like that. Furthermore, now that we build and push the docs with every
> merge in master, there is less reason to not do it that way.
> On Wed, Mar 18, 2015 at 1:56 PM, Thomas Caswell <tca...@gm...> wrote:
>> Currently we are doing MEPs on the wiki (
>> https://github.com/matplotlib/matplotlib/wiki/MEPTemplate) , but I would
>> like to move them to be in the docs (make a MEP folder next to 'users'?) as
>> the visibility on the wiki is low, there isn't a great way to leave line
>> comments, and we should have these documents in the official docs
>> eventually.
>>
>> Tom
>>
>> On Wed, Mar 18, 2015 at 1:45 PM Nicolas P. Rougier <
>> Nic...@in...> wrote:
>>
>>>
>>> Yes, a MEP makes sense to discuss the proposal.
>>> What's the procedure to open a MEP (i.e. where) ?
>>>
>>> Nicolas
>>>
>>>
>>> > On 18 Mar 2015, at 18:44, Benjamin Root <ben...@ou...> wrote:
>>> >
>>> > Also, perhaps it makes sense to make this a MEP to finalize and
>>> document the spec?
>>> >
>>> > On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:
>>> > That is neat. I would be sure to put in some "..seealso::" lines in
>>> places like plt.subplots and GridSpec and such.
>>> >
>>> > A thought... could this perhaps be extended somehow to specify
>>> colorbars in the layout? I am not sure how I would do that, but if we could
>>> come up with a way to do it, *that* would make this a killer feature. But
>>> even without that, this is still pretty useful.
>>> >
>>> > On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...>
>>> wrote:
>>> > Cool.  I think it make sense to put this in to `pyplot.py` next to
>>> `subplots`
>>> >
>>> > Tom
>>> >
>>> > On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
>>> Nic...@in...> wrote:
>>> >
>>> > Hi,
>>> >
>>> > I've been experimenting with a simple idea for specifying plot layout
>>> in a rather intuitive way.
>>> > The idea is simply to "draw" your layout using strings.
>>> >
>>> > Examples:
>>> >
>>> > layout = ["AB"]
>>> > -> means two plots side by side with equal width
>>> >
>>> > layout = ["AAAB"]
>>> > -> means two plots side by side A being 3 times wider than B
>>> >
>>> > layout = ["AB",
>>> >           "CC"]
>>> > -> means two plots (A & B) side by side and C below with full width
>>> >
>>> > layout = ["AB",
>>> >           "C "]
>>> > -> means two plots (A & B) side by side and C below A (same width)
>>> >
>>> > etc... (have a look at sources)
>>> >
>>> > I guess you cannot express every layout but it might work for most
>>> common ones.
>>> >
>>> > If you think this might a good addition I can try to make a PR but I'm
>>> not sure where to insert it.
>>> > My idea would be to have a layout function such that you can write:
>>> >
>>> > A,B,C = plt.layout(["AB", "CC"], border=0.01)
>>> > A.plot(...)
>>> > B.plot(...)
>>> > C.plot(...)
>>> >
>>> >
>>> > Nicolas
>>> >
>>> >
>>> > ------------------------------------------------------------
>>> ------------------
>>> > 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
>>> > Mat...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>> >
>>> > ------------------------------------------------------------
>>> ------------------
>>> > 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
>>> > Mat...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>> >
>>> >
>>> >
>>>
>>>
I like that. Furthermore, now that we build and push the docs with every
merge in master, there is less reason to not do it that way.

On Wed, Mar 18, 2015 at 1:56 PM, Thomas Caswell <tca...@gm...> wrote:

> Currently we are doing MEPs on the wiki (
> https://github.com/matplotlib/matplotlib/wiki/MEPTemplate) , but I would
> like to move them to be in the docs (make a MEP folder next to 'users'?) as
> the visibility on the wiki is low, there isn't a great way to leave line
> comments, and we should have these documents in the official docs
> eventually.
>
> Tom
>
> On Wed, Mar 18, 2015 at 1:45 PM Nicolas P. Rougier <
> Nic...@in...> wrote:
>
>>
>> Yes, a MEP makes sense to discuss the proposal.
>> What's the procedure to open a MEP (i.e. where) ?
>>
>> Nicolas
>>
>>
>> > On 18 Mar 2015, at 18:44, Benjamin Root <ben...@ou...> wrote:
>> >
>> > Also, perhaps it makes sense to make this a MEP to finalize and
>> document the spec?
>> >
>> > On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:
>> > That is neat. I would be sure to put in some "..seealso::" lines in
>> places like plt.subplots and GridSpec and such.
>> >
>> > A thought... could this perhaps be extended somehow to specify
>> colorbars in the layout? I am not sure how I would do that, but if we could
>> come up with a way to do it, *that* would make this a killer feature. But
>> even without that, this is still pretty useful.
>> >
>> > On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...>
>> wrote:
>> > Cool.  I think it make sense to put this in to `pyplot.py` next to
>> `subplots`
>> >
>> > Tom
>> >
>> > On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
>> Nic...@in...> wrote:
>> >
>> > Hi,
>> >
>> > I've been experimenting with a simple idea for specifying plot layout
>> in a rather intuitive way.
>> > The idea is simply to "draw" your layout using strings.
>> >
>> > Examples:
>> >
>> > layout = ["AB"]
>> > -> means two plots side by side with equal width
>> >
>> > layout = ["AAAB"]
>> > -> means two plots side by side A being 3 times wider than B
>> >
>> > layout = ["AB",
>> >           "CC"]
>> > -> means two plots (A & B) side by side and C below with full width
>> >
>> > layout = ["AB",
>> >           "C "]
>> > -> means two plots (A & B) side by side and C below A (same width)
>> >
>> > etc... (have a look at sources)
>> >
>> > I guess you cannot express every layout but it might work for most
>> common ones.
>> >
>> > If you think this might a good addition I can try to make a PR but I'm
>> not sure where to insert it.
>> > My idea would be to have a layout function such that you can write:
>> >
>> > A,B,C = plt.layout(["AB", "CC"], border=0.01)
>> > A.plot(...)
>> > B.plot(...)
>> > C.plot(...)
>> >
>> >
>> > Nicolas
>> >
>> >
>> > ------------------------------------------------------------
>> ------------------
>> > 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
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>> > ------------------------------------------------------------
>> ------------------
>> > 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
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>> >
>> >
>>
>>

Currently we are doing MEPs on the wiki (
https://github.com/matplotlib/matplotlib/wiki/MEPTemplate) , but I would
like to move them to be in the docs (make a MEP folder next to 'users'?) as
the visibility on the wiki is low, there isn't a great way to leave line
comments, and we should have these documents in the official docs
eventually.

Tom

On Wed, Mar 18, 2015 at 1:45 PM Nicolas P. Rougier <Nic...@in...>
wrote:

>
> Yes, a MEP makes sense to discuss the proposal.
> What's the procedure to open a MEP (i.e. where) ?
>
> Nicolas
>
>
> > On 18 Mar 2015, at 18:44, Benjamin Root <ben...@ou...> wrote:
> >
> > Also, perhaps it makes sense to make this a MEP to finalize and document
> the spec?
> >
> > On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:
> > That is neat. I would be sure to put in some "..seealso::" lines in
> places like plt.subplots and GridSpec and such.
> >
> > A thought... could this perhaps be extended somehow to specify colorbars
> in the layout? I am not sure how I would do that, but if we could come up
> with a way to do it, *that* would make this a killer feature. But even
> without that, this is still pretty useful.
> >
> > On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...>
> wrote:
> > Cool.  I think it make sense to put this in to `pyplot.py` next to
> `subplots`
> >
> > Tom
> >
> > On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
> Nic...@in...> wrote:
> >
> > Hi,
> >
> > I've been experimenting with a simple idea for specifying plot layout in
> a rather intuitive way.
> > The idea is simply to "draw" your layout using strings.
> >
> > Examples:
> >
> > layout = ["AB"]
> > -> means two plots side by side with equal width
> >
> > layout = ["AAAB"]
> > -> means two plots side by side A being 3 times wider than B
> >
> > layout = ["AB",
> >           "CC"]
> > -> means two plots (A & B) side by side and C below with full width
> >
> > layout = ["AB",
> >           "C "]
> > -> means two plots (A & B) side by side and C below A (same width)
> >
> > etc... (have a look at sources)
> >
> > I guess you cannot express every layout but it might work for most
> common ones.
> >
> > If you think this might a good addition I can try to make a PR but I'm
> not sure where to insert it.
> > My idea would be to have a layout function such that you can write:
> >
> > A,B,C = plt.layout(["AB", "CC"], border=0.01)
> > A.plot(...)
> > B.plot(...)
> > C.plot(...)
> >
> >
> > Nicolas
> >
> >
> > ------------------------------------------------------------
> ------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> > ------------------------------------------------------------
> ------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
> >
>
>

Fantastic question. I don't see any mention of it in the docs. Perhaps I
should create a MEP to discuss that...

This is the best I could find: https://github.com/matplotlib/matplotlib/wiki

On Wed, Mar 18, 2015 at 1:45 PM, Nicolas P. Rougier <
Nic...@in...> wrote:

>
> Yes, a MEP makes sense to discuss the proposal.
> What's the procedure to open a MEP (i.e. where) ?
>
> Nicolas
>
>
> > On 18 Mar 2015, at 18:44, Benjamin Root <ben...@ou...> wrote:
> >
> > Also, perhaps it makes sense to make this a MEP to finalize and document
> the spec?
> >
> > On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:
> > That is neat. I would be sure to put in some "..seealso::" lines in
> places like plt.subplots and GridSpec and such.
> >
> > A thought... could this perhaps be extended somehow to specify colorbars
> in the layout? I am not sure how I would do that, but if we could come up
> with a way to do it, *that* would make this a killer feature. But even
> without that, this is still pretty useful.
> >
> > On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...>
> wrote:
> > Cool.  I think it make sense to put this in to `pyplot.py` next to
> `subplots`
> >
> > Tom
> >
> > On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
> Nic...@in...> wrote:
> >
> > Hi,
> >
> > I've been experimenting with a simple idea for specifying plot layout in
> a rather intuitive way.
> > The idea is simply to "draw" your layout using strings.
> >
> > Examples:
> >
> > layout = ["AB"]
> > -> means two plots side by side with equal width
> >
> > layout = ["AAAB"]
> > -> means two plots side by side A being 3 times wider than B
> >
> > layout = ["AB",
> >           "CC"]
> > -> means two plots (A & B) side by side and C below with full width
> >
> > layout = ["AB",
> >           "C "]
> > -> means two plots (A & B) side by side and C below A (same width)
> >
> > etc... (have a look at sources)
> >
> > I guess you cannot express every layout but it might work for most
> common ones.
> >
> > If you think this might a good addition I can try to make a PR but I'm
> not sure where to insert it.
> > My idea would be to have a layout function such that you can write:
> >
> > A,B,C = plt.layout(["AB", "CC"], border=0.01)
> > A.plot(...)
> > B.plot(...)
> > C.plot(...)
> >
> >
> > Nicolas
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On 2015/03/18 7:42 AM, Benjamin Root wrote:
> A thought... could this perhaps be extended somehow to specify colorbars
> in the layout?

A lower-case letter could indicate a colorbar-size Axes:

layout = ["ABc",
           "DE ",
           "ff "]

would put a vertical think axes to the right of B, and a double-wide 
hoizontal one below D and E.

All of this seems like an alternative API for gridspec and axes_grid1.

I am concerned about ending up with too many ways to do things, but with 
subtle differences.

How much control over spacing and sizing would be provided by kwargs or 
other adjustment mechanisms?  How would this relate to subplot_params?

Eric

Yes, a MEP makes sense to discuss the proposal.
What's the procedure to open a MEP (i.e. where) ?

Nicolas

> On 18 Mar 2015, at 18:44, Benjamin Root <ben...@ou...> wrote:
> 
> Also, perhaps it makes sense to make this a MEP to finalize and document the spec?
> 
> On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:
> That is neat. I would be sure to put in some "..seealso::" lines in places like plt.subplots and GridSpec and such.
> 
> A thought... could this perhaps be extended somehow to specify colorbars in the layout? I am not sure how I would do that, but if we could come up with a way to do it, *that* would make this a killer feature. But even without that, this is still pretty useful.
> 
> On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...> wrote:
> Cool.  I think it make sense to put this in to `pyplot.py` next to `subplots`
> 
> Tom
> 
> On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <Nic...@in...> wrote:
> 
> Hi,
> 
> I've been experimenting with a simple idea for specifying plot layout in a rather intuitive way.
> The idea is simply to "draw" your layout using strings.
> 
> Examples:
> 
> layout = ["AB"]
> -> means two plots side by side with equal width
> 
> layout = ["AAAB"]
> -> means two plots side by side A being 3 times wider than B
> 
> layout = ["AB",
>           "CC"]
> -> means two plots (A & B) side by side and C below with full width
> 
> layout = ["AB",
>           "C "]
> -> means two plots (A & B) side by side and C below A (same width)
> 
> etc... (have a look at sources)
> 
> I guess you cannot express every layout but it might work for most common ones.
> 
> If you think this might a good addition I can try to make a PR but I'm not sure where to insert it.
> My idea would be to have a layout function such that you can write:
> 
> A,B,C = plt.layout(["AB", "CC"], border=0.01)
> A.plot(...)
> B.plot(...)
> C.plot(...)
> 
> 
> Nicolas
> 
> 
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> 

Also, perhaps it makes sense to make this a MEP to finalize and document
the spec?

On Wed, Mar 18, 2015 at 1:42 PM, Benjamin Root <ben...@ou...> wrote:

> That is neat. I would be sure to put in some "..seealso::" lines in places
> like plt.subplots and GridSpec and such.
>
> A thought... could this perhaps be extended somehow to specify colorbars
> in the layout? I am not sure how I would do that, but if we could come up
> with a way to do it, *that* would make this a killer feature. But even
> without that, this is still pretty useful.
>
> On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...>
> wrote:
>
>> Cool.  I think it make sense to put this in to `pyplot.py` next to
>> `subplots`
>>
>> Tom
>>
>> On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
>> Nic...@in...> wrote:
>>
>>>
>>> Hi,
>>>
>>> I've been experimenting with a simple idea for specifying plot layout in
>>> a rather intuitive way.
>>> The idea is simply to "draw" your layout using strings.
>>>
>>> Examples:
>>>
>>> layout = ["AB"]
>>> -> means two plots side by side with equal width
>>>
>>> layout = ["AAAB"]
>>> -> means two plots side by side A being 3 times wider than B
>>>
>>> layout = ["AB",
>>>           "CC"]
>>> -> means two plots (A & B) side by side and C below with full width
>>>
>>> layout = ["AB",
>>>           "C "]
>>> -> means two plots (A & B) side by side and C below A (same width)
>>>
>>> etc... (have a look at sources)
>>>
>>> I guess you cannot express every layout but it might work for most
>>> common ones.
>>>
>>> If you think this might a good addition I can try to make a PR but I'm
>>> not sure where to insert it.
>>> My idea would be to have a layout function such that you can write:
>>>
>>> A,B,C = plt.layout(["AB", "CC"], border=0.01)
>>> A.plot(...)
>>> B.plot(...)
>>> C.plot(...)
>>>
>>>
>>> Nicolas
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> 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
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>

That is neat. I would be sure to put in some "..seealso::" lines in places
like plt.subplots and GridSpec and such.

A thought... could this perhaps be extended somehow to specify colorbars in
the layout? I am not sure how I would do that, but if we could come up with
a way to do it, *that* would make this a killer feature. But even without
that, this is still pretty useful.

On Wed, Mar 18, 2015 at 1:20 PM, Thomas Caswell <tca...@gm...> wrote:

> Cool.  I think it make sense to put this in to `pyplot.py` next to
> `subplots`
>
> Tom
>
> On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <
> Nic...@in...> wrote:
>
>>
>> Hi,
>>
>> I've been experimenting with a simple idea for specifying plot layout in
>> a rather intuitive way.
>> The idea is simply to "draw" your layout using strings.
>>
>> Examples:
>>
>> layout = ["AB"]
>> -> means two plots side by side with equal width
>>
>> layout = ["AAAB"]
>> -> means two plots side by side A being 3 times wider than B
>>
>> layout = ["AB",
>>           "CC"]
>> -> means two plots (A & B) side by side and C below with full width
>>
>> layout = ["AB",
>>           "C "]
>> -> means two plots (A & B) side by side and C below A (same width)
>>
>> etc... (have a look at sources)
>>
>> I guess you cannot express every layout but it might work for most common
>> ones.
>>
>> If you think this might a good addition I can try to make a PR but I'm
>> not sure where to insert it.
>> My idea would be to have a layout function such that you can write:
>>
>> A,B,C = plt.layout(["AB", "CC"], border=0.01)
>> A.plot(...)
>> B.plot(...)
>> C.plot(...)
>>
>>
>> Nicolas
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> 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
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Cool.  I think it make sense to put this in to `pyplot.py` next to
`subplots`

Tom

On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier <Nic...@in...>
wrote:

>
> Hi,
>
> I've been experimenting with a simple idea for specifying plot layout in a
> rather intuitive way.
> The idea is simply to "draw" your layout using strings.
>
> Examples:
>
> layout = ["AB"]
> -> means two plots side by side with equal width
>
> layout = ["AAAB"]
> -> means two plots side by side A being 3 times wider than B
>
> layout = ["AB",
>           "CC"]
> -> means two plots (A & B) side by side and C below with full width
>
> layout = ["AB",
>           "C "]
> -> means two plots (A & B) side by side and C below A (same width)
>
> etc... (have a look at sources)
>
> I guess you cannot express every layout but it might work for most common
> ones.
>
> If you think this might a good addition I can try to make a PR but I'm not
> sure where to insert it.
> My idea would be to have a layout function such that you can write:
>
> A,B,C = plt.layout(["AB", "CC"], border=0.01)
> A.plot(...)
> B.plot(...)
> C.plot(...)
>
>
> Nicolas
>
>
> ------------------------------------------------------------
> ------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,

I've been experimenting with a simple idea for specifying plot layout in a rather intuitive way.
The idea is simply to "draw" your layout using strings.

Examples:

layout = ["AB"]
-> means two plots side by side with equal width

layout = ["AAAB"]
-> means two plots side by side A being 3 times wider than B

layout = ["AB",
          "CC"]
-> means two plots (A & B) side by side and C below with full width

layout = ["AB",
          "C "]
-> means two plots (A & B) side by side and C below A (same width)

etc... (have a look at sources)

I guess you cannot express every layout but it might work for most common ones.

If you think this might a good addition I can try to make a PR but I'm not sure where to insert it.
My idea would be to have a layout function such that you can write:

A,B,C = plt.layout(["AB", "CC"], border=0.01)
A.plot(...)
B.plot(...)
C.plot(...)

Nicolas

Keith,

Back to the issue at hand. could you do the following?

import setuptools
print(setuptools.__file__)

It would be interesting to see if that path differs from the path of the
egg you just listed.
Ben

On Wed, Mar 18, 2015 at 11:39 AM, <kei...@bt...> wrote:

> pip still thinks I have the latest.   I think it's a question of how to
> force the matplotlib setup.py to use actually it.
> Keith
>
> kbriggs:~/Downloads/matplotlib-1.4.3> sudo pip3  install setuptools
> --upgrade
> Requirement already up-to-date: setuptools in
> /usr/local/lib/python3.4/dist-packages/setuptools-14.3-py3.4.egg
> Cleaning up...
>
> ________________________________________
> From: ben...@gm... [ben...@gm...] On Behalf Of Benjamin
> Root [ben...@ou...]
> Sent: 18 March 2015 15:33
> To: Briggs,KM,Keith,TUB2 R
> Cc: matplotlib development list
> Subject: Re: [matplotlib-devel] 1.4.3 does not build on Ubuntu 14 with
> python3
>
> I would just use pip. Ubuntu/Debian has really messed up the python
> environment in more ways than one.
>
> On Wed, Mar 18, 2015 at 11:08 AM, keithbriggs <kei...@bt...<mailto:
> kei...@bt...>> wrote:
> The Ubuntu package manager tells me it is up to date.
> If I download setuptools-14.3 and install, it goes into /usr/local/lib/ and
> doesn't get used.
> How do I force it to be used?
> Or am I supposed to override the Ubuntu package manager?
> Keith
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Wed, Mar 18, 2015 at 3:51 PM, Benjamin Root <ben...@ou...> wrote:
> Let's not turn this into a flame war and let's figure out why this user's
> setuptools is not being recognized properly. We can discuss my experience
> with python2.7 on 12.04 LTS off-list, if you wish (i personally switched to
> miniconda to avoid the hassle).

I agree, but you started it :) also if you had problems with Ubuntu, I
would have avoided to bring Debian in the discussion - case closed for
me.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Let's not turn this into a flame war and let's figure out why this user's
setuptools is not being recognized properly. We can discuss my experience
with python2.7 on 12.04 LTS off-list, if you wish (i personally switched to
miniconda to avoid the hassle).

On Wed, Mar 18, 2015 at 11:43 AM, Sandro Tosi <mo...@de...> wrote:

> On Wed, Mar 18, 2015 at 3:33 PM, Benjamin Root <ben...@ou...> wrote:
> > I would just use pip. Ubuntu/Debian has really messed up the python
> > environment in more ways than one.
>
> <debian developer hat=on/> ehm... either you back up your claims
> (and/or try to understand the reasons behind the distro needs) or
> maybe i would not output such a strong statement.
>
> Regards,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Wed, Mar 18, 2015 at 3:33 PM, Benjamin Root <ben...@ou...> wrote:
> I would just use pip. Ubuntu/Debian has really messed up the python
> environment in more ways than one.

<debian developer hat=on/> ehm... either you back up your claims
(and/or try to understand the reasons behind the distro needs) or
maybe i would not output such a strong statement.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

pip still thinks I have the latest.   I think it's a question of how to force the matplotlib setup.py to use actually it.
Keith

kbriggs:~/Downloads/matplotlib-1.4.3> sudo pip3  install setuptools --upgrade 
Requirement already up-to-date: setuptools in /usr/local/lib/python3.4/dist-packages/setuptools-14.3-py3.4.egg
Cleaning up...

________________________________________
From: ben...@gm... [ben...@gm...] On Behalf Of Benjamin Root [ben...@ou...]
Sent: 18 March 2015 15:33
To: Briggs,KM,Keith,TUB2 R
Cc: matplotlib development list
Subject: Re: [matplotlib-devel] 1.4.3 does not build on Ubuntu 14 with python3

I would just use pip. Ubuntu/Debian has really messed up the python environment in more ways than one.

On Wed, Mar 18, 2015 at 11:08 AM, keithbriggs <kei...@bt...<mailto:kei...@bt...>> wrote:
The Ubuntu package manager tells me it is up to date.
If I download setuptools-14.3 and install, it goes into /usr/local/lib/ and
doesn't get used.
How do I force it to be used?
Or am I supposed to override the Ubuntu package manager?
Keith

I would just use pip. Ubuntu/Debian has really messed up the python
environment in more ways than one.

On Wed, Mar 18, 2015 at 11:08 AM, keithbriggs <kei...@bt...> wrote:

> The Ubuntu package manager tells me it is up to date.
> If I download setuptools-14.3 and install, it goes into /usr/local/lib/ and
> doesn't get used.
> How do I force it to be used?
> Or am I supposed to override the Ubuntu package manager?
> Keith
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/1-4-3-does-not-build-on-Ubuntu-14-with-python3-tp45198p45201.html
> Sent from the matplotlib - devel mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

The Ubuntu package manager tells me it is up to date.
If I download setuptools-14.3 and install, it goes into /usr/local/lib/ and
doesn't get used.
How do I force it to be used?
Or am I supposed to override the Ubuntu package manager?
Keith

--
View this message in context: http://matplotlib.1069221.n5.nabble.com/1-4-3-does-not-build-on-Ubuntu-14-with-python3-tp45198p45201.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

Also see https://github.com/matplotlib/matplotlib/issues/3889

On Wed, Mar 18, 2015 at 10:22 AM Benjamin Root <ben...@ou...> wrote:

> Please update your install of setuptools.
>
> On Wed, Mar 18, 2015 at 10:01 AM, <kei...@bt...> wrote:
>
>> kbriggs:~/Downloads/matplotlib-1.4.3> python3 setup.py build
>> ============================================================================
>> Edit setup.cfg to change the build options
>>
>> BUILDING MATPLOTLIB
>>             matplotlib: yes [1.4.3]
>>                 python: yes [3.4.0 (default, Apr 11 2014, 13:05:11)  [GCC
>>                         4.8.2]]
>>               platform: yes [linux]
>>
>> REQUIRED DEPENDENCIES AND EXTENSIONS
>>                  numpy: yes [version 1.8.2]
>>                    six: yes [using six version 1.5.2]
>>               dateutil: yes [dateutil was not found. It is required for
>> date
>>                         axis support. pip/easy_install may attempt to
>>                         install it after matplotlib.]
>>                   pytz: yes [pytz was not found. pip will attempt to
>> install
>>                         it after matplotlib.]
>>                tornado: yes [tornado was not found. It is required for the
>>                         WebAgg backend. pip/easy_install may attempt to
>>                         install it after matplotlib.]
>>              pyparsing: yes [using pyparsing version 2.0.1]
>>                  pycxx: yes [Official versions of PyCXX are not compatible
>>                         with matplotlib on Python 3.x, since they lack
>>                         support for the buffer object.  Using local copy]
>>                 libagg: yes [pkg-config information for 'libagg' could not
>>                         be found. Using local copy.] Traceback (most
>> recent call last):
>>   File "setup.py", line 155, in <module>
>>     result = package.check()
>>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 961,
>> in check
>>     min_version='2.3', version=version)
>>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 445,
>> in _check_for_pkg_config
>>     if (not is_min_version(version, min_version)):
>>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 173,
>> in is_min_version
>>     return found_version >= expected_version
>>   File "/usr/lib/python3.4/distutils/version.py", line 76, in __ge__
>>     c = self._cmp(other)
>>   File "/usr/lib/python3.4/distutils/version.py", line 343, in _cmp
>>     if self.version < other.version:
>> TypeError: unorderable types: str() < int()
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
> ------------------------------------------------------------
> ------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Please update your install of setuptools.

On Wed, Mar 18, 2015 at 10:01 AM, <kei...@bt...> wrote:

> kbriggs:~/Downloads/matplotlib-1.4.3> python3 setup.py build
> ============================================================================
> Edit setup.cfg to change the build options
>
> BUILDING MATPLOTLIB
>             matplotlib: yes [1.4.3]
>                 python: yes [3.4.0 (default, Apr 11 2014, 13:05:11)  [GCC
>                         4.8.2]]
>               platform: yes [linux]
>
> REQUIRED DEPENDENCIES AND EXTENSIONS
>                  numpy: yes [version 1.8.2]
>                    six: yes [using six version 1.5.2]
>               dateutil: yes [dateutil was not found. It is required for
> date
>                         axis support. pip/easy_install may attempt to
>                         install it after matplotlib.]
>                   pytz: yes [pytz was not found. pip will attempt to
> install
>                         it after matplotlib.]
>                tornado: yes [tornado was not found. It is required for the
>                         WebAgg backend. pip/easy_install may attempt to
>                         install it after matplotlib.]
>              pyparsing: yes [using pyparsing version 2.0.1]
>                  pycxx: yes [Official versions of PyCXX are not compatible
>                         with matplotlib on Python 3.x, since they lack
>                         support for the buffer object.  Using local copy]
>                 libagg: yes [pkg-config information for 'libagg' could not
>                         be found. Using local copy.] Traceback (most
> recent call last):
>   File "setup.py", line 155, in <module>
>     result = package.check()
>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 961,
> in check
>     min_version='2.3', version=version)
>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 445,
> in _check_for_pkg_config
>     if (not is_min_version(version, min_version)):
>   File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 173,
> in is_min_version
>     return found_version >= expected_version
>   File "/usr/lib/python3.4/distutils/version.py", line 76, in __ge__
>     c = self._cmp(other)
>   File "/usr/lib/python3.4/distutils/version.py", line 343, in _cmp
>     if self.version < other.version:
> TypeError: unorderable types: str() < int()
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

kbriggs:~/Downloads/matplotlib-1.4.3> python3 setup.py build ============================================================================
Edit setup.cfg to change the build options

BUILDING MATPLOTLIB
            matplotlib: yes [1.4.3]
                python: yes [3.4.0 (default, Apr 11 2014, 13:05:11)  [GCC
                        4.8.2]]
              platform: yes [linux]

REQUIRED DEPENDENCIES AND EXTENSIONS
                 numpy: yes [version 1.8.2]
                   six: yes [using six version 1.5.2]
              dateutil: yes [dateutil was not found. It is required for date
                        axis support. pip/easy_install may attempt to
                        install it after matplotlib.]
                  pytz: yes [pytz was not found. pip will attempt to install
                        it after matplotlib.]
               tornado: yes [tornado was not found. It is required for the
                        WebAgg backend. pip/easy_install may attempt to
                        install it after matplotlib.]
             pyparsing: yes [using pyparsing version 2.0.1]
                 pycxx: yes [Official versions of PyCXX are not compatible
                        with matplotlib on Python 3.x, since they lack
                        support for the buffer object.  Using local copy]
                libagg: yes [pkg-config information for 'libagg' could not
                        be found. Using local copy.] Traceback (most recent call last):
  File "setup.py", line 155, in <module>
    result = package.check()
  File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 961, in check
    min_version='2.3', version=version)
  File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 445, in _check_for_pkg_config
    if (not is_min_version(version, min_version)):
  File "/home/kbriggs/Downloads/matplotlib-1.4.3/setupext.py", line 173, in is_min_version
    return found_version >= expected_version
  File "/usr/lib/python3.4/distutils/version.py", line 76, in __ge__
    c = self._cmp(other)
  File "/usr/lib/python3.4/distutils/version.py", line 343, in _cmp
    if self.version < other.version:
TypeError: unorderable types: str() < int()

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

matplotlib-devel Mailing List for matplotlib (Page 12)

matplotlib-devel — matplotlib developers