matplotlib-devel Mailing List for matplotlib

---------------------------------
Submission deadline in 3 days !!!
---------------------------------
EuroScipy 2015, the annual conference on Python in science will take place in
Cambridge, UK on 26-30 August 2015. The conference features two days of
tutorials followed by two days of scientific talks & posters and an extra day
dedicated to developer sprints. It is the major event in Europe in the field of
technical/scientific computing within the Python ecosystem. Data scientists,
analysts, quants, PhD's, scientists and students from more than 20 countries
attended the conference last year.
The topics presented at EuroSciPy are very diverse, with a focus on advanced
software engineering and original uses of Python and its scientific libraries,
either in theoretical or experimental research, from both academia and the
industry.
Submissions for posters, talks & tutorials (beginner and advanced) are welcome
on our website at http://www.euroscipy.org/2015/ Sprint proposals should be
addressed directly to the organisation at eur...@py...
Important dates
===============
Mar 24, 2015	Call for talks, posters & tutorials
Apr 30, 2015	Talk and tutorials submission deadline
May 1, 2015	Registration opens
May 30, 2015	Final program announced
Jun 15, 2015	Early-bird registration ends
Aug 26-27, 2015	Tutorials
Aug 28-29, 2015	Main conference
Aug 30, 2015	Sprints
We look forward to an exciting conference and hope to see you in Cambridge
The EuroSciPy 2015 Team - http://www.euroscipy.org/2015/

The branch 1.4.x was the branch for bug fixes that would eventually turn
into the _next_ 1.4 series release. We do not plan on doing a 1.4.4 so the
1.4.x branch no longer is needed. The commit used for the releases are
tagged (ex v1.4.3). The v1.4.3-doc branch is so that we can correct any
documentation issues and re-build the website if needed.
Tom
On Sun, Apr 26, 2015 at 9:12 AM Mike Kaufman <mc...@gm...> wrote:
> So it seems I was using the old branch (now deleted?) v1.4.x rather than
> v1.4.3-doc, which does have the commit for the fix in question. I was
> naively assuming that v1.4.x was always the latest release in the v1.4
> series.
>
> False alarm. Sorry.
>
> M
>
> On 4/25/15 4:26 PM, Thomas Caswell wrote:
> > The commit that fixes that
> >
> https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
> > should be in 1.4.1 an onward. Exactly which version are you using?
> >
> > There will be no 1.4.4.
> >
> > On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman <kau...@or...
> > <mailto:kau...@or...>> wrote:
> >
> > Is there any possibility of back-porting the fix to the boxplot
> > positions to v1.4.x? This would be ticket #3563. I had thought that
> this
> > was fixed in 1.4, but it seems to be there again. v1.5-devel (where
> the
> > boxplot works fine) is not-very-usable for me due to the GTK idle
> bug.
> >
> > Thanks,
> >
> > M
> >
> >
> ------------------------------------------------------------------------------
> > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> > Develop your own process in accordance with the BPMN 2 standard
> > Learn Process modeling best practices with Bonita BPM through live
> > exercises
> > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> > event?utm_
> >
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > <mailto:Mat...@li...>
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > One dashboard for servers and applications across Physical-Virtual-Cloud
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> >
> >
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

I am in favor of doing in in PR comments so we can to line comments.
On Sun, Apr 26, 2015 at 3:47 AM Nicolas P. Rougier <Nic...@in...>
wrote:
>
> Great ! Thanks for setting this up. One comment, it would be great to have
> a README.rst in the directory to have abstract of all MEPS at once in
> github (I can make a PR).
>
>
> I've started working on MEP28 (
> https://github.com/rougier/matplotlib/blob/MEP28/doc/devel/MEP/MEP28.rst).
> I intend to make a PR once it is a bit more polished or should I make a PR
> right now to initiate the discussion on the PR ? (It is not clear to me if
> the preferred medium for discussion is the mailing list or the PR comments).
>
>
> Nicolas
>
> > On 25 Apr 2015, at 23:04, Thomas Caswell <tca...@gm...> wrote:
> >
> > The MEP tree has been moved into the main repo
> https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP
> >
> > I am pretty excited about this feature.
> >
> > I don't remember if this got mentioned upthread, but this ties in with
> https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to set
> up all of the constraints.
> >
> > Tom
> >
> > On Thu, Mar 19, 2015 at 1:10 PM Nicolas P. Rougier <
> Nic...@in...> wrote:
> > 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
> >>
> >
> >
> ------------------------------------------------------------------------------
> > 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
>
>

So it seems I was using the old branch (now deleted?) v1.4.x rather than 
v1.4.3-doc, which does have the commit for the fix in question. I was 
naively assuming that v1.4.x was always the latest release in the v1.4 
series.
False alarm. Sorry.
M
On 4/25/15 4:26 PM, Thomas Caswell wrote:
> The commit that fixes that
> https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
> should be in 1.4.1 an onward. Exactly which version are you using?
>
> There will be no 1.4.4.
>
> On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman <kau...@or...
> <mailto:kau...@or...>> wrote:
>
> Is there any possibility of back-porting the fix to the boxplot
> positions to v1.4.x? This would be ticket #3563. I had thought that this
> was fixed in 1.4, but it seems to be there again. v1.5-devel (where the
> boxplot works fine) is not-very-usable for me due to the GTK idle bug.
>
> Thanks,
>
> M
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Great ! Thanks for setting this up. One comment, it would be great to have a README.rst in the directory to have abstract of all MEPS at once in github (I can make a PR).
I've started working on MEP28 (https://github.com/rougier/matplotlib/blob/MEP28/doc/devel/MEP/MEP28.rst). I intend to make a PR once it is a bit more polished or should I make a PR right now to initiate the discussion on the PR ? (It is not clear to me if the preferred medium for discussion is the mailing list or the PR comments).
Nicolas
> On 25 Apr 2015, at 23:04, Thomas Caswell <tca...@gm...> wrote:
> 
> The MEP tree has been moved into the main repo https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP
> 
> I am pretty excited about this feature.
> 
> I don't remember if this got mentioned upthread, but this ties in with https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to set up all of the constraints.
> 
> Tom
> 
> On Thu, Mar 19, 2015 at 1:10 PM Nicolas P. Rougier <Nic...@in...> wrote:
> 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
>> 
> 
> ------------------------------------------------------------------------------
> 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 have made some progress with this, I found a incomplete recipe written by
some body. So the next step for me is to read the python-for-android's
distribute.sh file so I can get a better understanding of the template they
provide. I am slow though because less time and will power.
On Sun, Apr 26, 2015 at 2:29 AM, Thomas Caswell <tca...@gm...> wrote:
> Sorry this never got a response. I also have no idea where to start, but
> mpl depends an numpy (which has significant c code) and a number of c
> extensions internally (Agg for rasterization, freetype for font rendering).
>
> I would suggest starting with figuring out how to compile numpy as it is
> required and I suspect simpler to compile.
>
> Tom
>
> On Sun, Mar 29, 2015 at 9:19 AM Achyut Rastogi <ras...@gm...>
> wrote:
>
>> Hello,
>> I want to compile matplotlib for Android, but I really don't have any
>> clue where to start, well I have already stated with learning SL4A, also
>> inclement sir(Alexander Taylor) says that its already been done by someone
>> but I couldn't find it at all so if somebody has any information about it
>> please post it here, also if you have anything else that may help in this,
>> please post that here too.
>> If somebody is interested in this, they can check my progress here
>> <http://immovableone.blogspot.in/>.
>> Lastly, Thank you very much for all the informative comments on the
>> thread 'Kivy backend', that really helped me a lot in writing my proposal.
>>
>> ------------------------------------------------------------------------------
>> 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 MEP tree has been moved into the main repo
https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP
I am pretty excited about this feature.
I don't remember if this got mentioned upthread, but this ties in with
https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to set
up all of the constraints.
Tom
On Thu, Mar 19, 2015 at 1:10 PM Nicolas P. Rougier <Nic...@in...>
wrote:
> 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
>
>
>
> ------------------------------------------------------------------------------
> 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
>

Sorry this never got a response. I also have no idea where to start, but
mpl depends an numpy (which has significant c code) and a number of c
extensions internally (Agg for rasterization, freetype for font rendering).
I would suggest starting with figuring out how to compile numpy as it is
required and I suspect simpler to compile.
Tom
On Sun, Mar 29, 2015 at 9:19 AM Achyut Rastogi <ras...@gm...>
wrote:
> Hello,
> I want to compile matplotlib for Android, but I really don't have any clue
> where to start, well I have already stated with learning SL4A, also
> inclement sir(Alexander Taylor) says that its already been done by someone
> but I couldn't find it at all so if somebody has any information about it
> please post it here, also if you have anything else that may help in this,
> please post that here too.
> If somebody is interested in this, they can check my progress here
> <http://immovableone.blogspot.in/>.
> Lastly, Thank you very much for all the informative comments on the thread
> 'Kivy backend', that really helped me a lot in writing my proposal.
>
> ------------------------------------------------------------------------------
> 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 commit that fixes that
https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
should be in 1.4.1 an onward. Exactly which version are you using?
There will be no 1.4.4.
On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman <kau...@or...> wrote:
> Is there any possibility of back-porting the fix to the boxplot
> positions to v1.4.x? This would be ticket #3563. I had thought that this
> was fixed in 1.4, but it seems to be there again. v1.5-devel (where the
> boxplot works fine) is not-very-usable for me due to the GTK idle bug.
>
> Thanks,
>
> M
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Is there any possibility of back-porting the fix to the boxplot 
positions to v1.4.x? This would be ticket #3563. I had thought that this 
was fixed in 1.4, but it seems to be there again. v1.5-devel (where the 
boxplot works fine) is not-very-usable for me due to the GTK idle bug.
Thanks,
M

Kelvin,
Thank you for your work. Would it be possible for you to open a pull
request on git hub with these changes (that is where we so almost all of
our code review recently and is hooked in to a continuous integration
service).
I have not looked at the diff yet (still on my phone), but from looking at
the file list I am a bit concerned. The backends have a good number of
imports that are there for compatibility reasons.
This might also conflict with the mep27 related pr #4143.
There is also an open pr working on the wx backend that this may conflict
with (#3421).
Tom
On Mon, Apr 20, 2015, 02:07 Kelvin Li <ltw...@gm...> wrote:
> First ever patch submission. Here I propose cleaning up some unused
> variables
> and imports.
>
> Kelvin Li (2):
> remove unused variable "cmd_split"
> backends: remove unnecessary import statements
>
> lib/matplotlib/backends/backend_agg.py | 2 --
> lib/matplotlib/backends/backend_cairo.py | 5 ++--
> lib/matplotlib/backends/backend_gdk.py | 9 -------
> lib/matplotlib/backends/backend_gtk.py | 7 +++--
> lib/matplotlib/backends/backend_gtk3agg.py | 1 -
> lib/matplotlib/backends/backend_gtk3cairo.py | 2 --
> lib/matplotlib/backends/backend_gtkagg.py | 7 +----
> lib/matplotlib/backends/backend_gtkcairo.py | 3 ---
> lib/matplotlib/backends/backend_macosx.py | 11 +++-----
> lib/matplotlib/backends/backend_mixed.py | 2 --
> lib/matplotlib/backends/backend_nbagg.py | 2 --
> lib/matplotlib/backends/backend_pgf.py | 2 --
> lib/matplotlib/backends/backend_ps.py | 26 +++----------------
> lib/matplotlib/backends/backend_qt4.py | 36
> ++------------------------
> lib/matplotlib/backends/backend_qt4agg.py | 11 --------
> lib/matplotlib/backends/backend_qt5agg.py | 9 -------
> lib/matplotlib/backends/backend_svg.py | 12 ++++-----
> lib/matplotlib/backends/backend_template.py | 4 ---
> lib/matplotlib/backends/backend_tkagg.py | 13 +++-------
> lib/matplotlib/backends/backend_webagg.py | 1 -
> lib/matplotlib/backends/backend_webagg_core.py | 4 ---
> lib/matplotlib/backends/backend_wx.py | 2 --
> lib/matplotlib/backends/backend_wxagg.py | 9 +++----
> lib/matplotlib/backends/tkagg.py | 3 ---
> lib/matplotlib/backends/windowing.py | 2 --
> lib/matplotlib/texmanager.py | 6 -----
> 26 files changed, 26 insertions(+), 165 deletions(-)
>
> --
> 2.1.4
>
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

---
 lib/matplotlib/backends/backend_agg.py | 2 --
 lib/matplotlib/backends/backend_cairo.py | 5 ++--
 lib/matplotlib/backends/backend_gdk.py | 9 -------
 lib/matplotlib/backends/backend_gtk.py | 7 +++--
 lib/matplotlib/backends/backend_gtk3agg.py | 1 -
 lib/matplotlib/backends/backend_gtk3cairo.py | 2 --
 lib/matplotlib/backends/backend_gtkagg.py | 7 +----
 lib/matplotlib/backends/backend_gtkcairo.py | 3 ---
 lib/matplotlib/backends/backend_macosx.py | 11 +++-----
 lib/matplotlib/backends/backend_mixed.py | 2 --
 lib/matplotlib/backends/backend_nbagg.py | 2 --
 lib/matplotlib/backends/backend_pgf.py | 2 --
 lib/matplotlib/backends/backend_ps.py | 23 +++-------------
 lib/matplotlib/backends/backend_qt4.py | 36 ++------------------------
 lib/matplotlib/backends/backend_qt4agg.py | 11 --------
 lib/matplotlib/backends/backend_qt5agg.py | 9 -------
 lib/matplotlib/backends/backend_svg.py | 12 ++++-----
 lib/matplotlib/backends/backend_template.py | 4 ---
 lib/matplotlib/backends/backend_tkagg.py | 13 +++-------
 lib/matplotlib/backends/backend_webagg.py | 1 -
 lib/matplotlib/backends/backend_webagg_core.py | 4 ---
 lib/matplotlib/backends/backend_wx.py | 2 --
 lib/matplotlib/backends/backend_wxagg.py | 9 +++----
 lib/matplotlib/backends/tkagg.py | 3 ---
 lib/matplotlib/backends/windowing.py | 2 --
 25 files changed, 26 insertions(+), 156 deletions(-)
diff --git a/lib/matplotlib/backends/backend_agg.py b/lib/matplotlib/backends/backend_agg.py
index 687e52b..a048014 100644
--- a/lib/matplotlib/backends/backend_agg.py
+++ b/lib/matplotlib/backends/backend_agg.py
@@ -22,8 +22,6 @@ TODO:
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import threading
 import numpy as np
 
diff --git a/lib/matplotlib/backends/backend_cairo.py b/lib/matplotlib/backends/backend_cairo.py
index 5956982..0402a26 100644
--- a/lib/matplotlib/backends/backend_cairo.py
+++ b/lib/matplotlib/backends/backend_cairo.py
@@ -23,7 +23,7 @@ from __future__ import (absolute_import, division, print_function,
 
 import six
 
-import os, sys, warnings, gzip
+import sys, warnings, gzip
 
 import numpy as np
 
@@ -55,11 +55,10 @@ from matplotlib.cbook import is_string_like
 from matplotlib.figure import Figure
 from matplotlib.mathtext import MathTextParser
 from matplotlib.path import Path
-from matplotlib.transforms import Bbox, Affine2D
+from matplotlib.transforms import Affine2D
 from matplotlib.font_manager import ttfFontProperty
 
 _debug = False
-#_debug = True
 
 # Image::color_conv(format) for draw_image()
 if sys.byteorder == 'little':
diff --git a/lib/matplotlib/backends/backend_gdk.py b/lib/matplotlib/backends/backend_gdk.py
index d3e8e5b..51912aa 100644
--- a/lib/matplotlib/backends/backend_gdk.py
+++ b/lib/matplotlib/backends/backend_gdk.py
@@ -1,15 +1,8 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
-import math
-import os
-import sys
 import warnings
-def fn_name(): return sys._getframe(1).f_code.co_name
 
-import gobject
 import gtk; gdk = gtk.gdk
 import pango
 pygtk_version_required = (2,2,0)
@@ -23,10 +16,8 @@ import numpy as np
 
 import matplotlib
 from matplotlib import rcParams
-from matplotlib._pylab_helpers import Gcf
 from matplotlib.backend_bases import RendererBase, GraphicsContextBase, \
 FigureManagerBase, FigureCanvasBase
-from matplotlib.cbook import is_string_like
 from matplotlib.figure import Figure
 from matplotlib.mathtext import MathTextParser
 from matplotlib.transforms import Affine2D
diff --git a/lib/matplotlib/backends/backend_gtk.py b/lib/matplotlib/backends/backend_gtk.py
index 1a6ee31..9febd7a 100644
--- a/lib/matplotlib/backends/backend_gtk.py
+++ b/lib/matplotlib/backends/backend_gtk.py
@@ -29,11 +29,11 @@ _new_tooltip_api = (gtk.pygtk_version[1] >= 12)
 
 import matplotlib
 from matplotlib._pylab_helpers import Gcf
-from matplotlib.backend_bases import RendererBase, GraphicsContextBase, \
- FigureManagerBase, FigureCanvasBase, NavigationToolbar2, cursors, TimerBase
+from matplotlib.backend_bases import (FigureManagerBase, FigureCanvasBase,
+ NavigationToolbar2, cursors, TimerBase)
 from matplotlib.backend_bases import ShowBase
 
-from matplotlib.backends.backend_gdk import RendererGDK, FigureCanvasGDK
+from matplotlib.backends.backend_gdk import RendererGDK
 from matplotlib.cbook import is_string_like, is_writable_file_like
 from matplotlib.colors import colorConverter
 from matplotlib.figure import Figure
@@ -48,7 +48,6 @@ from matplotlib import rcParams
 backend_version = "%d.%d.%d" % gtk.pygtk_version
 
 _debug = False
-#_debug = True
 
 # the true dots per inch on the screen; should be display dependent
 # see http://groups.google.com/groups?q=screen+dpi+x11&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&selm=7077.26e81ad5%40swift.cs.tcd.ie&rnum=5 for some info about screen dpi
diff --git a/lib/matplotlib/backends/backend_gtk3agg.py b/lib/matplotlib/backends/backend_gtk3agg.py
index c3eb1da..7a98311 100644
--- a/lib/matplotlib/backends/backend_gtk3agg.py
+++ b/lib/matplotlib/backends/backend_gtk3agg.py
@@ -4,7 +4,6 @@ from __future__ import (absolute_import, division, print_function,
 import six
 
 import numpy as np
-import sys
 import warnings
 
 from . import backend_agg
diff --git a/lib/matplotlib/backends/backend_gtk3cairo.py b/lib/matplotlib/backends/backend_gtk3cairo.py
index da8f099..dde3b08 100644
--- a/lib/matplotlib/backends/backend_gtk3cairo.py
+++ b/lib/matplotlib/backends/backend_gtk3cairo.py
@@ -1,8 +1,6 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 from . import backend_gtk3
 from . import backend_cairo
 from .backend_cairo import cairo, HAS_CAIRO_CFFI
diff --git a/lib/matplotlib/backends/backend_gtkagg.py b/lib/matplotlib/backends/backend_gtkagg.py
index 3e10841..8177d2b 100644
--- a/lib/matplotlib/backends/backend_gtkagg.py
+++ b/lib/matplotlib/backends/backend_gtkagg.py
@@ -4,16 +4,11 @@ Render to gtk from agg
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
-import os
-
 import matplotlib
 from matplotlib.figure import Figure
 from matplotlib.backends.backend_agg import FigureCanvasAgg
 from matplotlib.backends.backend_gtk import gtk, FigureManagerGTK, FigureCanvasGTK,\
- show, draw_if_interactive,\
- error_msg_gtk, PIXELS_PER_INCH, backend_version, \
+ backend_version, \
 NavigationToolbar2GTK
 from matplotlib.backends._gtkagg import agg_to_gtk_drawable
 
diff --git a/lib/matplotlib/backends/backend_gtkcairo.py b/lib/matplotlib/backends/backend_gtkcairo.py
index 93bb698..94d0dd8 100644
--- a/lib/matplotlib/backends/backend_gtkcairo.py
+++ b/lib/matplotlib/backends/backend_gtkcairo.py
@@ -5,8 +5,6 @@ Author: Steve Chaplin
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import gtk
 if gtk.pygtk_version < (2,7,0):
 import cairo.gtk
@@ -19,7 +17,6 @@ backend_version = 'PyGTK(%d.%d.%d) ' % gtk.pygtk_version + \
 
 _debug = False
-#_debug = True
 
 def new_figure_manager(num, *args, **kwargs):
diff --git a/lib/matplotlib/backends/backend_macosx.py b/lib/matplotlib/backends/backend_macosx.py
index ef4572f..05f568f 100755
--- a/lib/matplotlib/backends/backend_macosx.py
+++ b/lib/matplotlib/backends/backend_macosx.py
@@ -2,28 +2,23 @@ from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
 import six
-
 import os
 import numpy
 
 from matplotlib._pylab_helpers import Gcf
-from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
- FigureManagerBase, FigureCanvasBase, NavigationToolbar2, TimerBase
-from matplotlib.backend_bases import ShowBase
+from matplotlib.backend_bases import (RendererBase, GraphicsContextBase,
+ FigureManagerBase, FigureCanvasBase, NavigationToolbar2, TimerBase,
+ ShowBase)
 
 from matplotlib.cbook import maxdict
 from matplotlib.figure import Figure
-from matplotlib.path import Path
 from matplotlib.mathtext import MathTextParser
-from matplotlib.colors import colorConverter
 from matplotlib import rcParams
-
 from matplotlib.widgets import SubplotTool
 
 import matplotlib
 from matplotlib.backends import _macosx
 
-
 class Show(ShowBase):
 def mainloop(self):
 _macosx.show()
diff --git a/lib/matplotlib/backends/backend_mixed.py b/lib/matplotlib/backends/backend_mixed.py
index 6de45ed..d63985c 100644
--- a/lib/matplotlib/backends/backend_mixed.py
+++ b/lib/matplotlib/backends/backend_mixed.py
@@ -1,8 +1,6 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 from matplotlib._image import frombuffer
 from matplotlib.backends.backend_agg import RendererAgg
 from matplotlib.tight_bbox import process_figure_for_rasterizing
diff --git a/lib/matplotlib/backends/backend_nbagg.py b/lib/matplotlib/backends/backend_nbagg.py
index eada1c1..d72c0e2 100644
--- a/lib/matplotlib/backends/backend_nbagg.py
+++ b/lib/matplotlib/backends/backend_nbagg.py
@@ -4,7 +4,6 @@
 # that changes made maintain expected behaviour.
 
 from base64 import b64encode
-from contextlib import contextmanager
 import json
 import io
 import os
@@ -18,7 +17,6 @@ from IPython.kernel.comm import Comm
 
 from matplotlib import rcParams
 from matplotlib.figure import Figure
-from matplotlib.backends import backend_agg
 from matplotlib.backends.backend_webagg_core import (FigureManagerWebAgg,
 FigureCanvasWebAggCore,
 NavigationToolbar2WebAgg)
diff --git a/lib/matplotlib/backends/backend_pgf.py b/lib/matplotlib/backends/backend_pgf.py
index db8cda3..69b1cb1 100644
--- a/lib/matplotlib/backends/backend_pgf.py
+++ b/lib/matplotlib/backends/backend_pgf.py
@@ -22,14 +22,12 @@ from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
 FigureManagerBase, FigureCanvasBase
 from matplotlib.backends.backend_mixed import MixedModeRenderer
 from matplotlib.figure import Figure
-from matplotlib.text import Text
 from matplotlib.path import Path
 from matplotlib import _png, rcParams
 from matplotlib.cbook import is_string_like, is_writable_file_like
 from matplotlib.compat import subprocess
 from matplotlib.compat.subprocess import check_output
 
-
 ###############################################################################
 
 # create a list of system fonts, all of these should work with xe/lua-latex
diff --git a/lib/matplotlib/backends/backend_ps.py b/lib/matplotlib/backends/backend_ps.py
index 699d1ba..68f0db8 100644
--- a/lib/matplotlib/backends/backend_ps.py
+++ b/lib/matplotlib/backends/backend_ps.py
@@ -5,21 +5,15 @@ A PostScript backend, which can produce both PostScript .ps and .eps
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
+import binascii, glob, io, os, re, shutil, sys, time
+from tempfile import mkstemp
+
 import six
 from six.moves import StringIO
 
-import glob, math, os, shutil, sys, time
-def _fn_name(): return sys._getframe(1).f_code.co_name
-import io
-
-try:
- from hashlib import md5
-except ImportError:
- from md5 import md5 #Deprecated in 2.5
+import numpy as np
 
-from tempfile import mkstemp
 from matplotlib import verbose, __version__, rcParams, checkdep_ghostscript
-from matplotlib._pylab_helpers import Gcf
 from matplotlib.afm import AFM
 from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
 FigureManagerBase, FigureCanvasBase
@@ -27,33 +21,24 @@ from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
 from matplotlib.cbook import is_string_like, get_realpath_and_stat, \
 is_writable_file_like, maxdict, file_requires_unicode
 from matplotlib.figure import Figure
-
 from matplotlib.font_manager import findfont, is_opentype_cff_font
 from matplotlib.ft2font import FT2Font, KERNING_DEFAULT, LOAD_NO_HINTING
 from matplotlib.ttconv import convert_ttf_to_ps
 from matplotlib.mathtext import MathTextParser
 from matplotlib._mathtext_data import uni2type1
-from matplotlib.text import Text
 from matplotlib.path import Path
 from matplotlib import _path
 from matplotlib.transforms import Affine2D
-
 from matplotlib.backends.backend_mixed import MixedModeRenderer
 
-
-import numpy as np
-import binascii
-import re
 try:
 set
 except NameError:
 from sets import Set as set
 
 backend_version = 'Level II'
-
 debugPS = 0
 
-
 class PsBackendHelper(object):
 
 def __init__(self):
diff --git a/lib/matplotlib/backends/backend_qt4.py b/lib/matplotlib/backends/backend_qt4.py
index 8298ae3..095cf60 100644
--- a/lib/matplotlib/backends/backend_qt4.py
+++ b/lib/matplotlib/backends/backend_qt4.py
@@ -1,48 +1,16 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-from six import unichr
-import os
-import re
-import signal
-import sys
-
-import matplotlib
-
-from matplotlib.cbook import is_string_like
-from matplotlib.backend_bases import FigureManagerBase
 from matplotlib.backend_bases import FigureCanvasBase
-from matplotlib.backend_bases import NavigationToolbar2
-
-from matplotlib.backend_bases import cursors
-from matplotlib.backend_bases import TimerBase
-from matplotlib.backend_bases import ShowBase
-
-from matplotlib._pylab_helpers import Gcf
 from matplotlib.figure import Figure
 
+from .qt_compat import QtCore, QtWidgets, __version__
 
-from matplotlib.widgets import SubplotTool
-try:
- import matplotlib.backends.qt_editor.figureoptions as figureoptions
-except ImportError:
- figureoptions = None
-
-from .qt_compat import QtCore, QtWidgets, _getSaveFileName, __version__
-from matplotlib.backends.qt_editor.formsubplottool import UiSubplotTool
-
-from .backend_qt5 import (backend_version, SPECIAL_KEYS, SUPER, ALT, CTRL,
- SHIFT, MODIFIER_KEYS, fn_name, cursord,
- draw_if_interactive, _create_qApp, show, TimerQT,
- MainWindow, FigureManagerQT, NavigationToolbar2QT,
- SubplotToolQt, error_msg_qt, exception_handler)
-
+from .backend_qt5 import (backend_version, _create_qApp, FigureManagerQT)
 from .backend_qt5 import FigureCanvasQT as FigureCanvasQT5
 
 DEBUG = False
 
-
 def new_figure_manager(num, *args, **kwargs):
 """
 Create a new figure manager instance
diff --git a/lib/matplotlib/backends/backend_qt4agg.py b/lib/matplotlib/backends/backend_qt4agg.py
index fc20578..31ce686 100644
--- a/lib/matplotlib/backends/backend_qt4agg.py
+++ b/lib/matplotlib/backends/backend_qt4agg.py
@@ -4,29 +4,18 @@ Render to qt from agg
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
-import os # not used
 import sys
 import ctypes
-import warnings
 
 import matplotlib
 from matplotlib.figure import Figure
 
-
 from .backend_qt5agg import FigureCanvasQTAggBase
 
 from .backend_agg import FigureCanvasAgg
 from .backend_qt4 import QtCore
 from .backend_qt4 import FigureManagerQT
 from .backend_qt4 import FigureCanvasQT
-from .backend_qt4 import NavigationToolbar2QT
-##### not used
-from .backend_qt4 import show
-from .backend_qt4 import draw_if_interactive
-from .backend_qt4 import backend_version
-######
 
 DEBUG = False
 
diff --git a/lib/matplotlib/backends/backend_qt5agg.py b/lib/matplotlib/backends/backend_qt5agg.py
index 687f436..41f6a0c 100644
--- a/lib/matplotlib/backends/backend_qt5agg.py
+++ b/lib/matplotlib/backends/backend_qt5agg.py
@@ -4,8 +4,6 @@ Render to qt from agg
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import sys
 import ctypes
 
@@ -15,15 +13,8 @@ from .backend_agg import FigureCanvasAgg
 from .backend_qt5 import QtCore
 from .backend_qt5 import QtGui
 from .backend_qt5 import FigureManagerQT
-from .backend_qt5 import NavigationToolbar2QT
 ##### Modified Qt5 backend import
 from .backend_qt5 import FigureCanvasQT
-##### not used
-from .backend_qt5 import show
-from .backend_qt5 import draw_if_interactive
-from .backend_qt5 import backend_version
-######
-
 
 DEBUG = False
 
diff --git a/lib/matplotlib/backends/backend_svg.py b/lib/matplotlib/backends/backend_svg.py
index 4462c9b..e8ddf64 100644
--- a/lib/matplotlib/backends/backend_svg.py
+++ b/lib/matplotlib/backends/backend_svg.py
@@ -5,29 +5,27 @@ import six
 from six.moves import xrange
 from six import unichr
 
-import os, base64, tempfile, gzip, io, sys, codecs, re
+import base64, gzip, io, codecs, re
 
 import numpy as np
 
 from hashlib import md5
 
 from matplotlib import verbose, __version__, rcParams
-from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
- FigureManagerBase, FigureCanvasBase
+from matplotlib.backend_bases import (RendererBase, FigureManagerBase,
+ FigureCanvasBase)
 from matplotlib.backends.backend_mixed import MixedModeRenderer
 from matplotlib.cbook import is_string_like, is_writable_file_like, maxdict
 from matplotlib.colors import rgb2hex
 from matplotlib.figure import Figure
-from matplotlib.font_manager import findfont, FontProperties
-from matplotlib.ft2font import FT2Font, KERNING_DEFAULT, LOAD_NO_HINTING
+from matplotlib.font_manager import findfont
+from matplotlib.ft2font import FT2Font, LOAD_NO_HINTING
 from matplotlib.mathtext import MathTextParser
 from matplotlib.path import Path
 from matplotlib import _path
 from matplotlib.transforms import Affine2D, Affine2DBase
 from matplotlib import _png
 
-from xml.sax.saxutils import escape as escape_xml_text
-
 backend_version = __version__
 
 # ----------------------------------------------------------------------
diff --git a/lib/matplotlib/backends/backend_template.py b/lib/matplotlib/backends/backend_template.py
index f3e483d..91b25c2 100644
--- a/lib/matplotlib/backends/backend_template.py
+++ b/lib/matplotlib/backends/backend_template.py
@@ -65,15 +65,11 @@ Naming Conventions
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import matplotlib
 from matplotlib._pylab_helpers import Gcf
 from matplotlib.backend_bases import RendererBase, GraphicsContextBase,\
 FigureManagerBase, FigureCanvasBase
 from matplotlib.figure import Figure
-from matplotlib.transforms import Bbox
-
 
 class RendererTemplate(RendererBase):
 """
diff --git a/lib/matplotlib/backends/backend_tkagg.py b/lib/matplotlib/backends/backend_tkagg.py
index 8ffc8a8..8dc934b 100644
--- a/lib/matplotlib/backends/backend_tkagg.py
+++ b/lib/matplotlib/backends/backend_tkagg.py
@@ -4,7 +4,6 @@ from __future__ import (absolute_import, division, print_function,
 
 import six
 from six.moves import tkinter as Tk
-from six.moves import tkinter_filedialog as FileDialog
 
 import os, sys, math
 import os.path
@@ -17,25 +16,19 @@ import matplotlib.backends.windowing as windowing
 
 import matplotlib
 from matplotlib.cbook import is_string_like
-from matplotlib.backend_bases import RendererBase, GraphicsContextBase
-from matplotlib.backend_bases import FigureManagerBase, FigureCanvasBase
-from matplotlib.backend_bases import NavigationToolbar2, cursors, TimerBase
-from matplotlib.backend_bases import (ShowBase, ToolContainerBase,
+from matplotlib.backend_bases import (FigureManagerBase, FigureCanvasBase,
+ NavigationToolbar2, cursors, TimerBase,
+ ShowBase, ToolContainerBase,
 StatusbarBase)
 from matplotlib.backend_managers import ToolManager
 from matplotlib import backend_tools
 from matplotlib._pylab_helpers import Gcf
-
 from matplotlib.figure import Figure
-
 from matplotlib.widgets import SubplotTool
 
-import matplotlib.cbook as cbook
-
 rcParams = matplotlib.rcParams
 verbose = matplotlib.verbose
 
-
 backend_version = Tk.TkVersion
 
 # the true dots per inch on the screen; should be display dependent
diff --git a/lib/matplotlib/backends/backend_webagg.py b/lib/matplotlib/backends/backend_webagg.py
index fe03107..0e0a225 100644
--- a/lib/matplotlib/backends/backend_webagg.py
+++ b/lib/matplotlib/backends/backend_webagg.py
@@ -15,7 +15,6 @@ from __future__ import (absolute_import, division, print_function,
 
 import six
 
-import datetime
 import errno
 import json
 import os
diff --git a/lib/matplotlib/backends/backend_webagg_core.py b/lib/matplotlib/backends/backend_webagg_core.py
index 849b3de..aacd727 100644
--- a/lib/matplotlib/backends/backend_webagg_core.py
+++ b/lib/matplotlib/backends/backend_webagg_core.py
@@ -13,12 +13,9 @@ Displays Agg images in the browser, with interactivity
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import io
 import json
 import os
-import time
 import warnings
 
 import numpy as np
@@ -28,7 +25,6 @@ from matplotlib.figure import Figure
 from matplotlib import backend_bases
 from matplotlib import _png
 
-
 def new_figure_manager(num, *args, **kwargs):
 """
 Create a new figure manager instance
diff --git a/lib/matplotlib/backends/backend_wx.py b/lib/matplotlib/backends/backend_wx.py
index 81f41d7..da08a41 100644
--- a/lib/matplotlib/backends/backend_wx.py
+++ b/lib/matplotlib/backends/backend_wx.py
@@ -28,8 +28,6 @@ import warnings
 
 import numpy as np
 
-from matplotlib.cbook import mplDeprecation
-
 # Debugging settings here...
 # Debug level set here. If the debug level is less than 5, information
 # messages (progressively more info for lower value) are printed. In addition,
diff --git a/lib/matplotlib/backends/backend_wxagg.py b/lib/matplotlib/backends/backend_wxagg.py
index 5dd0103..f1d8c3c 100644
--- a/lib/matplotlib/backends/backend_wxagg.py
+++ b/lib/matplotlib/backends/backend_wxagg.py
@@ -1,19 +1,16 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 import matplotlib
 from matplotlib.figure import Figure
 
 from .backend_agg import FigureCanvasAgg
 from . import backend_wx # already uses wxversion.ensureMinimal('2.8')
-from .backend_wx import FigureManagerWx, FigureCanvasWx, \
- FigureFrameWx, DEBUG_MSG, NavigationToolbar2Wx, error_msg_wx, \
- draw_if_interactive, show, Toolbar, backend_version
+from .backend_wx import (FigureManagerWx, FigureCanvasWx,
+ FigureFrameWx, DEBUG_MSG, NavigationToolbar2Wx,
+ draw_if_interactive, backend_version)
 import wx
 
-
 class FigureFrameWxAgg(FigureFrameWx):
 def get_canvas(self, fig):
 return FigureCanvasWxAgg(self, -1, fig)
diff --git a/lib/matplotlib/backends/tkagg.py b/lib/matplotlib/backends/tkagg.py
index 81fe926..fa16b67 100644
--- a/lib/matplotlib/backends/tkagg.py
+++ b/lib/matplotlib/backends/tkagg.py
@@ -1,11 +1,8 @@
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
 from six.moves import tkinter as Tk
-
 import numpy as np
-
 from matplotlib.backends import _tkagg
 
 def blit(photoimage, aggimage, bbox=None, colormode=1):
diff --git a/lib/matplotlib/backends/windowing.py b/lib/matplotlib/backends/windowing.py
index 6c2e495..1b99fd6 100644
--- a/lib/matplotlib/backends/windowing.py
+++ b/lib/matplotlib/backends/windowing.py
@@ -9,8 +9,6 @@ It uses a tiny C++ extension module to access MS Win functions.
 from __future__ import (absolute_import, division, print_function,
 unicode_literals)
 
-import six
-
 from matplotlib import rcParams
 
 try:
-- 
2.1.4

---
 lib/matplotlib/backends/backend_ps.py | 3 ---
 lib/matplotlib/texmanager.py | 6 ------
 2 files changed, 9 deletions(-)
diff --git a/lib/matplotlib/backends/backend_ps.py b/lib/matplotlib/backends/backend_ps.py
index cea707d..699d1ba 100644
--- a/lib/matplotlib/backends/backend_ps.py
+++ b/lib/matplotlib/backends/backend_ps.py
@@ -49,9 +49,6 @@ try:
 except NameError:
 from sets import Set as set
 
-if sys.platform.startswith('win'): cmd_split = '&'
-else: cmd_split = ';'
-
 backend_version = 'Level II'
 
 debugPS = 0
diff --git a/lib/matplotlib/texmanager.py b/lib/matplotlib/texmanager.py
index 5d52e7d..c23ed5f 100644
--- a/lib/matplotlib/texmanager.py
+++ b/lib/matplotlib/texmanager.py
@@ -60,12 +60,6 @@ import re
 
 DEBUG = False
 
-if sys.platform.startswith('win'):
- cmd_split = '&'
-else:
- cmd_split = ';'
-
-
 def dvipng_hack_alpha():
 try:
 p = Popen(['dvipng', '-version'], stdin=PIPE, stdout=PIPE,
-- 
2.1.4

First ever patch submission. Here I propose cleaning up some unused variables
and imports.
Kelvin Li (2):
 remove unused variable "cmd_split"
 backends: remove unnecessary import statements
 lib/matplotlib/backends/backend_agg.py | 2 --
 lib/matplotlib/backends/backend_cairo.py | 5 ++--
 lib/matplotlib/backends/backend_gdk.py | 9 -------
 lib/matplotlib/backends/backend_gtk.py | 7 +++--
 lib/matplotlib/backends/backend_gtk3agg.py | 1 -
 lib/matplotlib/backends/backend_gtk3cairo.py | 2 --
 lib/matplotlib/backends/backend_gtkagg.py | 7 +----
 lib/matplotlib/backends/backend_gtkcairo.py | 3 ---
 lib/matplotlib/backends/backend_macosx.py | 11 +++-----
 lib/matplotlib/backends/backend_mixed.py | 2 --
 lib/matplotlib/backends/backend_nbagg.py | 2 --
 lib/matplotlib/backends/backend_pgf.py | 2 --
 lib/matplotlib/backends/backend_ps.py | 26 +++----------------
 lib/matplotlib/backends/backend_qt4.py | 36 ++------------------------
 lib/matplotlib/backends/backend_qt4agg.py | 11 --------
 lib/matplotlib/backends/backend_qt5agg.py | 9 -------
 lib/matplotlib/backends/backend_svg.py | 12 ++++-----
 lib/matplotlib/backends/backend_template.py | 4 ---
 lib/matplotlib/backends/backend_tkagg.py | 13 +++-------
 lib/matplotlib/backends/backend_webagg.py | 1 -
 lib/matplotlib/backends/backend_webagg_core.py | 4 ---
 lib/matplotlib/backends/backend_wx.py | 2 --
 lib/matplotlib/backends/backend_wxagg.py | 9 +++----
 lib/matplotlib/backends/tkagg.py | 3 ---
 lib/matplotlib/backends/windowing.py | 2 --
 lib/matplotlib/texmanager.py | 6 -----
 26 files changed, 26 insertions(+), 165 deletions(-)
-- 
2.1.4

Not sure why my message didn't go through earlier, but yes, the issue 
already exists in the system, see 
https://github.com/matplotlib/matplotlib/issues/4092
On 07/04/15 19:07, Benjamin Root wrote:
> Yes, this was discovered recently in connection to changes in how idle 
> events were handled. I don't recall if there was an issue created for 
> it, though.
>
> On Tue, Apr 7, 2015 at 11:48 AM, Michael Kaufman <kau...@or... 
> <mailto:kau...@or...>> wrote:
>
> Hi All,
>
> I don't have time at the moment to submit a ticket, but I thought I'd
> see if anyone else is having this problem:
>
> With latest master on 1.5-devel using GTKAgg backend, (and in ipython
> 3.0.0-dev, python 2.7.8, MacOSX 10.9.5) if I do figure() and nothing
> else, and then run 'top', I see Python running 100% CPU for the
> process.
> Closing the figure stops Python hogging the CPU.
>
> With latest 1.4.x, I do not see it.
>
> M
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Yes, this was discovered recently in connection to changes in how idle
events were handled. I don't recall if there was an issue created for it,
though.
On Tue, Apr 7, 2015 at 11:48 AM, Michael Kaufman <kau...@or...> wrote:
> Hi All,
>
> I don't have time at the moment to submit a ticket, but I thought I'd
> see if anyone else is having this problem:
>
> With latest master on 1.5-devel using GTKAgg backend, (and in ipython
> 3.0.0-dev, python 2.7.8, MacOSX 10.9.5) if I do figure() and nothing
> else, and then run 'top', I see Python running 100% CPU for the process.
> Closing the figure stops Python hogging the CPU.
>
> With latest 1.4.x, I do not see it.
>
> M
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi All,
I don't have time at the moment to submit a ticket, but I thought I'd 
see if anyone else is having this problem:
With latest master on 1.5-devel using GTKAgg backend, (and in ipython 
3.0.0-dev, python 2.7.8, MacOSX 10.9.5) if I do figure() and nothing 
else, and then run 'top', I see Python running 100% CPU for the process. 
Closing the figure stops Python hogging the CPU.
With latest 1.4.x, I do not see it.
M

I guess you could just load some test patterns into any commercial software
graphics or design package that supports color gamut alarms, and try some
typical printer settings to make sure that the candidate color maps aren't
excessively blowing the boundaries. I'm not advocating that the default
color map needs to be perfectly reproducible in print, but it might be
worth sanity checking this; it might mean avoiding bright greens and
yellows for example. I see that PIL/pillow contains littlecms support and I
see its ImageCms.py file contains a GAMUTCHECK flag, so it might be
possible to use that, along with some common icc profiles to automate the
checking, or build it into an optimiser as a constraint.
On 6 April 2015 at 15:57, Nathaniel Smith <nj...@po...> wrote:
> On Apr 5, 2015 8:29 PM, "gary ruben" <gar...@gm...> wrote:
> >
> > Just wondering whether anyone has suggested checking candidate colormaps
> against typical printer color gamuts?
>
> How would you go about doing this in practice? Is it even possible to
> choose a subset of sRGB space and have printers take advantage of that when
> doing gamut mapping? (I guess I always assumed that printer gamut mapping
> applied to an RGB image would map all of RGB into their gamut, so there
> would be no advantage to restricting oneself go a subspace. But maybe I'm
> wrong -- color management is pretty fancy these days.)
>
> -n
>

"sunset" has a connotation of things ending. Howabout "sunrise"?
On Sun, Apr 5, 2015 at 5:18 PM, Olga Botvinnik <obo...@uc...> wrote:
> How about "pythonic sunset" ?
>
> On Sun, Apr 5, 2015 at 2:01 PM Benjamin Root <ben...@ou...> wrote:
>
>> That is nice. The blue is a bit heavy, but that might be my display. Now,
>> how should we order it by default? I am used to thinking of blues as lower
>> values, and reds as higher. The yellow at the end throws me off a bit,
>> because I would think of it as a "weaker" color. Maybe if it was more
>> gold-like?
>>
>> We should also start thinking of a snazzy name. BlRdYe probably won't cut
>> it.
>>
>> Ben Root
>> On Apr 5, 2015 3:21 AM, "Nathaniel Smith" <nj...@po...> wrote:
>>
>>> On Mon, Feb 23, 2015 at 10:46 AM, Eric Firing <ef...@ha...>
>>> wrote:
>>> > On 2015年02月18日 2:39 PM, Nathaniel Smith wrote:
>>> >>
>>> >> On Feb 16, 2015 3:39 PM, "Eric Firing" <ef...@ha...> wrote:
>>> >>>
>>> >>>
>>> >>> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
>>> >>>
>>> >>>> Nathaniel's January 9 message in that thread (can't figure out how
>>> to
>>> >>>> link to it in the archives) had a suggestion that I thought was very
>>> >>>> promising, to do something similar to Parula but rotate around the
>>> hue
>>> >>>> circle the other direction so that the hues would go blue - purple
>>> - red
>>> >>>> - yellow. I don't think we've seen an example of exactly what it
>>> would
>>> >>>> look like, but I reckon it would be similar to the middle colormap
>>> here
>>> >>>>
>>> >>>>
>>> http://earthobservatory.nasa.gov/blogs/elegantfigures/files/2013/08/three_perceptual_palettes_618.png
>>> >>>> (from the elegant figures block series linked above), which I've
>>> always
>>> >>>> found quite attractive.
>>> >>>
>>> >>>
>>> >>> Certainly it can be considered--but we have to have a real
>>> >>> implementation.
>>> >>
>>> >>
>>> >> While I hate to promise vaporware, I actually was planning to have a
>>> >> go at implementing such a colormap in the next few weeks, based on
>>> >> optimizing the same set of parameters that viscm visualizes... FWIW.
>>> >
>>> >
>>> > It might be worth quite a bit--and the sooner, the better.
>>>
>>> While it's taking longer than hoped, just to reassure you that this
>>> isn't total vaporware, here's a screenshot from the colormap designer
>>> that Stéfan van der Walt and I have been working on... still needs
>>> fine-tuning (which at this point probably won't happen until after I
>>> get back from PyCon), but we like what we're seeing so far :-)
>>>
>>> The colormap shown has, by construction, perfect lightness linearity
>>> and perfect perceptual uniformity, according to the better-than-CIELAB
>>> model used by the viscm tool I linked upthread.
>>>
>>> --
>>> Nathaniel J. Smith -- http://vorpus.org
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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 Apr 5, 2015 8:29 PM, "gary ruben" <gar...@gm...> wrote:
>
> Just wondering whether anyone has suggested checking candidate colormaps
against typical printer color gamuts?
How would you go about doing this in practice? Is it even possible to
choose a subset of sRGB space and have printers take advantage of that when
doing gamut mapping? (I guess I always assumed that printer gamut mapping
applied to an RGB image would map all of RGB into their gamut, so there
would be no advantage to restricting oneself go a subspace. But maybe I'm
wrong -- color management is pretty fancy these days.)
-n

Just wondering whether anyone has suggested checking candidate colormaps
against typical printer color gamuts?
On 6 Apr 2015 1:11 pm, "Eric Firing" <ef...@ha...> wrote:
> On 2015年04月04日 10:10 PM, Nathaniel Smith wrote:
>
>> We'd welcome any feedback from readers with non-simulated color
>> deficiency!
>>
>
> I checked with my red-green color-blind colleague, Niklas Schneider, and
> his evaluation is attached.
>
> Eric
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

On 2015年04月04日 10:10 PM, Nathaniel Smith wrote:
> We'd welcome any feedback from readers with non-simulated color deficiency!
I checked with my red-green color-blind colleague, Niklas Schneider, and 
his evaluation is attached.
Eric

I like it, but perhaps we should condense it to one word for ease of 
typing, how about "Redgauntlet"? It kind of feels appropriate (for 
those who need an explanation of why, see 
https://www.youtube.com/watch?v=_guKhYVr5vA).
On the colormap itself, it looks good apart from the fade into blue, my 
eyes on this laptop monitor see a sharp gradient around 0.2 compared 
with the more gradual gradient at the other end. Also I see constant 
colour between 0 and 0.1, and between 0.9 and 1, with less change 
between 0.8 to 0.9 then 0.1 and 0.2. Not sure if one causes an optical 
illusion in the other or not.
Finally a bit confused as to what all the lines mean, any chance of some 
annotation? Also I would find it helpful to see a version without the 
big red line and what it looks like in practice (see the doc for the 
test script).
Best,
OceanWolf
On 05/04/15 23:18, Olga Botvinnik wrote:
> How about "pythonic sunset" ?
>
> On Sun, Apr 5, 2015 at 2:01 PM Benjamin Root <ben...@ou... 
> <mailto:ben...@ou...>> wrote:
>
> That is nice. The blue is a bit heavy, but that might be my
> display. Now, how should we order it by default? I am used to
> thinking of blues as lower values, and reds as higher. The yellow
> at the end throws me off a bit, because I would think of it as a
> "weaker" color. Maybe if it was more gold-like?
>
> We should also start thinking of a snazzy name. BlRdYe probably
> won't cut it.
>
> Ben Root
>
> On Apr 5, 2015 3:21 AM, "Nathaniel Smith" <nj...@po...
> <mailto:nj...@po...>> wrote:
>
> On Mon, Feb 23, 2015 at 10:46 AM, Eric Firing
> <ef...@ha... <mailto:ef...@ha...>> wrote:
> > On 2015年02月18日 2:39 PM, Nathaniel Smith wrote:
> >>
> >> On Feb 16, 2015 3:39 PM, "Eric Firing" <ef...@ha...
> <mailto:ef...@ha...>> wrote:
> >>>
> >>>
> >>> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
> >>>
> >>>> Nathaniel's January 9 message in that thread (can't
> figure out how to
> >>>> link to it in the archives) had a suggestion that I
> thought was very
> >>>> promising, to do something similar to Parula but rotate
> around the hue
> >>>> circle the other direction so that the hues would go blue
> - purple - red
> >>>> - yellow. I don't think we've seen an example of exactly
> what it would
> >>>> look like, but I reckon it would be similar to the middle
> colormap here
> >>>>
> >>>>
> http://earthobservatory.nasa.gov/blogs/elegantfigures/files/2013/08/three_perceptual_palettes_618.png
> >>>> (from the elegant figures block series linked above),
> which I've always
> >>>> found quite attractive.
> >>>
> >>>
> >>> Certainly it can be considered--but we have to have a real
> >>> implementation.
> >>
> >>
> >> While I hate to promise vaporware, I actually was planning
> to have a
> >> go at implementing such a colormap in the next few weeks,
> based on
> >> optimizing the same set of parameters that viscm
> visualizes... FWIW.
> >
> >
> > It might be worth quite a bit--and the sooner, the better.
>
> While it's taking longer than hoped, just to reassure you that
> this
> isn't total vaporware, here's a screenshot from the colormap
> designer
> that Stéfan van der Walt and I have been working on... still needs
> fine-tuning (which at this point probably won't happen until
> after I
> get back from PyCon), but we like what we're seeing so far :-)
>
> The colormap shown has, by construction, perfect lightness
> linearity
> and perfect perceptual uniformity, according to the
> better-than-CIELAB
> model used by the viscm tool I linked upthread.
>
> --
> Nathaniel J. Smith -- http://vorpus.org
>
> ------------------------------------------------------------------------------
> 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...
> <mailto: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...
> <mailto: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

How about "pythonic sunset" ?
On Sun, Apr 5, 2015 at 2:01 PM Benjamin Root <ben...@ou...> wrote:
> That is nice. The blue is a bit heavy, but that might be my display. Now,
> how should we order it by default? I am used to thinking of blues as lower
> values, and reds as higher. The yellow at the end throws me off a bit,
> because I would think of it as a "weaker" color. Maybe if it was more
> gold-like?
>
> We should also start thinking of a snazzy name. BlRdYe probably won't cut
> it.
>
> Ben Root
> On Apr 5, 2015 3:21 AM, "Nathaniel Smith" <nj...@po...> wrote:
>
>> On Mon, Feb 23, 2015 at 10:46 AM, Eric Firing <ef...@ha...> wrote:
>> > On 2015年02月18日 2:39 PM, Nathaniel Smith wrote:
>> >>
>> >> On Feb 16, 2015 3:39 PM, "Eric Firing" <ef...@ha...> wrote:
>> >>>
>> >>>
>> >>> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
>> >>>
>> >>>> Nathaniel's January 9 message in that thread (can't figure out how to
>> >>>> link to it in the archives) had a suggestion that I thought was very
>> >>>> promising, to do something similar to Parula but rotate around the
>> hue
>> >>>> circle the other direction so that the hues would go blue - purple -
>> red
>> >>>> - yellow. I don't think we've seen an example of exactly what it
>> would
>> >>>> look like, but I reckon it would be similar to the middle colormap
>> here
>> >>>>
>> >>>>
>> http://earthobservatory.nasa.gov/blogs/elegantfigures/files/2013/08/three_perceptual_palettes_618.png
>> >>>> (from the elegant figures block series linked above), which I've
>> always
>> >>>> found quite attractive.
>> >>>
>> >>>
>> >>> Certainly it can be considered--but we have to have a real
>> >>> implementation.
>> >>
>> >>
>> >> While I hate to promise vaporware, I actually was planning to have a
>> >> go at implementing such a colormap in the next few weeks, based on
>> >> optimizing the same set of parameters that viscm visualizes... FWIW.
>> >
>> >
>> > It might be worth quite a bit--and the sooner, the better.
>>
>> While it's taking longer than hoped, just to reassure you that this
>> isn't total vaporware, here's a screenshot from the colormap designer
>> that Stéfan van der Walt and I have been working on... still needs
>> fine-tuning (which at this point probably won't happen until after I
>> get back from PyCon), but we like what we're seeing so far :-)
>>
>> The colormap shown has, by construction, perfect lightness linearity
>> and perfect perceptual uniformity, according to the better-than-CIELAB
>> model used by the viscm tool I linked upthread.
>>
>> --
>> Nathaniel J. Smith -- http://vorpus.org
>>
>>
>> ------------------------------------------------------------------------------
>> 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 nice. The blue is a bit heavy, but that might be my display. Now,
how should we order it by default? I am used to thinking of blues as lower
values, and reds as higher. The yellow at the end throws me off a bit,
because I would think of it as a "weaker" color. Maybe if it was more
gold-like?
We should also start thinking of a snazzy name. BlRdYe probably won't cut
it.
Ben Root
On Apr 5, 2015 3:21 AM, "Nathaniel Smith" <nj...@po...> wrote:
> On Mon, Feb 23, 2015 at 10:46 AM, Eric Firing <ef...@ha...> wrote:
> > On 2015年02月18日 2:39 PM, Nathaniel Smith wrote:
> >>
> >> On Feb 16, 2015 3:39 PM, "Eric Firing" <ef...@ha...> wrote:
> >>>
> >>>
> >>> On 2015年02月16日 1:29 PM, Michael Waskom wrote:
> >>>
> >>>> Nathaniel's January 9 message in that thread (can't figure out how to
> >>>> link to it in the archives) had a suggestion that I thought was very
> >>>> promising, to do something similar to Parula but rotate around the hue
> >>>> circle the other direction so that the hues would go blue - purple -
> red
> >>>> - yellow. I don't think we've seen an example of exactly what it would
> >>>> look like, but I reckon it would be similar to the middle colormap
> here
> >>>>
> >>>>
> http://earthobservatory.nasa.gov/blogs/elegantfigures/files/2013/08/three_perceptual_palettes_618.png
> >>>> (from the elegant figures block series linked above), which I've
> always
> >>>> found quite attractive.
> >>>
> >>>
> >>> Certainly it can be considered--but we have to have a real
> >>> implementation.
> >>
> >>
> >> While I hate to promise vaporware, I actually was planning to have a
> >> go at implementing such a colormap in the next few weeks, based on
> >> optimizing the same set of parameters that viscm visualizes... FWIW.
> >
> >
> > It might be worth quite a bit--and the sooner, the better.
>
> While it's taking longer than hoped, just to reassure you that this
> isn't total vaporware, here's a screenshot from the colormap designer
> that Stéfan van der Walt and I have been working on... still needs
> fine-tuning (which at this point probably won't happen until after I
> get back from PyCon), but we like what we're seeing so far :-)
>
> The colormap shown has, by construction, perfect lightness linearity
> and perfect perceptual uniformity, according to the better-than-CIELAB
> model used by the viscm tool I linked upthread.
>
> --
> Nathaniel J. Smith -- http://vorpus.org
>
>
> ------------------------------------------------------------------------------
> 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
>
>