From tcaswell at gmail.com  Fri Jan  1 17:33:12 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Fri, 01 Jan 2016 22:33:12 +0000
Subject: [Matplotlib-devel] plan for v1.5.1 release
Message-ID: <CAA48SF-aagokmR95=prw8KmkSMCuVKQ-UUToYEeoDLCDHozejw@mail.gmail.com>

Hey Folks,

I plan to cut an rc1 for mpl 1.5.1 tonight or tomorrow morning with a final
release aimed for mid-next week.  The only issue left tagged for 1.5.1
milestone
<https://github.com/matplotlib/matplotlib/milestones/Critical%20bugfix%20release%20(1.5.1)>
is
a text change to the main page.

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

From cgohlke at uci.edu  Fri Jan  1 22:34:37 2016
From: cgohlke at uci.edu (Christoph Gohlke)
Date: Fri, 1 Jan 2016 19:34:37 -0800
Subject: [Matplotlib-devel] plan for v1.5.1 release
In-Reply-To: <CAA48SF-aagokmR95=prw8KmkSMCuVKQ-UUToYEeoDLCDHozejw@mail.gmail.com>
References: <CAA48SF-aagokmR95=prw8KmkSMCuVKQ-UUToYEeoDLCDHozejw@mail.gmail.com>
Message-ID: <5687454D.2040604@uci.edu>

On 1/1/2016 2:33 PM, Thomas Caswell wrote:
> Hey Folks,
>
> I plan to cut an rc1 for mpl 1.5.1 tonight or tomorrow morning with a
> final release aimed for mid-next week.  The only issue left tagged for
> 1.5.1 milestone
> <https://github.com/matplotlib/matplotlib/milestones/Critical%20bugfix%20release%20%281.5.1%29> is
> a text change to the main page.
>
> Tom
>

Could PR #5460 be backported? It fixes two test errors on Windows.

https://github.com/matplotlib/matplotlib/pull/5460
https://github.com/matplotlib/matplotlib/issues/5446

Christoph

From tcaswell at gmail.com  Sat Jan  2 01:46:13 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 02 Jan 2016 06:46:13 +0000
Subject: [Matplotlib-devel] plan for v1.5.1 release
In-Reply-To: <5687454D.2040604@uci.edu>
References: <CAA48SF-aagokmR95=prw8KmkSMCuVKQ-UUToYEeoDLCDHozejw@mail.gmail.com>
 <5687454D.2040604@uci.edu>
Message-ID: <CAA48SF8aiT8Ou_DUUmfS5MwF5ZVnPbmrqfekyGCYgGz=3K_9+g@mail.gmail.com>

Done as
https://github.com/matplotlib/matplotlib/commit/2e9ff448fb139b45c58d5c2a3ab40e5aad606b4e

Sorry that did not get taken care of earlier and thank you for the gentle
reminder!

Tom

On Fri, Jan 1, 2016 at 10:36 PM Christoph Gohlke <cgohlke at uci.edu> wrote:

> On 1/1/2016 2:33 PM, Thomas Caswell wrote:
> > Hey Folks,
> >
> > I plan to cut an rc1 for mpl 1.5.1 tonight or tomorrow morning with a
> > final release aimed for mid-next week.  The only issue left tagged for
> > 1.5.1 milestone
> > <
> https://github.com/matplotlib/matplotlib/milestones/Critical%20bugfix%20release%20%281.5.1%29>
> is
> > a text change to the main page.
> >
> > Tom
> >
>
> Could PR #5460 be backported? It fixes two test errors on Windows.
>
> https://github.com/matplotlib/matplotlib/pull/5460
> https://github.com/matplotlib/matplotlib/issues/5446
>
> Christoph
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160102/1df447da/attachment.html>

From Nicolas.Rougier at inria.fr  Sat Jan  2 06:06:05 2016
From: Nicolas.Rougier at inria.fr (Nicolas P. Rougier)
Date: Sat, 2 Jan 2016 12:06:05 +0100
Subject: [Matplotlib-devel] article on scales
In-Reply-To: <CAH4pYpTPaq2w_d62iWyn=6k9rUrkoCADz-VHNAMA_H9gaaGmZA@mail.gmail.com>
References: <CAA48SF9k2efrEXudhsibNPTQq1KB7YOcGHn79Cx1oSFvGSJHCg@mail.gmail.com>
 <CAH4pYpTPaq2w_d62iWyn=6k9rUrkoCADz-VHNAMA_H9gaaGmZA@mail.gmail.com>
Message-ID: <9B968FA8-7309-40FB-B821-698C9874C650@inria.fr>



I?ve started some experiments at: https://github.com/rougier/pyd3

I?ve only implemented linear scales (pyd3.scale) so far, but it is a good start at showing what can be done because it also requires the d3-interpolate functions (pyd3.interpolate). Almost all (translated) D3 tests pass.


For example, you can write:

  >>> from pyd3 import interpolate
  >>> i = interpolate.value( {"bg": "red"}, {"bg": "green?} )
  >>> print(i(.5)
  >>> {"bg": "#804000?}


Also, I?ve used linear/power/log scales in glumpy and they are pretty useful (but implementation is only for the GPU).


Nicolas


> On 29 Dec 2015, at 00:10, Brian Granger <ellisonbg at gmail.com> wrote:
> 
> Nice, I would really like to see a nice python scale library that was
> independent of any particular viz package that everyone could start to
> use...
> 
> On Mon, Dec 28, 2015 at 11:17 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
>> There has been some discussion about how to generalize/unify the mixture of
>> scaling functionality in mpl (axes scales, color.norm, and the units
>> framework).  Mike Bostock has pulled the scale functionality out of d3 [1],
>> we might want to take a look at that for API inspiration (also scroll to the
>> bottom of the post and note what color maps he uses as demo :) ).
>> 
>> Tom
>> 
>> [1] https://medium.com/@mbostock/introducing-d3-scale-61980c51545f
>> 
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>> 
> 
> 
> 
> -- 
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgranger at calpoly.edu and ellisonbg at gmail.com
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel


From tcaswell at gmail.com  Sat Jan  2 16:56:22 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 02 Jan 2016 21:56:22 +0000
Subject: [Matplotlib-devel] ANN mpl v1.5.1rc1
Message-ID: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>

Hey Folks,

We are happy to announce the first RC for 1.5.1, the first bug-fix release
is the 1.5.x series, please kick the tires.  Given the scale of the changes
from 1.5.0 we are planning a short RC cycle with a 1.5.1 final tagged on
2016-01-06.

To see the differences between 1.5.0 and 1.5.1rc1
<https://github.com/matplotlib/matplotlib/compare/v1.5.0...v1.5.1rc1> .

We had not planned to do a 1.5.1 release, but the style changes for v2.0
revealed a number of critical issues which needed to be addressed.  The
time line for 2.0 is contingent on how well that work goes and if we
discover any other major work that needs to be done to support the default
style changes.  The goal is v2.0.0rc1 sometime in the Q1 of 2016 with a
long rc cycle to have as many users as possible try the new defaults prior
to tagging v2.

Thank you to everyone who reported bugs and fixes against v1.5.0.

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

From mdroettboom at continuum.io  Mon Jan  4 16:12:55 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Mon, 4 Jan 2016 16:12:55 -0500
Subject: [Matplotlib-devel] Matplotlib minutes 2016-01-04
Message-ID: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>

In attendance: Thomas Caswell, Michael Droettboom, Eric Firing, Jens Nielsen

- 1.5.1rc1 is out. (yay)  We missed a lot of Python 3 bugs that crept into
the examples because we (a) don't build the docs on Py3 and (b) many
examples don't run in docs build.  Running backend_driver.py before
releases may help, as would running examples as smoke tests as part of
regular test suite (though dependencies for everything on Travis may be
tricky).

- Image rewrite (#5718): The bboximage test is weird and should be sorted
out.  Image compositing should be performed *after* sorting for z-order so
the z-order between images and other artists isn't ignored.  Ben Root still
needs time to review C++ part.

- Dora will meet next week to discuss ideas for website/documentation
overhaul.

- The only major features for 2.1 are Traitlets and the GUI refactor
(merging of toolbar handling etc).  Possibly we may include a bunch of
Jupyter notebook-related changes in 2.1, and push Traitlets and GUI
refactor to 2.2.  There is concern that 2.1 is already too overloaded.

- 2.0 is nearing completion.  There are a bunch of small things, no obvious
large stuff on the horizon.  Anthony Lee's formatting and text offset work
will likely end up in 2.0.

- 2.0 will need a larger than normal rc cycle, with aggressive promotion
for testing and as many "easy" channels for installation as possible.

- More brainstorming about how to move #5674 forward were discussed, which
I plan to implement and move forward in the coming days.

Mike

-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160104/30034b9b/attachment.html>

From njs at pobox.com  Mon Jan  4 16:18:08 2016
From: njs at pobox.com (Nathaniel Smith)
Date: Mon, 4 Jan 2016 13:18:08 -0800
Subject: [Matplotlib-devel] Matplotlib minutes 2016-01-04
In-Reply-To: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
References: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
Message-ID: <CAPJVwB=-Q=Da=5w6DK7KYjFwyR7YxmZb56=eaJDvdTsNc2ApUw@mail.gmail.com>

On Jan 4, 2016 1:13 PM, "Michael Droettboom" <mdroettboom at continuum.io>
wrote:
>
> In attendance: Thomas Caswell, Michael Droettboom, Eric Firing, Jens
Nielsen
>
> - 1.5.1rc1 is out. (yay)  We missed a lot of Python 3 bugs that crept
into the examples because we (a) don't build the docs on Py3 and (b) many
examples don't run in docs build.  Running backend_driver.py before
releases may help, as would running examples as smoke tests as part of
regular test suite (though dependencies for everything on Travis may be
tricky).

Only somewhat related, but it might be time to consider switching to python
3 as the place where you build the docs, even.

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

From jenshnielsen at gmail.com  Mon Jan  4 16:24:33 2016
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Mon, 04 Jan 2016 21:24:33 +0000
Subject: [Matplotlib-devel] Matplotlib minutes 2016-01-04
In-Reply-To: <CAPJVwB=-Q=Da=5w6DK7KYjFwyR7YxmZb56=eaJDvdTsNc2ApUw@mail.gmail.com>
References: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
 <CAPJVwB=-Q=Da=5w6DK7KYjFwyR7YxmZb56=eaJDvdTsNc2ApUw@mail.gmail.com>
Message-ID: <CAM-Pw01QdxV30hmSsMxZeveqj6eaUV6cVvKDg3QPtZsJg=ER1g@mail.gmail.com>

Indeed we would like to build the docs with Python 3 see
https://github.com/matplotlib/matplotlib/pull/5338
It's basically only hold back by link checker not being compatible. We
could run that with a different python version

Jens

On Mon, 4 Jan 2016 at 21:19 Nathaniel Smith <njs at pobox.com> wrote:

> On Jan 4, 2016 1:13 PM, "Michael Droettboom" <mdroettboom at continuum.io>
> wrote:
> >
> > In attendance: Thomas Caswell, Michael Droettboom, Eric Firing, Jens
> Nielsen
> >
> > - 1.5.1rc1 is out. (yay)  We missed a lot of Python 3 bugs that crept
> into the examples because we (a) don't build the docs on Py3 and (b) many
> examples don't run in docs build.  Running backend_driver.py before
> releases may help, as would running examples as smoke tests as part of
> regular test suite (though dependencies for everything on Travis may be
> tricky).
>
> Only somewhat related, but it might be time to consider switching to
> python 3 as the place where you build the docs, even.
>
> -n
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160104/9df38171/attachment.html>

From ellisonbg at gmail.com  Mon Jan  4 16:46:45 2016
From: ellisonbg at gmail.com (Brian Granger)
Date: Mon, 4 Jan 2016 13:46:45 -0800
Subject: [Matplotlib-devel] Matplotlib minutes 2016-01-04
In-Reply-To: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
References: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
Message-ID: <CAH4pYpSeUtK5MtWQ33TmSh529SCzKfE3duzgZxd3Js8VV39aoQ@mail.gmail.com>

Thanks for the update!

On Mon, Jan 4, 2016 at 1:12 PM, Michael Droettboom
<mdroettboom at continuum.io> wrote:
> In attendance: Thomas Caswell, Michael Droettboom, Eric Firing, Jens Nielsen
>
> - 1.5.1rc1 is out. (yay)  We missed a lot of Python 3 bugs that crept into
> the examples because we (a) don't build the docs on Py3 and (b) many
> examples don't run in docs build.  Running backend_driver.py before releases
> may help, as would running examples as smoke tests as part of regular test
> suite (though dependencies for everything on Travis may be tricky).
>
> - Image rewrite (#5718): The bboximage test is weird and should be sorted
> out.  Image compositing should be performed *after* sorting for z-order so
> the z-order between images and other artists isn't ignored.  Ben Root still
> needs time to review C++ part.
>
> - Dora will meet next week to discuss ideas for website/documentation
> overhaul.
>
> - The only major features for 2.1 are Traitlets and the GUI refactor
> (merging of toolbar handling etc).  Possibly we may include a bunch of
> Jupyter notebook-related changes in 2.1, and push Traitlets and GUI refactor
> to 2.2.  There is concern that 2.1 is already too overloaded.
>
> - 2.0 is nearing completion.  There are a bunch of small things, no obvious
> large stuff on the horizon.  Anthony Lee's formatting and text offset work
> will likely end up in 2.0.
>
> - 2.0 will need a larger than normal rc cycle, with aggressive promotion for
> testing and as many "easy" channels for installation as possible.
>
> - More brainstorming about how to move #5674 forward were discussed, which I
> plan to implement and move forward in the coming days.
>
> Mike
>
> --
> Michael Droettboom
> Continuum Analytics
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com

From antony.lee at berkeley.edu  Mon Jan  4 18:48:08 2016
From: antony.lee at berkeley.edu (Antony Lee)
Date: Mon, 4 Jan 2016 15:48:08 -0800
Subject: [Matplotlib-devel] Help for testing unicode support on the MacOS
 backend
Message-ID: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>

Hi all,

As part of my rewrite of the Formatter classes (#5787), I am planning to
switch to always use `fix_minus` in the statusbar text (i.e., use a
typographically correct unicode "MINUS SIGN" rather than a dash for
negative numbers).

The original docstring on the topic was

    Some classes may want to replace a hyphen for minus with the
    proper unicode symbol (U+2212) for typographical correctness.
    The default is to not replace it.

    Note, if you use this method, e.g., in :meth:`format_data` or
    call, you probably don't want to use it for
    :meth:`format_data_short` since the toolbar uses this for
    interactive coord reporting and I doubt we can expect GUIs
    across platforms will handle the unicode correctly.  So for
    now the classes that override :meth:`fix_minus` should have an
    explicit :meth:`format_data_short` method

I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3 (Python3)
backends on Linux, as well as Tk and Qt4 (Python2) on Windows and they all
handle unicode fine.  Can someone try the MacOS backend for me?  You
basically need to patch ScalarFormatter.format_data_short (in ticker.py) to
wrap the returned values in `self.fix_minus`

    def format_data_short(self, value):
        """return a short formatted string representation of a number"""
        if self._useLocale:
            return self.fix_minus(locale.format_string('%-12g', (value,)))
        else:
            return self.fix_minus('%-12g' % value)

plot e.g. `plot([-1, 1])`, and check that the statusbar displays negative x
values properly (with a minus sign that's actually much more readable IMO).

Thanks,

Antony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160104/427c8776/attachment-0001.html>

From juichenieder-nabb at yahoo.co.uk  Mon Jan  4 20:55:28 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Tue, 5 Jan 2016 02:55:28 +0100
Subject: [Matplotlib-devel] Matplotlib minutes 2016-01-04
In-Reply-To: <CAH4pYpSeUtK5MtWQ33TmSh529SCzKfE3duzgZxd3Js8VV39aoQ@mail.gmail.com>
References: <CADsn3C2YBzgRQt9bYb+eJfrVWhNabf2+Xk6XNKSA9qP8t=n1Ug@mail.gmail.com>
 <CAH4pYpSeUtK5MtWQ33TmSh529SCzKfE3duzgZxd3Js8VV39aoQ@mail.gmail.com>
Message-ID: <568B2290.6000700@yahoo.co.uk>

Hmm, I see plans afoot for linkchecker to become python3 in the future, 
I see python3 fixes in the commit messages and in code comments, but 
these do date back to 2014, either he has fixed it for python3 and 
forgotten to update the docs, or he has gotten side-tracked...

On 04/01/16 22:46, Brian Granger wrote:
> Thanks for the update!
>
> On Mon, Jan 4, 2016 at 1:12 PM, Michael Droettboom
> <mdroettboom at continuum.io> wrote:
>> In attendance: Thomas Caswell, Michael Droettboom, Eric Firing, Jens Nielsen
>>
>> - 1.5.1rc1 is out. (yay)  We missed a lot of Python 3 bugs that crept into
>> the examples because we (a) don't build the docs on Py3 and (b) many
>> examples don't run in docs build.  Running backend_driver.py before releases
>> may help, as would running examples as smoke tests as part of regular test
>> suite (though dependencies for everything on Travis may be tricky).
>>
>> - Image rewrite (#5718): The bboximage test is weird and should be sorted
>> out.  Image compositing should be performed *after* sorting for z-order so
>> the z-order between images and other artists isn't ignored.  Ben Root still
>> needs time to review C++ part.
>>
>> - Dora will meet next week to discuss ideas for website/documentation
>> overhaul.
>>
>> - The only major features for 2.1 are Traitlets and the GUI refactor
>> (merging of toolbar handling etc).  Possibly we may include a bunch of
>> Jupyter notebook-related changes in 2.1, and push Traitlets and GUI refactor
>> to 2.2.  There is concern that 2.1 is already too overloaded.
>>
>> - 2.0 is nearing completion.  There are a bunch of small things, no obvious
>> large stuff on the horizon.  Anthony Lee's formatting and text offset work
>> will likely end up in 2.0.
>>
>> - 2.0 will need a larger than normal rc cycle, with aggressive promotion for
>> testing and as many "easy" channels for installation as possible.
>>
>> - More brainstorming about how to move #5674 forward were discussed, which I
>> plan to implement and move forward in the coming days.
>>
>> Mike
>>
>> --
>> Michael Droettboom
>> Continuum Analytics
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
>


From antony.lee at berkeley.edu  Tue Jan  5 08:31:00 2016
From: antony.lee at berkeley.edu (Antony Lee)
Date: Tue, 5 Jan 2016 05:31:00 -0800
Subject: [Matplotlib-devel] Straw poll on default offset text precision
Message-ID: <CAGRr6BHDXM5uOPGhmUwdfVtSVRCduVg0qJF8_45=-Fd0aRjuDA@mail.gmail.com>

Currently, after e.g. `plot([10000000, 10000010])`, the y-axis is labeled
"0, ..., 10 + 1e7".  The physicist in me always thought that this was
inelegant, as the offset is specified with much less precision than the
increments.

Yes, I know, there are physical cases where this makes sense, but here this
is really just due to "sloppy" formatting: after `plot([12345671,
12345678])`, the y-axis is labeled "0, ..., 7 + 1.2345671e7", so both the
offset and the increments have the same precision (ideally, perhaps the
offset should be written with the same exponent as the increments, so just
1,234,567 here).

Although the issue is "relatively" easy to fix, this will give rise to a
lot of zeros in pathological cases such as `plot([.5, .50000001])`
(currently 0, ..., 1 x 1e-8 + 5e-1, but 0, ..., 1 x 1e-8 + 0.50000000 after
the change).  But again, perhaps it makes more sense to actually display
these zeros.

Thoughts?

Antony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/3443ab82/attachment.html>

From mdroettboom at continuum.io  Tue Jan  5 09:06:40 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Tue, 5 Jan 2016 09:06:40 -0500
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
Message-ID: <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>

The Mac OSX backend seems to work just fine.

That docstring comment goes back to 2008, and the OSS GUI frameworks and
Python 3 etc. have made great strides with Unicode support since then.  We
should probably just remove it along with your proposed change.

Mike

On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu> wrote:

> Hi all,
>
> As part of my rewrite of the Formatter classes (#5787), I am planning to
> switch to always use `fix_minus` in the statusbar text (i.e., use a
> typographically correct unicode "MINUS SIGN" rather than a dash for
> negative numbers).
>
> The original docstring on the topic was
>
>     Some classes may want to replace a hyphen for minus with the
>     proper unicode symbol (U+2212) for typographical correctness.
>     The default is to not replace it.
>
>     Note, if you use this method, e.g., in :meth:`format_data` or
>     call, you probably don't want to use it for
>     :meth:`format_data_short` since the toolbar uses this for
>     interactive coord reporting and I doubt we can expect GUIs
>     across platforms will handle the unicode correctly.  So for
>     now the classes that override :meth:`fix_minus` should have an
>     explicit :meth:`format_data_short` method
>
> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
> they all handle unicode fine.  Can someone try the MacOS backend for me?
> You basically need to patch ScalarFormatter.format_data_short (in
> ticker.py) to wrap the returned values in `self.fix_minus`
>
>     def format_data_short(self, value):
>         """return a short formatted string representation of a number"""
>         if self._useLocale:
>             return self.fix_minus(locale.format_string('%-12g', (value,)))
>         else:
>             return self.fix_minus('%-12g' % value)
>
> plot e.g. `plot([-1, 1])`, and check that the statusbar displays negative
> x values properly (with a minus sign that's actually much more readable
> IMO).
>
> Thanks,
>
> Antony
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/465049ab/attachment.html>

From jenshnielsen at gmail.com  Tue Jan  5 09:11:08 2016
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Tue, 05 Jan 2016 14:11:08 +0000
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
 <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
Message-ID: <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>

We should be careful about the PySide QT4 backend and unicode. See
https://github.com/matplotlib/matplotlib/pull/5690

best
Jens

On Tue, 5 Jan 2016 at 14:06 Michael Droettboom <mdroettboom at continuum.io>
wrote:

> The Mac OSX backend seems to work just fine.
>
> That docstring comment goes back to 2008, and the OSS GUI frameworks and
> Python 3 etc. have made great strides with Unicode support since then.  We
> should probably just remove it along with your proposed change.
>
> Mike
>
> On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu>
> wrote:
>
>> Hi all,
>>
>> As part of my rewrite of the Formatter classes (#5787), I am planning to
>> switch to always use `fix_minus` in the statusbar text (i.e., use a
>> typographically correct unicode "MINUS SIGN" rather than a dash for
>> negative numbers).
>>
>> The original docstring on the topic was
>>
>>     Some classes may want to replace a hyphen for minus with the
>>     proper unicode symbol (U+2212) for typographical correctness.
>>     The default is to not replace it.
>>
>>     Note, if you use this method, e.g., in :meth:`format_data` or
>>     call, you probably don't want to use it for
>>     :meth:`format_data_short` since the toolbar uses this for
>>     interactive coord reporting and I doubt we can expect GUIs
>>     across platforms will handle the unicode correctly.  So for
>>     now the classes that override :meth:`fix_minus` should have an
>>     explicit :meth:`format_data_short` method
>>
>> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
>> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
>> they all handle unicode fine.  Can someone try the MacOS backend for me?
>> You basically need to patch ScalarFormatter.format_data_short (in
>> ticker.py) to wrap the returned values in `self.fix_minus`
>>
>>     def format_data_short(self, value):
>>         """return a short formatted string representation of a number"""
>>         if self._useLocale:
>>             return self.fix_minus(locale.format_string('%-12g', (value,)))
>>         else:
>>             return self.fix_minus('%-12g' % value)
>>
>> plot e.g. `plot([-1, 1])`, and check that the statusbar displays negative
>> x values properly (with a minus sign that's actually much more readable
>> IMO).
>>
>> Thanks,
>>
>> Antony
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Michael Droettboom
> Continuum Analytics
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/ae07c9bf/attachment-0001.html>

From antony.lee at berkeley.edu  Tue Jan  5 09:26:38 2016
From: antony.lee at berkeley.edu (Antony Lee)
Date: Tue, 5 Jan 2016 06:26:38 -0800
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
 <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
 <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>
Message-ID: <CAGRr6BGy5ULWqAzV-guD20hXYX4JifGY+M8OmzEKmaak3VaZ=Q@mail.gmail.com>

Works with PySide Py2/Py3 (on Linux).

2016-01-05 6:11 GMT-08:00 Jens Nielsen <jenshnielsen at gmail.com>:

> We should be careful about the PySide QT4 backend and unicode. See
> https://github.com/matplotlib/matplotlib/pull/5690
>
> best
> Jens
>
> On Tue, 5 Jan 2016 at 14:06 Michael Droettboom <mdroettboom at continuum.io>
> wrote:
>
>> The Mac OSX backend seems to work just fine.
>>
>> That docstring comment goes back to 2008, and the OSS GUI frameworks and
>> Python 3 etc. have made great strides with Unicode support since then.  We
>> should probably just remove it along with your proposed change.
>>
>> Mike
>>
>> On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu>
>> wrote:
>>
>>> Hi all,
>>>
>>> As part of my rewrite of the Formatter classes (#5787), I am planning to
>>> switch to always use `fix_minus` in the statusbar text (i.e., use a
>>> typographically correct unicode "MINUS SIGN" rather than a dash for
>>> negative numbers).
>>>
>>> The original docstring on the topic was
>>>
>>>     Some classes may want to replace a hyphen for minus with the
>>>     proper unicode symbol (U+2212) for typographical correctness.
>>>     The default is to not replace it.
>>>
>>>     Note, if you use this method, e.g., in :meth:`format_data` or
>>>     call, you probably don't want to use it for
>>>     :meth:`format_data_short` since the toolbar uses this for
>>>     interactive coord reporting and I doubt we can expect GUIs
>>>     across platforms will handle the unicode correctly.  So for
>>>     now the classes that override :meth:`fix_minus` should have an
>>>     explicit :meth:`format_data_short` method
>>>
>>> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
>>> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
>>> they all handle unicode fine.  Can someone try the MacOS backend for me?
>>> You basically need to patch ScalarFormatter.format_data_short (in
>>> ticker.py) to wrap the returned values in `self.fix_minus`
>>>
>>>     def format_data_short(self, value):
>>>         """return a short formatted string representation of a number"""
>>>         if self._useLocale:
>>>             return self.fix_minus(locale.format_string('%-12g',
>>> (value,)))
>>>         else:
>>>             return self.fix_minus('%-12g' % value)
>>>
>>> plot e.g. `plot([-1, 1])`, and check that the statusbar displays
>>> negative x values properly (with a minus sign that's actually much more
>>> readable IMO).
>>>
>>> Thanks,
>>>
>>> Antony
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>>
>>
>>
>> --
>> Michael Droettboom
>> Continuum Analytics
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/9b0f3cb2/attachment.html>

From jenshnielsen at gmail.com  Tue Jan  5 09:42:07 2016
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Tue, 05 Jan 2016 14:42:07 +0000
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CAGRr6BGy5ULWqAzV-guD20hXYX4JifGY+M8OmzEKmaak3VaZ=Q@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
 <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
 <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>
 <CAGRr6BGy5ULWqAzV-guD20hXYX4JifGY+M8OmzEKmaak3VaZ=Q@mail.gmail.com>
Message-ID: <CAM-Pw00hH3kqfZZJvwc7fRsyrAx1FwpW+rGxkrpj62vkZbNueg@mail.gmail.com>

Great, Sounds like that is every backend then

Jens

On Tue, 5 Jan 2016 at 14:26 Antony Lee <antony.lee at berkeley.edu> wrote:

> Works with PySide Py2/Py3 (on Linux).
>
> 2016-01-05 6:11 GMT-08:00 Jens Nielsen <jenshnielsen at gmail.com>:
>
>> We should be careful about the PySide QT4 backend and unicode. See
>> https://github.com/matplotlib/matplotlib/pull/5690
>>
>> best
>> Jens
>>
>> On Tue, 5 Jan 2016 at 14:06 Michael Droettboom <mdroettboom at continuum.io>
>> wrote:
>>
>>> The Mac OSX backend seems to work just fine.
>>>
>>> That docstring comment goes back to 2008, and the OSS GUI frameworks and
>>> Python 3 etc. have made great strides with Unicode support since then.  We
>>> should probably just remove it along with your proposed change.
>>>
>>> Mike
>>>
>>> On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> As part of my rewrite of the Formatter classes (#5787), I am planning
>>>> to switch to always use `fix_minus` in the statusbar text (i.e., use a
>>>> typographically correct unicode "MINUS SIGN" rather than a dash for
>>>> negative numbers).
>>>>
>>>> The original docstring on the topic was
>>>>
>>>>     Some classes may want to replace a hyphen for minus with the
>>>>     proper unicode symbol (U+2212) for typographical correctness.
>>>>     The default is to not replace it.
>>>>
>>>>     Note, if you use this method, e.g., in :meth:`format_data` or
>>>>     call, you probably don't want to use it for
>>>>     :meth:`format_data_short` since the toolbar uses this for
>>>>     interactive coord reporting and I doubt we can expect GUIs
>>>>     across platforms will handle the unicode correctly.  So for
>>>>     now the classes that override :meth:`fix_minus` should have an
>>>>     explicit :meth:`format_data_short` method
>>>>
>>>> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
>>>> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
>>>> they all handle unicode fine.  Can someone try the MacOS backend for me?
>>>> You basically need to patch ScalarFormatter.format_data_short (in
>>>> ticker.py) to wrap the returned values in `self.fix_minus`
>>>>
>>>>     def format_data_short(self, value):
>>>>         """return a short formatted string representation of a number"""
>>>>         if self._useLocale:
>>>>             return self.fix_minus(locale.format_string('%-12g',
>>>> (value,)))
>>>>         else:
>>>>             return self.fix_minus('%-12g' % value)
>>>>
>>>> plot e.g. `plot([-1, 1])`, and check that the statusbar displays
>>>> negative x values properly (with a minus sign that's actually much more
>>>> readable IMO).
>>>>
>>>> Thanks,
>>>>
>>>> Antony
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at python.org
>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>>
>>>
>>>
>>> --
>>> Michael Droettboom
>>> Continuum Analytics
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/8a427c39/attachment.html>

From efiring at hawaii.edu  Tue Jan  5 13:17:49 2016
From: efiring at hawaii.edu (Eric Firing)
Date: Tue, 5 Jan 2016 08:17:49 -1000
Subject: [Matplotlib-devel] Straw poll on default offset text precision
In-Reply-To: <CAGRr6BHDXM5uOPGhmUwdfVtSVRCduVg0qJF8_45=-Fd0aRjuDA@mail.gmail.com>
References: <CAGRr6BHDXM5uOPGhmUwdfVtSVRCduVg0qJF8_45=-Fd0aRjuDA@mail.gmail.com>
Message-ID: <568C08CD.4000408@hawaii.edu>

On 2016/01/05 3:31 AM, Antony Lee wrote:
> Currently, after e.g. `plot([10000000, 10000010])`, the y-axis is
> labeled "0, ..., 10 + 1e7".  The physicist in me always thought that
> this was inelegant, as the offset is specified with much less precision
> than the increments.
>
> Yes, I know, there are physical cases where this makes sense, but here
> this is really just due to "sloppy" formatting: after `plot([12345671,
> 12345678])`, the y-axis is labeled "0, ..., 7 + 1.2345671e7", so both
> the offset and the increments have the same precision (ideally, perhaps
> the offset should be written with the same exponent as the increments,
> so just 1,234,567 here).
>
> Although the issue is "relatively" easy to fix, this will give rise to a
> lot of zeros in pathological cases such as `plot([.5, .50000001])`
> (currently 0, ..., 1 x 1e-8 + 5e-1, but 0, ..., 1 x 1e-8 + 0.50000000
> after the change).  But again, perhaps it makes more sense to actually
> display these zeros.

I don't think that displaying those zeros is a net gain, but I don't 
feel strongly either way.

Eric

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


From chris.barker at noaa.gov  Tue Jan  5 15:49:28 2016
From: chris.barker at noaa.gov (Chris Barker)
Date: Tue, 5 Jan 2016 12:49:28 -0800
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CAM-Pw00hH3kqfZZJvwc7fRsyrAx1FwpW+rGxkrpj62vkZbNueg@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
 <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
 <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>
 <CAGRr6BGy5ULWqAzV-guD20hXYX4JifGY+M8OmzEKmaak3VaZ=Q@mail.gmail.com>
 <CAM-Pw00hH3kqfZZJvwc7fRsyrAx1FwpW+rGxkrpj62vkZbNueg@mail.gmail.com>
Message-ID: <CALGmxELRdWVsZY6Q4GODMJtXdFLeUQx7JT69ZT=FfjaBN3-rwQ@mail.gmail.com>

On Tue, Jan 5, 2016 at 6:42 AM, Jens Nielsen <jenshnielsen at gmail.com> wrote:

> Great, Sounds like that is every backend then
>

Anyone try wxPython? It should be fine, but worth a check.

-CHB



>
> Jens
>
> On Tue, 5 Jan 2016 at 14:26 Antony Lee <antony.lee at berkeley.edu> wrote:
>
>> Works with PySide Py2/Py3 (on Linux).
>>
>> 2016-01-05 6:11 GMT-08:00 Jens Nielsen <jenshnielsen at gmail.com>:
>>
>>> We should be careful about the PySide QT4 backend and unicode. See
>>> https://github.com/matplotlib/matplotlib/pull/5690
>>>
>>> best
>>> Jens
>>>
>>> On Tue, 5 Jan 2016 at 14:06 Michael Droettboom <mdroettboom at continuum.io>
>>> wrote:
>>>
>>>> The Mac OSX backend seems to work just fine.
>>>>
>>>> That docstring comment goes back to 2008, and the OSS GUI frameworks
>>>> and Python 3 etc. have made great strides with Unicode support since then.
>>>> We should probably just remove it along with your proposed change.
>>>>
>>>> Mike
>>>>
>>>> On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> As part of my rewrite of the Formatter classes (#5787), I am planning
>>>>> to switch to always use `fix_minus` in the statusbar text (i.e., use a
>>>>> typographically correct unicode "MINUS SIGN" rather than a dash for
>>>>> negative numbers).
>>>>>
>>>>> The original docstring on the topic was
>>>>>
>>>>>     Some classes may want to replace a hyphen for minus with the
>>>>>     proper unicode symbol (U+2212) for typographical correctness.
>>>>>     The default is to not replace it.
>>>>>
>>>>>     Note, if you use this method, e.g., in :meth:`format_data` or
>>>>>     call, you probably don't want to use it for
>>>>>     :meth:`format_data_short` since the toolbar uses this for
>>>>>     interactive coord reporting and I doubt we can expect GUIs
>>>>>     across platforms will handle the unicode correctly.  So for
>>>>>     now the classes that override :meth:`fix_minus` should have an
>>>>>     explicit :meth:`format_data_short` method
>>>>>
>>>>> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
>>>>> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
>>>>> they all handle unicode fine.  Can someone try the MacOS backend for me?
>>>>> You basically need to patch ScalarFormatter.format_data_short (in
>>>>> ticker.py) to wrap the returned values in `self.fix_minus`
>>>>>
>>>>>     def format_data_short(self, value):
>>>>>         """return a short formatted string representation of a
>>>>> number"""
>>>>>         if self._useLocale:
>>>>>             return self.fix_minus(locale.format_string('%-12g',
>>>>> (value,)))
>>>>>         else:
>>>>>             return self.fix_minus('%-12g' % value)
>>>>>
>>>>> plot e.g. `plot([-1, 1])`, and check that the statusbar displays
>>>>> negative x values properly (with a minus sign that's actually much more
>>>>> readable IMO).
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Antony
>>>>>
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing list
>>>>> Matplotlib-devel at python.org
>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Michael Droettboom
>>>> Continuum Analytics
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at python.org
>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>
>>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/ce3180fd/attachment.html>

From antony.lee at berkeley.edu  Tue Jan  5 17:31:00 2016
From: antony.lee at berkeley.edu (Antony Lee)
Date: Tue, 5 Jan 2016 14:31:00 -0800
Subject: [Matplotlib-devel] Help for testing unicode support on the
 MacOS backend
In-Reply-To: <CALGmxELRdWVsZY6Q4GODMJtXdFLeUQx7JT69ZT=FfjaBN3-rwQ@mail.gmail.com>
References: <CAGRr6BGGt0SMvrp55bjSHsSUdX_zyVzu-JJTa_WsBPQwRs828Q@mail.gmail.com>
 <CADsn3C24-sbv7opAUtp6AguT=y-0vGksGjmUOrK7OhiCYhr90w@mail.gmail.com>
 <CAM-Pw01cJOByJafZVXYiPGZH6LorHQ_dhHDYxN0OWd3YLuk2GQ@mail.gmail.com>
 <CAGRr6BGy5ULWqAzV-guD20hXYX4JifGY+M8OmzEKmaak3VaZ=Q@mail.gmail.com>
 <CAM-Pw00hH3kqfZZJvwc7fRsyrAx1FwpW+rGxkrpj62vkZbNueg@mail.gmail.com>
 <CALGmxELRdWVsZY6Q4GODMJtXdFLeUQx7JT69ZT=FfjaBN3-rwQ@mail.gmail.com>
Message-ID: <CAGRr6BEsFzcrdmx5UPq8=8U2SzSuA7oHvv_eKaNfMyX5Uyo9zA@mail.gmail.com>

wxPython/Python2 works.  If someone has a working installation of
Phoenix/Python3 that'll save me some headaches...
Antony

2016-01-05 12:49 GMT-08:00 Chris Barker <chris.barker at noaa.gov>:

>
>
> On Tue, Jan 5, 2016 at 6:42 AM, Jens Nielsen <jenshnielsen at gmail.com>
> wrote:
>
>> Great, Sounds like that is every backend then
>>
>
> Anyone try wxPython? It should be fine, but worth a check.
>
> -CHB
>
>
>
>>
>> Jens
>>
>> On Tue, 5 Jan 2016 at 14:26 Antony Lee <antony.lee at berkeley.edu> wrote:
>>
>>> Works with PySide Py2/Py3 (on Linux).
>>>
>>> 2016-01-05 6:11 GMT-08:00 Jens Nielsen <jenshnielsen at gmail.com>:
>>>
>>>> We should be careful about the PySide QT4 backend and unicode. See
>>>> https://github.com/matplotlib/matplotlib/pull/5690
>>>>
>>>> best
>>>> Jens
>>>>
>>>> On Tue, 5 Jan 2016 at 14:06 Michael Droettboom <
>>>> mdroettboom at continuum.io> wrote:
>>>>
>>>>> The Mac OSX backend seems to work just fine.
>>>>>
>>>>> That docstring comment goes back to 2008, and the OSS GUI frameworks
>>>>> and Python 3 etc. have made great strides with Unicode support since then.
>>>>> We should probably just remove it along with your proposed change.
>>>>>
>>>>> Mike
>>>>>
>>>>> On Mon, Jan 4, 2016 at 6:48 PM, Antony Lee <antony.lee at berkeley.edu>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> As part of my rewrite of the Formatter classes (#5787), I am planning
>>>>>> to switch to always use `fix_minus` in the statusbar text (i.e., use a
>>>>>> typographically correct unicode "MINUS SIGN" rather than a dash for
>>>>>> negative numbers).
>>>>>>
>>>>>> The original docstring on the topic was
>>>>>>
>>>>>>     Some classes may want to replace a hyphen for minus with the
>>>>>>     proper unicode symbol (U+2212) for typographical correctness.
>>>>>>     The default is to not replace it.
>>>>>>
>>>>>>     Note, if you use this method, e.g., in :meth:`format_data` or
>>>>>>     call, you probably don't want to use it for
>>>>>>     :meth:`format_data_short` since the toolbar uses this for
>>>>>>     interactive coord reporting and I doubt we can expect GUIs
>>>>>>     across platforms will handle the unicode correctly.  So for
>>>>>>     now the classes that override :meth:`fix_minus` should have an
>>>>>>     explicit :meth:`format_data_short` method
>>>>>>
>>>>>> I have tried the Tk, Qt4, Qt5 (Python2/3), Gtk (Python2) and Gtk3
>>>>>> (Python3) backends on Linux, as well as Tk and Qt4 (Python2) on Windows and
>>>>>> they all handle unicode fine.  Can someone try the MacOS backend for me?
>>>>>> You basically need to patch ScalarFormatter.format_data_short (in
>>>>>> ticker.py) to wrap the returned values in `self.fix_minus`
>>>>>>
>>>>>>     def format_data_short(self, value):
>>>>>>         """return a short formatted string representation of a
>>>>>> number"""
>>>>>>         if self._useLocale:
>>>>>>             return self.fix_minus(locale.format_string('%-12g',
>>>>>> (value,)))
>>>>>>         else:
>>>>>>             return self.fix_minus('%-12g' % value)
>>>>>>
>>>>>> plot e.g. `plot([-1, 1])`, and check that the statusbar displays
>>>>>> negative x values properly (with a minus sign that's actually much more
>>>>>> readable IMO).
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Antony
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matplotlib-devel mailing list
>>>>>> Matplotlib-devel at python.org
>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Droettboom
>>>>> Continuum Analytics
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing list
>>>>> Matplotlib-devel at python.org
>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>
>>>>
>>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/0707c05e/attachment-0001.html>

From isaac.gerg at gergltd.com  Tue Jan  5 17:31:41 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Tue, 5 Jan 2016 17:31:41 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in matplotlibrc
Message-ID: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>

Hi,

I was wondering if there are any plans to change some of the defaults in
matplotlibrc.  I have created a matplotlibrc file that I find very suitable
and wondering if its worth sharing here.

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

From juichenieder-nabb at yahoo.co.uk  Tue Jan  5 21:13:10 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Wed, 6 Jan 2016 03:13:10 +0100
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
Message-ID: <568C7836.9050608@yahoo.co.uk>

Hi Isaac,
As it happens, yes, in the upcoming 2.0 release has the sole purpose of 
changing rcParam defaults, see http://matplotlib.org/style_changes.html 
for more information.

Best,
OceanWolf

On 05/01/16 23:31, Isaac Gerg wrote:
> Hi,
>
> I was wondering if there are any plans to change some of the defaults 
> in matplotlibrc.  I have created a matplotlibrc file that I find very 
> suitable and wondering if its worth sharing here.
>
> Isaac
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel

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

From isaac.gerg at gergltd.com  Tue Jan  5 21:26:49 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Tue, 5 Jan 2016 21:26:49 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <568C7836.9050608@yahoo.co.uk>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
Message-ID: <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>

Where is the new rcparams?

On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
wrote:

> Hi Isaac,
> As it happens, yes, in the upcoming 2.0 release has the sole purpose of
> changing rcParam defaults, see http://matplotlib.org/style_changes.html
> for more information.
>
> Best,
> OceanWolf
>
>
> On 05/01/16 23:31, Isaac Gerg wrote:
>
> Hi,
>
> I was wondering if there are any plans to change some of the defaults in
> matplotlibrc.  I have created a matplotlibrc file that I find very suitable
> and wondering if its worth sharing here.
>
> Isaac
>
>
> _______________________________________________
> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160105/4bcca395/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Tue Jan  5 22:08:15 2016
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Wed, 6 Jan 2016 04:08:15 +0100
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
Message-ID: <568C851F.6000201@yahoo.co.uk>

Good question... I have gotten a bit out touch with the current state of 
things so I defer to others.  As far as I know the current plans at the 
moment only include changes to the default colormap to viridis, but 
others can get changed as well. feel free to post a link here, or (I 
guess even better), make an issue/or PR (changing rcsetup.py) on github, 
so that we can take it into consideration for 2.0.

Looking at the state of the branches on github I have gotten a bit 
confused with the strategy... now we have 1.5 released and 2.0 marked as 
a copy of 1.5.x bar rc changes, I would have assumed the new rc changes 
would end up in master and then backported to the v2.x branch, but that 
doesn't look like the case... can someone clarify that for me?

Best,
OceanWolf

On 06/01/16 03:26, Isaac Gerg wrote:
> Where is the new rcparams?
>
> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf 
> <juichenieder-nabb at yahoo.co.uk <mailto:juichenieder-nabb at yahoo.co.uk>> 
> wrote:
>
>     Hi Isaac,
>     As it happens, yes, in the upcoming 2.0 release has the sole
>     purpose of changing rcParam defaults, see
>     http://matplotlib.org/style_changes.html for more information.
>
>     Best,
>     OceanWolf
>
>
>     On 05/01/16 23:31, Isaac Gerg wrote:
>>     Hi,
>>
>>     I was wondering if there are any plans to change some of the
>>     defaults in matplotlibrc.  I have created a matplotlibrc file
>>     that I find very suitable and wondering if its worth sharing here.
>>
>>     Isaac
>>
>>
>>     _______________________________________________
>>     Matplotlib-devel mailing list
>>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>>     https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>     https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>

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

From matthew.brett at gmail.com  Wed Jan  6 04:11:25 2016
From: matthew.brett at gmail.com (Matthew Brett)
Date: Wed, 6 Jan 2016 09:11:25 +0000
Subject: [Matplotlib-devel] ANN mpl v1.5.1rc1
In-Reply-To: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
References: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
Message-ID: <CAH6Pt5qMnDopeWmLk27qjaOFDtt1O1fqVFjOTTSRgirqoe6ntw@mail.gmail.com>

Hi,

On Sat, Jan 2, 2016 at 9:56 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Hey Folks,
>
> We are happy to announce the first RC for 1.5.1, the first bug-fix release
> is the 1.5.x series, please kick the tires.  Given the scale of the changes
> from 1.5.0 we are planning a short RC cycle with a 1.5.1 final tagged on
> 2016-01-06.
>
> To see the differences between 1.5.0 and 1.5.1rc1 .
>
> We had not planned to do a 1.5.1 release, but the style changes for v2.0
> revealed a number of critical issues which needed to be addressed.  The time
> line for 2.0 is contingent on how well that work goes and if we discover any
> other major work that needs to be done to support the default style changes.
> The goal is v2.0.0rc1 sometime in the Q1 of 2016 with a long rc cycle to
> have as many users as possible try the new defaults prior to tagging v2.
>
> Thank you to everyone who reported bugs and fixes against v1.5.0.

OSX wheels for testing at wheels.scipy.org:

pip install --pre --trusted-host wheels.scipy.org -f
http://wheels.scipy.org matplotlib

Matthew

From mdroettboom at continuum.io  Wed Jan  6 08:53:17 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Wed, 6 Jan 2016 08:53:17 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <568C851F.6000201@yahoo.co.uk>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
Message-ID: <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>

The omnibus PR containing most of the style changes for 2.x is here:

https://github.com/matplotlib/matplotlib/pull/5774

This isn't everything -- some changes are already in 2.x and master.
Others are in separate PRs with 2.0 as a milestone.

The new changes are being made against 2.x and are forward-ported to master.

Also, to answer Isaac's original suggestion: if you have a matplotlibrc
that you think would be useful for others, feel free to submit it as a
style.  Since 1.4, we've had a style infrastructure that makes it easy for
users to switch styles.  While the default style has to be very carefully
designed so as to provide "reasonable behavior for the most common cases",
individual styles do not and can be more aggressively different.

Mike

On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
wrote:

> Good question... I have gotten a bit out touch with the current state of
> things so I defer to others.  As far as I know the current plans at the
> moment only include changes to the default colormap to viridis, but others
> can get changed as well. feel free to post a link here, or (I guess even
> better), make an issue/or PR (changing rcsetup.py) on github, so that we
> can take it into consideration for 2.0.
>
> Looking at the state of the branches on github I have gotten a bit
> confused with the strategy... now we have 1.5 released and 2.0 marked as a
> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
> end up in master and then backported to the v2.x branch, but that doesn't
> look like the case... can someone clarify that for me?
>
> Best,
> OceanWolf
>
>
> On 06/01/16 03:26, Isaac Gerg wrote:
>
> Where is the new rcparams?
>
> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
> wrote:
>
>> Hi Isaac,
>> As it happens, yes, in the upcoming 2.0 release has the sole purpose of
>> changing rcParam defaults, see <http://matplotlib.org/style_changes.html>
>> http://matplotlib.org/style_changes.html for more information.
>>
>> Best,
>> OceanWolf
>>
>>
>> On 05/01/16 23:31, Isaac Gerg wrote:
>>
>> Hi,
>>
>> I was wondering if there are any plans to change some of the defaults in
>> matplotlibrc.  I have created a matplotlibrc file that I find very suitable
>> and wondering if its worth sharing here.
>>
>> Isaac
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160106/9f42b843/attachment.html>

From isaac.gerg at gergltd.com  Wed Jan  6 10:56:33 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Wed, 6 Jan 2016 10:56:33 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
Message-ID: <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>

Thanks for everyone's replies.

I am still perfecting my rc file but am happy to share what I have so far.

https://github.com/isaacgerg/matplotlibrc

I did a research project a few years ago on color theory and am updating my
rc file based on my findings.

Additionally, it would be really cool to have some kind of webapp whereby a
user uploads their matplotlibrc file and the server generates a set of
plots based on it.  I'm happy to take a whack at it if folks want to chime
in and email me some example plots to render.  I would keep it to simple
plots to start.

I am aware of the plotornot "experiment" and also have rolled some of those
features into my rc file as well (its very based off of Cam Davidson's)

Isaac

On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <mdroettboom at continuum.io
> wrote:

> The omnibus PR containing most of the style changes for 2.x is here:
>
> https://github.com/matplotlib/matplotlib/pull/5774
>
> This isn't everything -- some changes are already in 2.x and master.
> Others are in separate PRs with 2.0 as a milestone.
>
> The new changes are being made against 2.x and are forward-ported to
> master.
>
> Also, to answer Isaac's original suggestion: if you have a matplotlibrc
> that you think would be useful for others, feel free to submit it as a
> style.  Since 1.4, we've had a style infrastructure that makes it easy for
> users to switch styles.  While the default style has to be very carefully
> designed so as to provide "reasonable behavior for the most common cases",
> individual styles do not and can be more aggressively different.
>
> Mike
>
> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
> wrote:
>
>> Good question... I have gotten a bit out touch with the current state of
>> things so I defer to others.  As far as I know the current plans at the
>> moment only include changes to the default colormap to viridis, but others
>> can get changed as well. feel free to post a link here, or (I guess even
>> better), make an issue/or PR (changing rcsetup.py) on github, so that we
>> can take it into consideration for 2.0.
>>
>> Looking at the state of the branches on github I have gotten a bit
>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>> end up in master and then backported to the v2.x branch, but that doesn't
>> look like the case... can someone clarify that for me?
>>
>> Best,
>> OceanWolf
>>
>>
>> On 06/01/16 03:26, Isaac Gerg wrote:
>>
>> Where is the new rcparams?
>>
>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk>
>> wrote:
>>
>>> Hi Isaac,
>>> As it happens, yes, in the upcoming 2.0 release has the sole purpose of
>>> changing rcParam defaults, see
>>> <http://matplotlib.org/style_changes.html>
>>> http://matplotlib.org/style_changes.html for more information.
>>>
>>> Best,
>>> OceanWolf
>>>
>>>
>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>
>>> Hi,
>>>
>>> I was wondering if there are any plans to change some of the defaults in
>>> matplotlibrc.  I have created a matplotlibrc file that I find very suitable
>>> and wondering if its worth sharing here.
>>>
>>> Isaac
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Michael Droettboom
> Continuum Analytics
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160106/f4b5eac8/attachment-0001.html>

From isaac.gerg at gergltd.com  Wed Jan  6 10:57:44 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Wed, 6 Jan 2016 10:57:44 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
 <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
Message-ID: <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>

To add, I should also say you could just paste a URL and it downloads the
rc file and shows the plots.  Matplotlib makes this easy!

On Wed, Jan 6, 2016 at 10:56 AM, Isaac Gerg <isaac.gerg at gergltd.com> wrote:

> Thanks for everyone's replies.
>
> I am still perfecting my rc file but am happy to share what I have so far.
>
>
> https://github.com/isaacgerg/matplotlibrc
>
> I did a research project a few years ago on color theory and am updating
> my rc file based on my findings.
>
> Additionally, it would be really cool to have some kind of webapp whereby
> a user uploads their matplotlibrc file and the server generates a set of
> plots based on it.  I'm happy to take a whack at it if folks want to chime
> in and email me some example plots to render.  I would keep it to simple
> plots to start.
>
> I am aware of the plotornot "experiment" and also have rolled some of
> those features into my rc file as well (its very based off of Cam
> Davidson's)
>
> Isaac
>
> On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <
> mdroettboom at continuum.io> wrote:
>
>> The omnibus PR containing most of the style changes for 2.x is here:
>>
>> https://github.com/matplotlib/matplotlib/pull/5774
>>
>> This isn't everything -- some changes are already in 2.x and master.
>> Others are in separate PRs with 2.0 as a milestone.
>>
>> The new changes are being made against 2.x and are forward-ported to
>> master.
>>
>> Also, to answer Isaac's original suggestion: if you have a matplotlibrc
>> that you think would be useful for others, feel free to submit it as a
>> style.  Since 1.4, we've had a style infrastructure that makes it easy for
>> users to switch styles.  While the default style has to be very carefully
>> designed so as to provide "reasonable behavior for the most common cases",
>> individual styles do not and can be more aggressively different.
>>
>> Mike
>>
>> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk
>> > wrote:
>>
>>> Good question... I have gotten a bit out touch with the current state of
>>> things so I defer to others.  As far as I know the current plans at the
>>> moment only include changes to the default colormap to viridis, but others
>>> can get changed as well. feel free to post a link here, or (I guess even
>>> better), make an issue/or PR (changing rcsetup.py) on github, so that we
>>> can take it into consideration for 2.0.
>>>
>>> Looking at the state of the branches on github I have gotten a bit
>>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>>> end up in master and then backported to the v2.x branch, but that doesn't
>>> look like the case... can someone clarify that for me?
>>>
>>> Best,
>>> OceanWolf
>>>
>>>
>>> On 06/01/16 03:26, Isaac Gerg wrote:
>>>
>>> Where is the new rcparams?
>>>
>>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <juichenieder-nabb at yahoo.co.uk
>>> > wrote:
>>>
>>>> Hi Isaac,
>>>> As it happens, yes, in the upcoming 2.0 release has the sole purpose of
>>>> changing rcParam defaults, see
>>>> <http://matplotlib.org/style_changes.html>
>>>> http://matplotlib.org/style_changes.html for more information.
>>>>
>>>> Best,
>>>> OceanWolf
>>>>
>>>>
>>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>>
>>>> Hi,
>>>>
>>>> I was wondering if there are any plans to change some of the defaults
>>>> in matplotlibrc.  I have created a matplotlibrc file that I find very
>>>> suitable and wondering if its worth sharing here.
>>>>
>>>> Isaac
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at python.org
>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>>
>>
>>
>> --
>> Michael Droettboom
>> Continuum Analytics
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160106/0b8a0542/attachment.html>

From isaac.gerg at gergltd.com  Wed Jan  6 11:21:47 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Wed, 6 Jan 2016 11:21:47 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
 <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
 <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>
Message-ID: <CADnN3yVKEzEQOBxvcX+CiPAN_WUdeiECKZ5vxauqYhTaHMUN2A@mail.gmail.com>

I've started work on a test script for matplotlibrc files.

Its here: https://github.com/isaacgerg/matplotlibrc

Its my plan to continue to update this along with my rc file as I go along
my day.

On Wed, Jan 6, 2016 at 10:57 AM, Isaac Gerg <isaac.gerg at gergltd.com> wrote:

> To add, I should also say you could just paste a URL and it downloads the
> rc file and shows the plots.  Matplotlib makes this easy!
>
> On Wed, Jan 6, 2016 at 10:56 AM, Isaac Gerg <isaac.gerg at gergltd.com>
> wrote:
>
>> Thanks for everyone's replies.
>>
>> I am still perfecting my rc file but am happy to share what I have so
>> far.
>>
>> https://github.com/isaacgerg/matplotlibrc
>>
>> I did a research project a few years ago on color theory and am updating
>> my rc file based on my findings.
>>
>> Additionally, it would be really cool to have some kind of webapp whereby
>> a user uploads their matplotlibrc file and the server generates a set of
>> plots based on it.  I'm happy to take a whack at it if folks want to chime
>> in and email me some example plots to render.  I would keep it to simple
>> plots to start.
>>
>> I am aware of the plotornot "experiment" and also have rolled some of
>> those features into my rc file as well (its very based off of Cam
>> Davidson's)
>>
>> Isaac
>>
>> On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <
>> mdroettboom at continuum.io> wrote:
>>
>>> The omnibus PR containing most of the style changes for 2.x is here:
>>>
>>> https://github.com/matplotlib/matplotlib/pull/5774
>>>
>>> This isn't everything -- some changes are already in 2.x and master.
>>> Others are in separate PRs with 2.0 as a milestone.
>>>
>>> The new changes are being made against 2.x and are forward-ported to
>>> master.
>>>
>>> Also, to answer Isaac's original suggestion: if you have a matplotlibrc
>>> that you think would be useful for others, feel free to submit it as a
>>> style.  Since 1.4, we've had a style infrastructure that makes it easy for
>>> users to switch styles.  While the default style has to be very carefully
>>> designed so as to provide "reasonable behavior for the most common cases",
>>> individual styles do not and can be more aggressively different.
>>>
>>> Mike
>>>
>>> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <
>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>
>>>> Good question... I have gotten a bit out touch with the current state
>>>> of things so I defer to others.  As far as I know the current plans at the
>>>> moment only include changes to the default colormap to viridis, but others
>>>> can get changed as well. feel free to post a link here, or (I guess even
>>>> better), make an issue/or PR (changing rcsetup.py) on github, so that we
>>>> can take it into consideration for 2.0.
>>>>
>>>> Looking at the state of the branches on github I have gotten a bit
>>>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>>>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>>>> end up in master and then backported to the v2.x branch, but that doesn't
>>>> look like the case... can someone clarify that for me?
>>>>
>>>> Best,
>>>> OceanWolf
>>>>
>>>>
>>>> On 06/01/16 03:26, Isaac Gerg wrote:
>>>>
>>>> Where is the new rcparams?
>>>>
>>>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <
>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>
>>>>> Hi Isaac,
>>>>> As it happens, yes, in the upcoming 2.0 release has the sole purpose
>>>>> of changing rcParam defaults, see
>>>>> <http://matplotlib.org/style_changes.html>
>>>>> http://matplotlib.org/style_changes.html for more information.
>>>>>
>>>>> Best,
>>>>> OceanWolf
>>>>>
>>>>>
>>>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I was wondering if there are any plans to change some of the defaults
>>>>> in matplotlibrc.  I have created a matplotlibrc file that I find very
>>>>> suitable and wondering if its worth sharing here.
>>>>>
>>>>> Isaac
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing list
>>>>> Matplotlib-devel at python.org
>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at python.org
>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>>
>>>
>>>
>>> --
>>> Michael Droettboom
>>> Continuum Analytics
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160106/416b8cdc/attachment-0001.html>

From morph at debian.org  Wed Jan  6 15:44:03 2016
From: morph at debian.org (Sandro Tosi)
Date: Wed, 6 Jan 2016 20:44:03 +0000
Subject: [Matplotlib-devel] ANN mpl v1.5.1rc1
In-Reply-To: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
References: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
Message-ID: <CAB4XWXzRw07kZ+Z=dad8Nge=Z9ihytaYEWa4npHUWKbbZbLYtQ@mail.gmail.com>

The only problem I found so far in Debian is:
https://github.com/matplotlib/matplotlib/issues/5807

On Sat, Jan 2, 2016 at 9:56 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Hey Folks,
>
> We are happy to announce the first RC for 1.5.1, the first bug-fix release
> is the 1.5.x series, please kick the tires.  Given the scale of the changes
> from 1.5.0 we are planning a short RC cycle with a 1.5.1 final tagged on
> 2016-01-06.
>
> To see the differences between 1.5.0 and 1.5.1rc1 .
>
> We had not planned to do a 1.5.1 release, but the style changes for v2.0
> revealed a number of critical issues which needed to be addressed.  The time
> line for 2.0 is contingent on how well that work goes and if we discover any
> other major work that needs to be done to support the default style changes.
> The goal is v2.0.0rc1 sometime in the Q1 of 2016 with a long rc cycle to
> have as many users as possible try the new defaults prior to tagging v2.
>
> Thank you to everyone who reported bugs and fixes against v1.5.0.
>
> Tom
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>



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

From isaac.gerg at gergltd.com  Wed Jan  6 15:46:29 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Wed, 6 Jan 2016 15:46:29 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yVKEzEQOBxvcX+CiPAN_WUdeiECKZ5vxauqYhTaHMUN2A@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
 <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
 <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>
 <CADnN3yVKEzEQOBxvcX+CiPAN_WUdeiECKZ5vxauqYhTaHMUN2A@mail.gmail.com>
Message-ID: <CADnN3yVQkuMy_jpeB_ayK1iHZhPsWLs_Y6UVD8c1ToEroCmDgQ@mail.gmail.com>

Is there any way to change the way the autoscale function from rcparams?
For my plot(x,y)'s there is too much space on the left and right of my line
plots.

On Wed, Jan 6, 2016 at 11:21 AM, Isaac Gerg <isaac.gerg at gergltd.com> wrote:

> I've started work on a test script for matplotlibrc files.
>
> Its here: https://github.com/isaacgerg/matplotlibrc
>
> Its my plan to continue to update this along with my rc file as I go along
> my day.
>
> On Wed, Jan 6, 2016 at 10:57 AM, Isaac Gerg <isaac.gerg at gergltd.com>
> wrote:
>
>> To add, I should also say you could just paste a URL and it downloads the
>> rc file and shows the plots.  Matplotlib makes this easy!
>>
>> On Wed, Jan 6, 2016 at 10:56 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>> wrote:
>>
>>> Thanks for everyone's replies.
>>>
>>> I am still perfecting my rc file but am happy to share what I have so
>>> far.
>>>
>>> https://github.com/isaacgerg/matplotlibrc
>>>
>>> I did a research project a few years ago on color theory and am updating
>>> my rc file based on my findings.
>>>
>>> Additionally, it would be really cool to have some kind of webapp
>>> whereby a user uploads their matplotlibrc file and the server generates a
>>> set of plots based on it.  I'm happy to take a whack at it if folks want to
>>> chime in and email me some example plots to render.  I would keep it to
>>> simple plots to start.
>>>
>>> I am aware of the plotornot "experiment" and also have rolled some of
>>> those features into my rc file as well (its very based off of Cam
>>> Davidson's)
>>>
>>> Isaac
>>>
>>> On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <
>>> mdroettboom at continuum.io> wrote:
>>>
>>>> The omnibus PR containing most of the style changes for 2.x is here:
>>>>
>>>> https://github.com/matplotlib/matplotlib/pull/5774
>>>>
>>>> This isn't everything -- some changes are already in 2.x and master.
>>>> Others are in separate PRs with 2.0 as a milestone.
>>>>
>>>> The new changes are being made against 2.x and are forward-ported to
>>>> master.
>>>>
>>>> Also, to answer Isaac's original suggestion: if you have a matplotlibrc
>>>> that you think would be useful for others, feel free to submit it as a
>>>> style.  Since 1.4, we've had a style infrastructure that makes it easy for
>>>> users to switch styles.  While the default style has to be very carefully
>>>> designed so as to provide "reasonable behavior for the most common cases",
>>>> individual styles do not and can be more aggressively different.
>>>>
>>>> Mike
>>>>
>>>> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <
>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>
>>>>> Good question... I have gotten a bit out touch with the current state
>>>>> of things so I defer to others.  As far as I know the current plans at the
>>>>> moment only include changes to the default colormap to viridis, but others
>>>>> can get changed as well. feel free to post a link here, or (I guess even
>>>>> better), make an issue/or PR (changing rcsetup.py) on github, so that we
>>>>> can take it into consideration for 2.0.
>>>>>
>>>>> Looking at the state of the branches on github I have gotten a bit
>>>>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>>>>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>>>>> end up in master and then backported to the v2.x branch, but that doesn't
>>>>> look like the case... can someone clarify that for me?
>>>>>
>>>>> Best,
>>>>> OceanWolf
>>>>>
>>>>>
>>>>> On 06/01/16 03:26, Isaac Gerg wrote:
>>>>>
>>>>> Where is the new rcparams?
>>>>>
>>>>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <
>>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>>
>>>>>> Hi Isaac,
>>>>>> As it happens, yes, in the upcoming 2.0 release has the sole purpose
>>>>>> of changing rcParam defaults, see
>>>>>> <http://matplotlib.org/style_changes.html>
>>>>>> http://matplotlib.org/style_changes.html for more information.
>>>>>>
>>>>>> Best,
>>>>>> OceanWolf
>>>>>>
>>>>>>
>>>>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was wondering if there are any plans to change some of the defaults
>>>>>> in matplotlibrc.  I have created a matplotlibrc file that I find very
>>>>>> suitable and wondering if its worth sharing here.
>>>>>>
>>>>>> Isaac
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matplotlib-devel mailing list
>>>>>> Matplotlib-devel at python.org
>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing list
>>>>> Matplotlib-devel at python.org
>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Michael Droettboom
>>>> Continuum Analytics
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160106/ecc760d0/attachment.html>

From tcaswell at gmail.com  Wed Jan  6 23:34:51 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 07 Jan 2016 04:34:51 +0000
Subject: [Matplotlib-devel] ANN mpl v1.5.1rc1
In-Reply-To: <CAB4XWXzRw07kZ+Z=dad8Nge=Z9ihytaYEWa4npHUWKbbZbLYtQ@mail.gmail.com>
References: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
 <CAB4XWXzRw07kZ+Z=dad8Nge=Z9ihytaYEWa4npHUWKbbZbLYtQ@mail.gmail.com>
Message-ID: <CAA48SF-BOFCEX7otV8BhxEkqW61RDm4jga3419_2h6Z=E7MRdA@mail.gmail.com>

Hey all,

We have accumulated open 4 issues one PR left (
https://github.com/matplotlib/matplotlib/milestones/Critical%20bugfix%20release%20(1.5.1
))

Of the 3 issues without a PR  5793 is documentation, 5807 I suspect is a
configuration issue in the debian build system (and I can not reproduce
locally), and 5737 can not be reproduced by Jens and may be GUI event loops
conflicting with each other.  I am comfortable not blocking on any of those
issues.

I hope 1.5.1 tagging will only be pushed back to tomorrow (Thursday
2016-01-07)

Tom

On Wed, Jan 6, 2016 at 3:44 PM Sandro Tosi <morph at debian.org> wrote:

> The only problem I found so far in Debian is:
> https://github.com/matplotlib/matplotlib/issues/5807
>
> On Sat, Jan 2, 2016 at 9:56 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> > Hey Folks,
> >
> > We are happy to announce the first RC for 1.5.1, the first bug-fix
> release
> > is the 1.5.x series, please kick the tires.  Given the scale of the
> changes
> > from 1.5.0 we are planning a short RC cycle with a 1.5.1 final tagged on
> > 2016-01-06.
> >
> > To see the differences between 1.5.0 and 1.5.1rc1 .
> >
> > We had not planned to do a 1.5.1 release, but the style changes for v2.0
> > revealed a number of critical issues which needed to be addressed.  The
> time
> > line for 2.0 is contingent on how well that work goes and if we discover
> any
> > other major work that needs to be done to support the default style
> changes.
> > The goal is v2.0.0rc1 sometime in the Q1 of 2016 with a long rc cycle to
> > have as many users as possible try the new defaults prior to tagging v2.
> >
> > Thank you to everyone who reported bugs and fixes against v1.5.0.
> >
> > Tom
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Matplotlib-devel at python.org
> > https://mail.python.org/mailman/listinfo/matplotlib-devel
> >
>
>
>
> --
> Sandro "morph" Tosi
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
> G+: https://plus.google.com/u/0/+SandroTosi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160107/4bbc7ebf/attachment-0001.html>

From pmhobson at gmail.com  Thu Jan  7 14:35:26 2016
From: pmhobson at gmail.com (Paul Hobson)
Date: Thu, 7 Jan 2016 11:35:26 -0800
Subject: [Matplotlib-devel] ANN mpl v1.5.1rc1
In-Reply-To: <CAA48SF-BOFCEX7otV8BhxEkqW61RDm4jga3419_2h6Z=E7MRdA@mail.gmail.com>
References: <CAA48SF_b1cB1CmjibhdgAs_fDYdF6W+6NmZFtps4sEt24p9QJA@mail.gmail.com>
 <CAB4XWXzRw07kZ+Z=dad8Nge=Z9ihytaYEWa4npHUWKbbZbLYtQ@mail.gmail.com>
 <CAA48SF-BOFCEX7otV8BhxEkqW61RDm4jga3419_2h6Z=E7MRdA@mail.gmail.com>
Message-ID: <CADT3MED4c9TQvNVFQ34CzLvpn1++FCfPU1-=xuxG9K9FBLYsiA@mail.gmail.com>

Is there a conda build (or whl) for windows I can mess with?

On Wed, Jan 6, 2016 at 8:34 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Hey all,
>
> We have accumulated open 4 issues one PR left (
> https://github.com/matplotlib/matplotlib/milestones/Critical%20bugfix%20release%20(1.5.1
> ))
>
> Of the 3 issues without a PR  5793 is documentation, 5807 I suspect is a
> configuration issue in the debian build system (and I can not reproduce
> locally), and 5737 can not be reproduced by Jens and may be GUI event loops
> conflicting with each other.  I am comfortable not blocking on any of those
> issues.
>
> I hope 1.5.1 tagging will only be pushed back to tomorrow (Thursday
> 2016-01-07)
>
> Tom
>
> On Wed, Jan 6, 2016 at 3:44 PM Sandro Tosi <morph at debian.org> wrote:
>
>> The only problem I found so far in Debian is:
>> https://github.com/matplotlib/matplotlib/issues/5807
>>
>> On Sat, Jan 2, 2016 at 9:56 PM, Thomas Caswell <tcaswell at gmail.com>
>> wrote:
>> > Hey Folks,
>> >
>> > We are happy to announce the first RC for 1.5.1, the first bug-fix
>> release
>> > is the 1.5.x series, please kick the tires.  Given the scale of the
>> changes
>> > from 1.5.0 we are planning a short RC cycle with a 1.5.1 final tagged on
>> > 2016-01-06.
>> >
>> > To see the differences between 1.5.0 and 1.5.1rc1 .
>> >
>> > We had not planned to do a 1.5.1 release, but the style changes for v2.0
>> > revealed a number of critical issues which needed to be addressed.  The
>> time
>> > line for 2.0 is contingent on how well that work goes and if we
>> discover any
>> > other major work that needs to be done to support the default style
>> changes.
>> > The goal is v2.0.0rc1 sometime in the Q1 of 2016 with a long rc cycle to
>> > have as many users as possible try the new defaults prior to tagging v2.
>> >
>> > Thank you to everyone who reported bugs and fixes against v1.5.0.
>> >
>> > Tom
>> >
>> > _______________________________________________
>> > Matplotlib-devel mailing list
>> > Matplotlib-devel at python.org
>> > https://mail.python.org/mailman/listinfo/matplotlib-devel
>> >
>>
>>
>>
>> --
>> Sandro "morph" Tosi
>> My website: http://matrixhasu.altervista.org/
>> Me at Debian: http://wiki.debian.org/SandroTosi
>> G+: https://plus.google.com/u/0/+SandroTosi
>>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160107/a4fd1ffd/attachment.html>

From mdroettboom at continuum.io  Thu Jan  7 15:19:19 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Thu, 7 Jan 2016 15:19:19 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADnN3yVQkuMy_jpeB_ayK1iHZhPsWLs_Y6UVD8c1ToEroCmDgQ@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
 <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
 <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>
 <CADnN3yVKEzEQOBxvcX+CiPAN_WUdeiECKZ5vxauqYhTaHMUN2A@mail.gmail.com>
 <CADnN3yVQkuMy_jpeB_ayK1iHZhPsWLs_Y6UVD8c1ToEroCmDgQ@mail.gmail.com>
Message-ID: <CADsn3C2M5ZBQziVwWQ9d2cdWg1+MHOGZbCVXr8VQq1TF=2zpnQ@mail.gmail.com>

The new defaults with 2.0 is to add a fixed amount of visual padding on all
sides. The amount of padding can be controlled with axes.xmargin and
axes.ymargin.

Prior to 2.0, the default behavior was to move to ?round numbers?, which is
a lot less predictable.

In either case, the algorithm used to autoscale can be replaced by
replacing the locator. See the ticker docs.

Mike
?

On Wed, Jan 6, 2016 at 3:46 PM, Isaac Gerg <isaac.gerg at gergltd.com> wrote:

> Is there any way to change the way the autoscale function from rcparams?
> For my plot(x,y)'s there is too much space on the left and right of my line
> plots.
>
> On Wed, Jan 6, 2016 at 11:21 AM, Isaac Gerg <isaac.gerg at gergltd.com>
> wrote:
>
>> I've started work on a test script for matplotlibrc files.
>>
>> Its here: https://github.com/isaacgerg/matplotlibrc
>>
>> Its my plan to continue to update this along with my rc file as I go
>> along my day.
>>
>> On Wed, Jan 6, 2016 at 10:57 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>> wrote:
>>
>>> To add, I should also say you could just paste a URL and it downloads
>>> the rc file and shows the plots.  Matplotlib makes this easy!
>>>
>>> On Wed, Jan 6, 2016 at 10:56 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>>> wrote:
>>>
>>>> Thanks for everyone's replies.
>>>>
>>>> I am still perfecting my rc file but am happy to share what I have so
>>>> far.
>>>>
>>>> https://github.com/isaacgerg/matplotlibrc
>>>>
>>>> I did a research project a few years ago on color theory and am
>>>> updating my rc file based on my findings.
>>>>
>>>> Additionally, it would be really cool to have some kind of webapp
>>>> whereby a user uploads their matplotlibrc file and the server generates a
>>>> set of plots based on it.  I'm happy to take a whack at it if folks want to
>>>> chime in and email me some example plots to render.  I would keep it to
>>>> simple plots to start.
>>>>
>>>> I am aware of the plotornot "experiment" and also have rolled some of
>>>> those features into my rc file as well (its very based off of Cam
>>>> Davidson's)
>>>>
>>>> Isaac
>>>>
>>>> On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <
>>>> mdroettboom at continuum.io> wrote:
>>>>
>>>>> The omnibus PR containing most of the style changes for 2.x is here:
>>>>>
>>>>> https://github.com/matplotlib/matplotlib/pull/5774
>>>>>
>>>>> This isn't everything -- some changes are already in 2.x and master.
>>>>> Others are in separate PRs with 2.0 as a milestone.
>>>>>
>>>>> The new changes are being made against 2.x and are forward-ported to
>>>>> master.
>>>>>
>>>>> Also, to answer Isaac's original suggestion: if you have a
>>>>> matplotlibrc that you think would be useful for others, feel free to submit
>>>>> it as a style.  Since 1.4, we've had a style infrastructure that makes it
>>>>> easy for users to switch styles.  While the default style has to be very
>>>>> carefully designed so as to provide "reasonable behavior for the most
>>>>> common cases", individual styles do not and can be more aggressively
>>>>> different.
>>>>>
>>>>> Mike
>>>>>
>>>>> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <
>>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>>
>>>>>> Good question... I have gotten a bit out touch with the current state
>>>>>> of things so I defer to others.  As far as I know the current plans at the
>>>>>> moment only include changes to the default colormap to viridis, but others
>>>>>> can get changed as well. feel free to post a link here, or (I guess even
>>>>>> better), make an issue/or PR (changing rcsetup.py) on github, so that we
>>>>>> can take it into consideration for 2.0.
>>>>>>
>>>>>> Looking at the state of the branches on github I have gotten a bit
>>>>>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>>>>>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>>>>>> end up in master and then backported to the v2.x branch, but that doesn't
>>>>>> look like the case... can someone clarify that for me?
>>>>>>
>>>>>> Best,
>>>>>> OceanWolf
>>>>>>
>>>>>>
>>>>>> On 06/01/16 03:26, Isaac Gerg wrote:
>>>>>>
>>>>>> Where is the new rcparams?
>>>>>>
>>>>>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <
>>>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>>>
>>>>>>> Hi Isaac,
>>>>>>> As it happens, yes, in the upcoming 2.0 release has the sole purpose
>>>>>>> of changing rcParam defaults, see
>>>>>>> <http://matplotlib.org/style_changes.html>
>>>>>>> http://matplotlib.org/style_changes.html for more information.
>>>>>>>
>>>>>>> Best,
>>>>>>> OceanWolf
>>>>>>>
>>>>>>>
>>>>>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I was wondering if there are any plans to change some of the
>>>>>>> defaults in matplotlibrc.  I have created a matplotlibrc file that I find
>>>>>>> very suitable and wondering if its worth sharing here.
>>>>>>>
>>>>>>> Isaac
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Matplotlib-devel mailing list
>>>>>>> Matplotlib-devel at python.org
>>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matplotlib-devel mailing list
>>>>>> Matplotlib-devel at python.org
>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Droettboom
>>>>> Continuum Analytics
>>>>>
>>>>
>>>>
>>>
>>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160107/1aed31ff/attachment-0001.html>

From isaac.gerg at gergltd.com  Thu Jan  7 15:31:23 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Thu, 7 Jan 2016 15:31:23 -0500
Subject: [Matplotlib-devel] Any plans to change the defaults in
 matplotlibrc
In-Reply-To: <CADsn3C2M5ZBQziVwWQ9d2cdWg1+MHOGZbCVXr8VQq1TF=2zpnQ@mail.gmail.com>
References: <CADnN3yWX6tVyMYejbE63RDydO2zXpyWjkWRFBB=4gqUx0ZFvuw@mail.gmail.com>
 <568C7836.9050608@yahoo.co.uk>
 <CADnN3yVgzCrwLXvpTiS7JnrE8+kUoD+wXzC+zQ3vEK=MeKMbUQ@mail.gmail.com>
 <568C851F.6000201@yahoo.co.uk>
 <CADsn3C0-GTzA-FK9yVYAdvZvJDGOvR7uT9p5J3wvTjHkYSFkGA@mail.gmail.com>
 <CADnN3yVqvDDvtUNq6AS-mPX8PEt1mFe-Vp4PLF1H6K2GP9g4NQ@mail.gmail.com>
 <CADnN3yU1zj6wJsLb+=kcdPTmoJBqdha4Zx-R9vuTs6TFbpaVXw@mail.gmail.com>
 <CADnN3yVKEzEQOBxvcX+CiPAN_WUdeiECKZ5vxauqYhTaHMUN2A@mail.gmail.com>
 <CADnN3yVQkuMy_jpeB_ayK1iHZhPsWLs_Y6UVD8c1ToEroCmDgQ@mail.gmail.com>
 <CADsn3C2M5ZBQziVwWQ9d2cdWg1+MHOGZbCVXr8VQq1TF=2zpnQ@mail.gmail.com>
Message-ID: <CADnN3yVLHcXug3FrHB_zHeDrZZ_Gz2rtP7d4jO7MdzPUZctPKA@mail.gmail.com>

This is great.  Stoked about the new updates in 2.0!

On Thu, Jan 7, 2016 at 3:19 PM, Michael Droettboom <mdroettboom at continuum.io
> wrote:

> The new defaults with 2.0 is to add a fixed amount of visual padding on
> all sides. The amount of padding can be controlled with axes.xmargin and
> axes.ymargin.
>
> Prior to 2.0, the default behavior was to move to ?round numbers?, which
> is a lot less predictable.
>
> In either case, the algorithm used to autoscale can be replaced by
> replacing the locator. See the ticker docs.
>
> Mike
> ?
>
> On Wed, Jan 6, 2016 at 3:46 PM, Isaac Gerg <isaac.gerg at gergltd.com> wrote:
>
>> Is there any way to change the way the autoscale function from rcparams?
>> For my plot(x,y)'s there is too much space on the left and right of my line
>> plots.
>>
>> On Wed, Jan 6, 2016 at 11:21 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>> wrote:
>>
>>> I've started work on a test script for matplotlibrc files.
>>>
>>> Its here: https://github.com/isaacgerg/matplotlibrc
>>>
>>> Its my plan to continue to update this along with my rc file as I go
>>> along my day.
>>>
>>> On Wed, Jan 6, 2016 at 10:57 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>>> wrote:
>>>
>>>> To add, I should also say you could just paste a URL and it downloads
>>>> the rc file and shows the plots.  Matplotlib makes this easy!
>>>>
>>>> On Wed, Jan 6, 2016 at 10:56 AM, Isaac Gerg <isaac.gerg at gergltd.com>
>>>> wrote:
>>>>
>>>>> Thanks for everyone's replies.
>>>>>
>>>>> I am still perfecting my rc file but am happy to share what I have so
>>>>> far.
>>>>>
>>>>> https://github.com/isaacgerg/matplotlibrc
>>>>>
>>>>> I did a research project a few years ago on color theory and am
>>>>> updating my rc file based on my findings.
>>>>>
>>>>> Additionally, it would be really cool to have some kind of webapp
>>>>> whereby a user uploads their matplotlibrc file and the server generates a
>>>>> set of plots based on it.  I'm happy to take a whack at it if folks want to
>>>>> chime in and email me some example plots to render.  I would keep it to
>>>>> simple plots to start.
>>>>>
>>>>> I am aware of the plotornot "experiment" and also have rolled some of
>>>>> those features into my rc file as well (its very based off of Cam
>>>>> Davidson's)
>>>>>
>>>>> Isaac
>>>>>
>>>>> On Wed, Jan 6, 2016 at 8:53 AM, Michael Droettboom <
>>>>> mdroettboom at continuum.io> wrote:
>>>>>
>>>>>> The omnibus PR containing most of the style changes for 2.x is here:
>>>>>>
>>>>>> https://github.com/matplotlib/matplotlib/pull/5774
>>>>>>
>>>>>> This isn't everything -- some changes are already in 2.x and master.
>>>>>> Others are in separate PRs with 2.0 as a milestone.
>>>>>>
>>>>>> The new changes are being made against 2.x and are forward-ported to
>>>>>> master.
>>>>>>
>>>>>> Also, to answer Isaac's original suggestion: if you have a
>>>>>> matplotlibrc that you think would be useful for others, feel free to submit
>>>>>> it as a style.  Since 1.4, we've had a style infrastructure that makes it
>>>>>> easy for users to switch styles.  While the default style has to be very
>>>>>> carefully designed so as to provide "reasonable behavior for the most
>>>>>> common cases", individual styles do not and can be more aggressively
>>>>>> different.
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>> On Tue, Jan 5, 2016 at 10:08 PM, OceanWolf <
>>>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>>>
>>>>>>> Good question... I have gotten a bit out touch with the current
>>>>>>> state of things so I defer to others.  As far as I know the current plans
>>>>>>> at the moment only include changes to the default colormap to viridis, but
>>>>>>> others can get changed as well. feel free to post a link here, or (I guess
>>>>>>> even better), make an issue/or PR (changing rcsetup.py) on github, so that
>>>>>>> we can take it into consideration for 2.0.
>>>>>>>
>>>>>>> Looking at the state of the branches on github I have gotten a bit
>>>>>>> confused with the strategy... now we have 1.5 released and 2.0 marked as a
>>>>>>> copy of 1.5.x bar rc changes, I would have assumed the new rc changes would
>>>>>>> end up in master and then backported to the v2.x branch, but that doesn't
>>>>>>> look like the case... can someone clarify that for me?
>>>>>>>
>>>>>>> Best,
>>>>>>> OceanWolf
>>>>>>>
>>>>>>>
>>>>>>> On 06/01/16 03:26, Isaac Gerg wrote:
>>>>>>>
>>>>>>> Where is the new rcparams?
>>>>>>>
>>>>>>> On Tue, Jan 5, 2016 at 9:13 PM, OceanWolf <
>>>>>>> juichenieder-nabb at yahoo.co.uk> wrote:
>>>>>>>
>>>>>>>> Hi Isaac,
>>>>>>>> As it happens, yes, in the upcoming 2.0 release has the sole
>>>>>>>> purpose of changing rcParam defaults, see
>>>>>>>> <http://matplotlib.org/style_changes.html>
>>>>>>>> http://matplotlib.org/style_changes.html for more information.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> OceanWolf
>>>>>>>>
>>>>>>>>
>>>>>>>> On 05/01/16 23:31, Isaac Gerg wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I was wondering if there are any plans to change some of the
>>>>>>>> defaults in matplotlibrc.  I have created a matplotlibrc file that I find
>>>>>>>> very suitable and wondering if its worth sharing here.
>>>>>>>>
>>>>>>>> Isaac
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Matplotlib-devel mailing listMatplotlib-devel at python.orghttps://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Matplotlib-devel mailing list
>>>>>>>> Matplotlib-devel at python.org
>>>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Matplotlib-devel mailing list
>>>>>>> Matplotlib-devel at python.org
>>>>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Droettboom
>>>>>> Continuum Analytics
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>
> --
> Michael Droettboom
> Continuum Analytics
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160107/58d77413/attachment.html>

From tcaswell at gmail.com  Sun Jan 10 18:43:19 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 10 Jan 2016 23:43:19 +0000
Subject: [Matplotlib-devel] mpl 1.5.1 tagged + currently active branches
Message-ID: <CAA48SF-+NMDTvioGjhabzQHrcJjswd++aJuw2=FZ+z1rxR5W1A@mail.gmail.com>

Hey folks,

I have tagged 1.5.1, but will hold off a wider announcement + rebuilding
the webpage until all of the wheels are built.  The mac wheels are built by
travis and should be done already but we did not back-port the appveyor
setup to the 1.5.x branch so we are still relying on Christoph Gohlke.

I am not sure the status of conda-forge for auto-built conda packages.

For branches, our currently active branches are:

  - 1.5.1-doc: documentation (rst files and examples) only
  - 1.5.x: critical bugs.  This is a hedge against needing to do a 1.5.2
  - 2.x: style changes + any new features required to make the style
changes work
  - master: almost anything can go in.  We are holding off on traitlets +
the GUI refactor just a bit longer in case we run into any other major
problems on 2.x (to avoid a potentially really messy merge).

A big thanks to everyone who reported bugs or provided fixes for this
release!

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

From tcaswell at gmail.com  Mon Jan 11 00:02:09 2016
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 11 Jan 2016 05:02:09 +0000
Subject: [Matplotlib-devel] matplotlib v1.5.1 released
Message-ID: <CAA48SF8MKjm0QK3tkoh8AsmCto9RfQo=D+7SAcf9QpR-RooKtA@mail.gmail.com>

Hey folks,

We are happy to announce the release of matplotlib v1.5.1.

Source + wheels are available on pypi and source forge.

   pip install --upgrade matplotlib

should get you 1.5.1.

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

From bussonniermatthias at gmail.com  Thu Jan 14 12:43:38 2016
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Thu, 14 Jan 2016 09:43:38 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
Message-ID: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>

Hello matplotlib devel, 

First thanks for all the work on Matplotlib 1.5, and future 2.0 this is (and will be) awesome releases. 

As all of you are (hopefully) aware, the various colormaps that have been designed and
shipped in matplotlib 1.5 are awesome, and are now available for many languages and
graphical frameworks. 

Unfortunately, it is still common to come across both numerical and printed versions of posters
in labs and at conferences that uses our dear hated jet colormap. 

I wonder if it would  be possible to design/acquire a number of ?use viridis? and ?jet kills? stickers, 
that I could stick here and there for inapropriate use of rainbow-like colormaps, as well as on my laptop. 

Please find attached an idea of what it could look like (though I?m not good at design)
I would be happy to get the same for Inferno, magma & plasma of course,
and I think that a distribution of these stickers at the same time as Matplotlib 2.0
would be a nice communication stunt. 

Thanks, 
-- 
M







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/94854bb1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use viridis.png
Type: image/png
Size: 39184 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/94854bb1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-01-14 at 09.24.29.png
Type: image/png
Size: 133906 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/94854bb1/attachment-0003.png>

From mdroettboom at continuum.io  Thu Jan 14 14:45:26 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Thu, 14 Jan 2016 14:45:26 -0500
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
Message-ID: <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>

Also, what about "friends don't let friends use jet"...?

On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <
mdroettboom at continuum.io> wrote:

> Very cool idea.  I'd have to see where our "sticker budget" sits for the
> year, but I know a lot of people would be very excited to have something
> like this.
>
> Mike
>
> On Thu, Jan 14, 2016 at 12:43 PM, Matthias Bussonnier <
> bussonniermatthias at gmail.com> wrote:
>
>> Hello matplotlib devel,
>>
>> First thanks for all the work on Matplotlib 1.5, and future 2.0 this is
>> (and will be) awesome releases.
>>
>> As all of you are (hopefully) aware, the various colormaps that have been
>> designed and
>> shipped in matplotlib 1.5 are awesome, and are now available for many
>> languages and
>> graphical frameworks.
>>
>> Unfortunately, it is still common to come across both numerical and
>> printed versions of posters
>> in labs and at conferences that uses our dear hated jet colormap.
>>
>> I wonder if it would  be possible to design/acquire a number of ?use
>> viridis? and ?jet kills? stickers,
>> that I could stick here and there for inapropriate use of rainbow-like
>> colormaps, as well as on my laptop.
>>
>> Please find attached an idea of what it could look like (though I?m not
>> good at design)
>> I would be happy to get the same for Inferno, magma & plasma of course,
>> and I think that a distribution of these stickers at the same time as
>> Matplotlib 2.0
>> would be a nice communication stunt.
>>
>> Thanks,
>> --
>> M
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Michael Droettboom
> Continuum Analytics
>



-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/9cd81836/attachment.html>

From bussonniermatthias at gmail.com  Thu Jan 14 14:53:20 2016
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Thu, 14 Jan 2016 11:53:20 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
Message-ID: <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>


> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io> wrote:
> 
> Also, what about "friends don't let friends use jet"...?

Definitively, more on a T-shirt I guess. 

> 
> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <mdroettboom at continuum.io <mailto:mdroettboom at continuum.io>> wrote:
> Very cool idea.  I'd have to see where our "sticker budget" sits for the year, but I know a lot of people would be very excited to have something like this.
> 

Maybe there is there a way to go directly through some cross project funds at NumFocus level ?

-- 
M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/00616abc/attachment.html>

From isaac.gerg at gergltd.com  Thu Jan 14 14:33:56 2016
From: isaac.gerg at gergltd.com (Isaac Gerg)
Date: Thu, 14 Jan 2016 14:33:56 -0500
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
Message-ID: <CADnN3yVRCGLQHG4L-Po+euJ4B+Rh9H6LEcLhFzy0xojR_8of=g@mail.gmail.com>

I like the "use viridis" slogan better than jet kills, because the first
points to the solution, and the second just tells me there's a problem.

On Thu, Jan 14, 2016 at 12:43 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> Hello matplotlib devel,
>
> First thanks for all the work on Matplotlib 1.5, and future 2.0 this is
> (and will be) awesome releases.
>
> As all of you are (hopefully) aware, the various colormaps that have been
> designed and
> shipped in matplotlib 1.5 are awesome, and are now available for many
> languages and
> graphical frameworks.
>
> Unfortunately, it is still common to come across both numerical and
> printed versions of posters
> in labs and at conferences that uses our dear hated jet colormap.
>
> I wonder if it would  be possible to design/acquire a number of ?use
> viridis? and ?jet kills? stickers,
> that I could stick here and there for inapropriate use of rainbow-like
> colormaps, as well as on my laptop.
>
> Please find attached an idea of what it could look like (though I?m not
> good at design)
> I would be happy to get the same for Inferno, magma & plasma of course,
> and I think that a distribution of these stickers at the same time as
> Matplotlib 2.0
> would be a nice communication stunt.
>
> Thanks,
> --
> M
>
>
>
>
>
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/d3fad3f2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use viridis.png
Type: image/png
Size: 39184 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/d3fad3f2/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-01-14 at 09.24.29.png
Type: image/png
Size: 133906 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/d3fad3f2/attachment-0003.png>

From mdroettboom at continuum.io  Thu Jan 14 14:41:43 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Thu, 14 Jan 2016 14:41:43 -0500
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
Message-ID: <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>

Very cool idea.  I'd have to see where our "sticker budget" sits for the
year, but I know a lot of people would be very excited to have something
like this.

Mike

On Thu, Jan 14, 2016 at 12:43 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> Hello matplotlib devel,
>
> First thanks for all the work on Matplotlib 1.5, and future 2.0 this is
> (and will be) awesome releases.
>
> As all of you are (hopefully) aware, the various colormaps that have been
> designed and
> shipped in matplotlib 1.5 are awesome, and are now available for many
> languages and
> graphical frameworks.
>
> Unfortunately, it is still common to come across both numerical and
> printed versions of posters
> in labs and at conferences that uses our dear hated jet colormap.
>
> I wonder if it would  be possible to design/acquire a number of ?use
> viridis? and ?jet kills? stickers,
> that I could stick here and there for inapropriate use of rainbow-like
> colormaps, as well as on my laptop.
>
> Please find attached an idea of what it could look like (though I?m not
> good at design)
> I would be happy to get the same for Inferno, magma & plasma of course,
> and I think that a distribution of these stickers at the same time as
> Matplotlib 2.0
> would be a nice communication stunt.
>
> Thanks,
> --
> M
>
>
>
>
>
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/4705e2dc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-01-14 at 09.24.29.png
Type: image/png
Size: 133906 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/4705e2dc/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use viridis.png
Type: image/png
Size: 39184 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/4705e2dc/attachment-0003.png>

From mdroettboom at continuum.io  Thu Jan 14 15:10:12 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Thu, 14 Jan 2016 15:10:12 -0500
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
 <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
Message-ID: <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>

What about this?



?

On Thu, Jan 14, 2016 at 2:53 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

>
> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io>
> wrote:
>
> Also, what about "friends don't let friends use jet"...?
>
>
> Definitively, more on a T-shirt I guess.
>
>
> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <
> mdroettboom at continuum.io> wrote:
>
>> Very cool idea.  I'd have to see where our "sticker budget" sits for the
>> year, but I know a lot of people would be very excited to have something
>> like this.
>>
>>
> Maybe there is there a way to go directly through some cross project funds
> at NumFocus level ?
>
> --
> M
>



-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/a78b8e5d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jet.png
Type: image/png
Size: 121908 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/a78b8e5d/attachment-0001.png>

From bussonniermatthias at gmail.com  Thu Jan 14 20:36:14 2016
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Thu, 14 Jan 2016 17:36:14 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
 <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
 <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>
Message-ID: <CANJQusWYkJ4gY53RUK5RfjQgTsjqdBm1XP+JDM7N1teZeRnaOQ@mail.gmail.com>

Forgot to reply-all:

> Maybe a bit too ..."subtle" :-)

Also, following Nathaniel Smith suggestion, I registered `useviridis.org`
and `jetkills.org`.  I'd be happy to make the DNS point to a custom page
that point to the merits of viridis / the drawback of Jet.
I would be also happy to hand over the control of the domain(s) if asked.

Also regarding "sticker budget", does it make sens /is it legally ok for
numfocus to set up a cafepress account that sells these stickers ?

-- 
M

On Thu, Jan 14, 2016 at 12:10 PM, Michael Droettboom <
mdroettboom at continuum.io> wrote:

> What about this?
>
>
>
> ?
>
> On Thu, Jan 14, 2016 at 2:53 PM, Matthias Bussonnier <
> bussonniermatthias at gmail.com> wrote:
>
>>
>> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io>
>> wrote:
>>
>> Also, what about "friends don't let friends use jet"...?
>>
>>
>> Definitively, more on a T-shirt I guess.
>>
>>
>> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <
>> mdroettboom at continuum.io> wrote:
>>
>>> Very cool idea.  I'd have to see where our "sticker budget" sits for the
>>> year, but I know a lot of people would be very excited to have something
>>> like this.
>>>
>>>
>> Maybe there is there a way to go directly through some cross project
>> funds at NumFocus level ?
>>
>> --
>> M
>>
>
>
>
> --
> Michael Droettboom
> Continuum Analytics
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/f62cf1d0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jet.png
Type: image/png
Size: 121908 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160114/f62cf1d0/attachment-0001.png>

From ellisonbg at gmail.com  Fri Jan 15 16:09:15 2016
From: ellisonbg at gmail.com (Brian Granger)
Date: Fri, 15 Jan 2016 13:09:15 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <0D865BAB-AB9A-4894-84A1-C18C4465D005@gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
 <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
 <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>
 <CANJQusWYkJ4gY53RUK5RfjQgTsjqdBm1XP+JDM7N1teZeRnaOQ@mail.gmail.com>
 <CAH4pYpSS1+nhU4eKX4qTKzTP9Ku7UDi72fRMyukO0qYa0wB=Hg@mail.gmail.com>
 <0D865BAB-AB9A-4894-84A1-C18C4465D005@gmail.com>
Message-ID: <CAH4pYpQ5CzDfVPKgJirK-QL1xNYhf1KMiWxJmvCJ0sbdA0ytGg@mail.gmail.com>

I would email Cameron, myself, Mike D. and Thomas C. to get the
discussion started. Oh and possibly Stefan and Nathaniel.

On Fri, Jan 15, 2016 at 1:06 PM, Matthias Bussonnier
<bussonniermatthias at gmail.com> wrote:
>
> On Jan 15, 2016, at 13:03, Brian Granger <ellisonbg at gmail.com> wrote:
>
> Maybe have Cameron take a pass at a super nice viridis logo?
>
>
>
> Well, I was going to ask you at next dev meeting...
>
> Should maybe open an issue somewhere on some GitHub repository ?
> --
> M
>
>
>
> On Thu, Jan 14, 2016 at 5:36 PM, Matthias Bussonnier
> <bussonniermatthias at gmail.com> wrote:
>>
>> Forgot to reply-all:
>>
>> > Maybe a bit too ..."subtle" :-)
>>
>> Also, following Nathaniel Smith suggestion, I registered `useviridis.org`
>> and `jetkills.org`.  I'd be happy to make the DNS point to a custom page
>> that point to the merits of viridis / the drawback of Jet.
>> I would be also happy to hand over the control of the domain(s) if asked.
>>
>> Also regarding "sticker budget", does it make sens /is it legally ok for
>> numfocus to set up a cafepress account that sells these stickers ?
>>
>> --
>> M
>>
>> On Thu, Jan 14, 2016 at 12:10 PM, Michael Droettboom
>> <mdroettboom at continuum.io> wrote:
>>>
>>> What about this?
>>>
>>>
>>> <jet.png>
>>>
>>>
>>> On Thu, Jan 14, 2016 at 2:53 PM, Matthias Bussonnier
>>> <bussonniermatthias at gmail.com> wrote:
>>>>
>>>>
>>>> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io>
>>>> wrote:
>>>>
>>>> Also, what about "friends don't let friends use jet"...?
>>>>
>>>>
>>>> Definitively, more on a T-shirt I guess.
>>>>
>>>>
>>>> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom
>>>> <mdroettboom at continuum.io> wrote:
>>>>>
>>>>> Very cool idea.  I'd have to see where our "sticker budget" sits for
>>>>> the year, but I know a lot of people would be very excited to have something
>>>>> like this.
>>>>>
>>>>
>>>> Maybe there is there a way to go directly through some cross project
>>>> funds at NumFocus level ?
>>>>
>>>> --
>>>> M
>>>
>>>
>>>
>>>
>>> --
>>> Michael Droettboom
>>> Continuum Analytics
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
>
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgranger at calpoly.edu and ellisonbg at gmail.com
>
>



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com

From bussonniermatthias at gmail.com  Fri Jan 15 16:06:51 2016
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Fri, 15 Jan 2016 13:06:51 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <CAH4pYpSS1+nhU4eKX4qTKzTP9Ku7UDi72fRMyukO0qYa0wB=Hg@mail.gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
 <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
 <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>
 <CANJQusWYkJ4gY53RUK5RfjQgTsjqdBm1XP+JDM7N1teZeRnaOQ@mail.gmail.com>
 <CAH4pYpSS1+nhU4eKX4qTKzTP9Ku7UDi72fRMyukO0qYa0wB=Hg@mail.gmail.com>
Message-ID: <0D865BAB-AB9A-4894-84A1-C18C4465D005@gmail.com>


> On Jan 15, 2016, at 13:03, Brian Granger <ellisonbg at gmail.com> wrote:
> 
> Maybe have Cameron take a pass at a super nice viridis logo?


Well, I was going to ask you at next dev meeting...

Should maybe open an issue somewhere on some GitHub repository ?
-- 
M


> 
> On Thu, Jan 14, 2016 at 5:36 PM, Matthias Bussonnier <bussonniermatthias at gmail.com <mailto:bussonniermatthias at gmail.com>> wrote:
> Forgot to reply-all:
> 
> > Maybe a bit too ..."subtle" :-)  
> 
> Also, following Nathaniel Smith suggestion, I registered `useviridis.org <http://useviridis.org/>` and `jetkills.org <http://jetkills.org/>`.  I'd be happy to make the DNS point to a custom page that point to the merits of viridis / the drawback of Jet.
> I would be also happy to hand over the control of the domain(s) if asked.
> 
> Also regarding "sticker budget", does it make sens /is it legally ok for numfocus to set up a cafepress account that sells these stickers ?
> 
> -- 
> M
> 
> On Thu, Jan 14, 2016 at 12:10 PM, Michael Droettboom <mdroettboom at continuum.io <mailto:mdroettboom at continuum.io>> wrote:
> What about this?
> 
> 
> <jet.png>
> ?
> 
> On Thu, Jan 14, 2016 at 2:53 PM, Matthias Bussonnier <bussonniermatthias at gmail.com <mailto:bussonniermatthias at gmail.com>> wrote:
> 
>> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io <mailto:mdroettboom at continuum.io>> wrote:
>> 
>> Also, what about "friends don't let friends use jet"...?
> 
> Definitively, more on a T-shirt I guess. 
> 
>> 
>> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <mdroettboom at continuum.io <mailto:mdroettboom at continuum.io>> wrote:
>> Very cool idea.  I'd have to see where our "sticker budget" sits for the year, but I know a lot of people would be very excited to have something like this.
>> 
> 
> Maybe there is there a way to go directly through some cross project funds at NumFocus level ?
> 
> -- 
> M
> 
> 
> 
> -- 
> Michael Droettboom
> Continuum Analytics
> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
> https://mail.python.org/mailman/listinfo/matplotlib-devel <https://mail.python.org/mailman/listinfo/matplotlib-devel>
> 
> 
> 
> 
> -- 
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgranger at calpoly.edu <mailto:bgranger at calpoly.edu> and ellisonbg at gmail.com <mailto:ellisonbg at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160115/b5ebb13d/attachment.html>

From ellisonbg at gmail.com  Fri Jan 15 16:03:56 2016
From: ellisonbg at gmail.com (Brian Granger)
Date: Fri, 15 Jan 2016 13:03:56 -0800
Subject: [Matplotlib-devel] Where can I get "Use viridis" Stickers ?
In-Reply-To: <CANJQusWYkJ4gY53RUK5RfjQgTsjqdBm1XP+JDM7N1teZeRnaOQ@mail.gmail.com>
References: <B5C1FE5C-9CEA-4435-A3C9-DB38DF42ACF5@gmail.com>
 <CADsn3C2Bh7jfU3iLJMhN-+1o7xsOnMdMFbXfv+FEaU70=5eSrw@mail.gmail.com>
 <CADsn3C3a5+5vTbfvDS3_XYdEZi1XPDyLFp3-fTrHuYxuQHXO3A@mail.gmail.com>
 <9313F06F-FEEE-447D-9655-73333AE8A813@gmail.com>
 <CADsn3C2L3ZgRxd8VsLFw+Q_cB9nyH+Zhwd70mo_oEhEG=1Zscg@mail.gmail.com>
 <CANJQusWYkJ4gY53RUK5RfjQgTsjqdBm1XP+JDM7N1teZeRnaOQ@mail.gmail.com>
Message-ID: <CAH4pYpSS1+nhU4eKX4qTKzTP9Ku7UDi72fRMyukO0qYa0wB=Hg@mail.gmail.com>

Maybe have Cameron take a pass at a super nice viridis logo?

On Thu, Jan 14, 2016 at 5:36 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> Forgot to reply-all:
>
> > Maybe a bit too ..."subtle" :-)
>
> Also, following Nathaniel Smith suggestion, I registered `useviridis.org`
> and `jetkills.org`.  I'd be happy to make the DNS point to a custom page
> that point to the merits of viridis / the drawback of Jet.
> I would be also happy to hand over the control of the domain(s) if asked.
>
> Also regarding "sticker budget", does it make sens /is it legally ok for
> numfocus to set up a cafepress account that sells these stickers ?
>
> --
> M
>
> On Thu, Jan 14, 2016 at 12:10 PM, Michael Droettboom <
> mdroettboom at continuum.io> wrote:
>
>> What about this?
>>
>>
>>
>> ?
>>
>> On Thu, Jan 14, 2016 at 2:53 PM, Matthias Bussonnier <
>> bussonniermatthias at gmail.com> wrote:
>>
>>>
>>> On Jan 14, 2016, at 11:45, Michael Droettboom <mdroettboom at continuum.io>
>>> wrote:
>>>
>>> Also, what about "friends don't let friends use jet"...?
>>>
>>>
>>> Definitively, more on a T-shirt I guess.
>>>
>>>
>>> On Thu, Jan 14, 2016 at 2:41 PM, Michael Droettboom <
>>> mdroettboom at continuum.io> wrote:
>>>
>>>> Very cool idea.  I'd have to see where our "sticker budget" sits for
>>>> the year, but I know a lot of people would be very excited to have
>>>> something like this.
>>>>
>>>>
>>> Maybe there is there a way to go directly through some cross project
>>> funds at NumFocus level ?
>>>
>>> --
>>> M
>>>
>>
>>
>>
>> --
>> Michael Droettboom
>> Continuum Analytics
>>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160115/4932f2a4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jet.png
Type: image/png
Size: 121908 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160115/4932f2a4/attachment-0001.png>

From safia at safia.rocks  Mon Jan 18 16:02:34 2016
From: safia at safia.rocks (Safia Abdalla)
Date: Mon, 18 Jan 2016 15:02:34 -0600
Subject: [Matplotlib-devel] PyData Chicago Sprint Volunteers
Message-ID: <CAJ2PXePOXX8_FL7BHmWQ2NaTHQ7DxN=6mxAydDOXBcCAifFxPQ@mail.gmail.com>

Hello,

I'm a developer on Project Jupyter and the organizer of the PyData Chicago.

I'm currently working on organizing monthly open-source sprints for the
Chicago chapter of PyData. The sprints will occur on the third Tuesday
evening of each month. Each sprint will consist of 5 divisions, each
focused on a NumFOCUS-sponsored project. Each of the divisions will be
mentored by an individual with particular expertise in that project.
Mentors prepare a particular set of issues to guide the team through,
provide guidance on open source contribution and TDD, and tell funny jokes
to keep people from going insane at the hands of bad bugs.

I was wondering if there were any matplotlib contributors in Chicago on
this list would be interested in being a mentor for the matplotib division.
The commitment will involve attending the sprints every other month and
selecting issues prior to each sprint that you will guide division
participants through.

If anyone is interested, feel free to send me an email at safia -at- safia
-dot- rocks. Feel free to send emails with any questions as well.

Looking forward to hearing from you folks!

Thanks,
Safia
@captainsafia on Twitter and GitHub
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160118/bd4963ff/attachment.html>

From paulstar at msn.com  Wed Jan 20 00:46:47 2016
From: paulstar at msn.com (pstarrett)
Date: Tue, 19 Jan 2016 22:46:47 -0700 (MST)
Subject: [Matplotlib-devel] Install of matplotlib into Python 3.4 virtual env
Message-ID: <1453268807243-46664.post@n5.nabble.com>

I have tried numerous ways to install matplotlib into a Python 3.4 virtual
environment with no luck. I have tried many variations of pip, easy_install
and apt-get (which installs globally automatically so is not useful). Thank
you!



--
View this message in context: http://matplotlib.1069221.n5.nabble.com/Install-of-matplotlib-into-Python-3-4-virtual-env-tp46664.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

From miketercek at yahoo.com  Fri Jan 22 03:43:39 2016
From: miketercek at yahoo.com (Mike Tercek)
Date: Fri, 22 Jan 2016 08:43:39 +0000 (UTC)
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
References: <1357899474.2057053.1453452219837.JavaMail.yahoo.ref@mail.yahoo.com>
Message-ID: <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>

When I make a map with the basemap and try to insert a background image from acrgis servers, the following code works ok if I have maplotlib version 1.3.1 installed:
m = Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz, fix_aspect = False)m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)
However, if I have matplotlib version 1.4.3 installed I get the following error:
Python 3.4.3 (default, Oct 14 2015, 20:28:29)?[GCC 4.8.4] on linuxType "help", "copyright", "credits" or "license" for more information.>>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py', wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')Content-Type: text/html
Traceback (most recent call last):? File "<stdin>", line 1, in <module>? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 680, in runfile? ? execfile(filename, namespace)? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 85, in execfile? ? exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in <module>? ? m,fig = make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in make_base_map? ? m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)? File "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py", line 4270, in arcgisimage? ? return self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')? File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line 1270, in imread? ? return handler(fname)RuntimeError: _image_module::readpng: file not recognized as a PNG file
And if I install matplotlib 1.5.1, I get this error:
Python 3.4.3 (default, Oct 14 2015, 20:28:29)?[GCC 4.8.4] on linuxType "help", "copyright", "credits" or "license" for more information.>>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py', wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')Content-Type: text/html
Traceback (most recent call last):? File "<stdin>", line 1, in <module>? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 680, in runfile? ? execfile(filename, namespace)? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 85, in execfile? ? exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in <module>? ? m,fig = make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in make_base_map? ? m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)? File "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py", line 4270, in arcgisimage? ? return self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')? File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line 1326, in imread? ? return handler(fname)SystemError: error return without exception set

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

From ben.v.root at gmail.com  Mon Jan 25 10:53:02 2016
From: ben.v.root at gmail.com (Benjamin Root)
Date: Mon, 25 Jan 2016 10:53:02 -0500
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
In-Reply-To: <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>
References: <1357899474.2057053.1453452219837.JavaMail.yahoo.ref@mail.yahoo.com>
 <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <CANNq6F=+_X+ovGEht2YpnTnE=nJQ0LtSEFO8YNT5U2WmwXZekQ@mail.gmail.com>

Yes, I recently noticed this, too. CC-ing Mike Droettboom, I think this is
caused by our recent changes to _image.cpp to add error-checking.

Ben Root

On Fri, Jan 22, 2016 at 3:43 AM, Mike Tercek via Matplotlib-devel <
matplotlib-devel at python.org> wrote:

> When I make a map with the basemap and try to insert a background image
> from acrgis servers, the following code works ok if I have maplotlib
> version 1.3.1 installed:
>
> m =
> Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz,
> fix_aspect = False)
> m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose=
> False, dpi = 80)
>
> However, if I have matplotlib version 1.4.3 installed I get the following
> error:
>
> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
> [GCC 4.8.4] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
> Content-Type: text/html
>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File
> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
> line 680, in runfile
>     execfile(filename, namespace)
>   File
> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
> line 85, in execfile
>     exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)
>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
> <module>
>     m,fig =
> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
> make_base_map
>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
> verbose= False, dpi = 80)
>   File
> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
> line 4270, in arcgisimage
>     return
> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line
> 1270, in imread
>     return handler(fname)
> RuntimeError: _image_module::readpng: file not recognized as a PNG file
>
> And if I install matplotlib 1.5.1, I get this error:
>
> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
> [GCC 4.8.4] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
> Content-Type: text/html
>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File
> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
> line 680, in runfile
>     execfile(filename, namespace)
>   File
> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
> line 85, in execfile
>     exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)
>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
> <module>
>     m,fig =
> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
> make_base_map
>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
> verbose= False, dpi = 80)
>   File
> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
> line 4270, in arcgisimage
>     return
> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line
> 1326, in imread
>     return handler(fname)
> SystemError: error return without exception set
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160125/d28d4042/attachment.html>

From mdroettboom at continuum.io  Mon Jan 25 11:32:03 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Mon, 25 Jan 2016 11:32:03 -0500
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
In-Reply-To: <CANNq6F=+_X+ovGEht2YpnTnE=nJQ0LtSEFO8YNT5U2WmwXZekQ@mail.gmail.com>
References: <1357899474.2057053.1453452219837.JavaMail.yahoo.ref@mail.yahoo.com>
 <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>
 <CANNq6F=+_X+ovGEht2YpnTnE=nJQ0LtSEFO8YNT5U2WmwXZekQ@mail.gmail.com>
Message-ID: <CADsn3C3Mqgw0-30d1v2XAByJ-tzNzq0qfXpp_bz+ktfNrA99sw@mail.gmail.com>

Can you provide a standalone example to reproduce, or fire up the debugger
and let me know that the value of "basemap_url" is on line 4270 of
basemap/__init__.py?  Were that to point to somewhere that fails, one would
expect this error.  (Though in the case of 1.5.1 something additionally
funky is going on, I'm not necessarily surprised by the result with 1.4.3
without additional information).

Mike

On Mon, Jan 25, 2016 at 10:53 AM, Benjamin Root <ben.v.root at gmail.com>
wrote:

> Yes, I recently noticed this, too. CC-ing Mike Droettboom, I think this is
> caused by our recent changes to _image.cpp to add error-checking.
>
> Ben Root
>
> On Fri, Jan 22, 2016 at 3:43 AM, Mike Tercek via Matplotlib-devel <
> matplotlib-devel at python.org> wrote:
>
>> When I make a map with the basemap and try to insert a background image
>> from acrgis servers, the following code works ok if I have maplotlib
>> version 1.3.1 installed:
>>
>> m =
>> Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz,
>> fix_aspect = False)
>> m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose=
>> False, dpi = 80)
>>
>> However, if I have matplotlib version 1.4.3 installed I get the following
>> error:
>>
>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>> [GCC 4.8.4] on linux
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>> Content-Type: text/html
>>
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>>   File
>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>> line 680, in runfile
>>     execfile(filename, namespace)
>>   File
>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>> line 85, in execfile
>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>> namespace)
>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>> <module>
>>     m,fig =
>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>> make_base_map
>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>> verbose= False, dpi = 80)
>>   File
>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>> line 4270, in arcgisimage
>>     return
>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line
>> 1270, in imread
>>     return handler(fname)
>> RuntimeError: _image_module::readpng: file not recognized as a PNG file
>>
>> And if I install matplotlib 1.5.1, I get this error:
>>
>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>> [GCC 4.8.4] on linux
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>> Content-Type: text/html
>>
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>>   File
>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>> line 680, in runfile
>>     execfile(filename, namespace)
>>   File
>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>> line 85, in execfile
>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>> namespace)
>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>> <module>
>>     m,fig =
>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>> make_base_map
>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>> verbose= False, dpi = 80)
>>   File
>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>> line 4270, in arcgisimage
>>     return
>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line
>> 1326, in imread
>>     return handler(fname)
>> SystemError: error return without exception set
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160125/f6dc665a/attachment-0001.html>

From ben.v.root at gmail.com  Mon Jan 25 11:59:07 2016
From: ben.v.root at gmail.com (Benjamin Root)
Date: Mon, 25 Jan 2016 11:59:07 -0500
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
In-Reply-To: <CADsn3C3Mqgw0-30d1v2XAByJ-tzNzq0qfXpp_bz+ktfNrA99sw@mail.gmail.com>
References: <1357899474.2057053.1453452219837.JavaMail.yahoo.ref@mail.yahoo.com>
 <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>
 <CANNq6F=+_X+ovGEht2YpnTnE=nJQ0LtSEFO8YNT5U2WmwXZekQ@mail.gmail.com>
 <CADsn3C3Mqgw0-30d1v2XAByJ-tzNzq0qfXpp_bz+ktfNrA99sw@mail.gmail.com>
Message-ID: <CANNq6Fm6cp4m==FH8ogTbN4my_dzoyanzY2nB5kbs88wSj7tMA@mail.gmail.com>

Mike, this is where I noticed this before:
https://github.com/matplotlib/basemap/issues/242

Simple example:

import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap
m=Basemap(projection='cyl',llcrnrlon=-90,llcrnrlat=30,urcrnrlon=-60,urcrnrlat=60)
m.arcgisimage(verbose=True)
plt.show()


Ben Root



On Mon, Jan 25, 2016 at 11:32 AM, Michael Droettboom <
mdroettboom at continuum.io> wrote:

> Can you provide a standalone example to reproduce, or fire up the debugger
> and let me know that the value of "basemap_url" is on line 4270 of
> basemap/__init__.py?  Were that to point to somewhere that fails, one would
> expect this error.  (Though in the case of 1.5.1 something additionally
> funky is going on, I'm not necessarily surprised by the result with 1.4.3
> without additional information).
>
> Mike
>
> On Mon, Jan 25, 2016 at 10:53 AM, Benjamin Root <ben.v.root at gmail.com>
> wrote:
>
>> Yes, I recently noticed this, too. CC-ing Mike Droettboom, I think this
>> is caused by our recent changes to _image.cpp to add error-checking.
>>
>> Ben Root
>>
>> On Fri, Jan 22, 2016 at 3:43 AM, Mike Tercek via Matplotlib-devel <
>> matplotlib-devel at python.org> wrote:
>>
>>> When I make a map with the basemap and try to insert a background image
>>> from acrgis servers, the following code works ok if I have maplotlib
>>> version 1.3.1 installed:
>>>
>>> m =
>>> Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz,
>>> fix_aspect = False)
>>> m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose=
>>> False, dpi = 80)
>>>
>>> However, if I have matplotlib version 1.4.3 installed I get the
>>> following error:
>>>
>>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>>> [GCC 4.8.4] on linux
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>>> Content-Type: text/html
>>>
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in <module>
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>> line 680, in runfile
>>>     execfile(filename, namespace)
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>> line 85, in execfile
>>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>>> namespace)
>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>>> <module>
>>>     m,fig =
>>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>>> make_base_map
>>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>>> verbose= False, dpi = 80)
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>>> line 4270, in arcgisimage
>>>     return
>>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py",
>>> line 1270, in imread
>>>     return handler(fname)
>>> RuntimeError: _image_module::readpng: file not recognized as a PNG file
>>>
>>> And if I install matplotlib 1.5.1, I get this error:
>>>
>>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>>> [GCC 4.8.4] on linux
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>>> Content-Type: text/html
>>>
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in <module>
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>> line 680, in runfile
>>>     execfile(filename, namespace)
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>> line 85, in execfile
>>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>>> namespace)
>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>>> <module>
>>>     m,fig =
>>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>>> make_base_map
>>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>>> verbose= False, dpi = 80)
>>>   File
>>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>>> line 4270, in arcgisimage
>>>     return
>>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py",
>>> line 1326, in imread
>>>     return handler(fname)
>>> SystemError: error return without exception set
>>>
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>
>>>
>>
>
>
> --
> Michael Droettboom
> Continuum Analytics
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160125/fa8474d2/attachment.html>

From mdroettboom at continuum.io  Mon Jan 25 12:13:31 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Mon, 25 Jan 2016 12:13:31 -0500
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
In-Reply-To: <CANNq6Fm6cp4m==FH8ogTbN4my_dzoyanzY2nB5kbs88wSj7tMA@mail.gmail.com>
References: <1357899474.2057053.1453452219837.JavaMail.yahoo.ref@mail.yahoo.com>
 <1357899474.2057053.1453452219837.JavaMail.yahoo@mail.yahoo.com>
 <CANNq6F=+_X+ovGEht2YpnTnE=nJQ0LtSEFO8YNT5U2WmwXZekQ@mail.gmail.com>
 <CADsn3C3Mqgw0-30d1v2XAByJ-tzNzq0qfXpp_bz+ktfNrA99sw@mail.gmail.com>
 <CANNq6Fm6cp4m==FH8ogTbN4my_dzoyanzY2nB5kbs88wSj7tMA@mail.gmail.com>
Message-ID: <CADsn3C2c-6jj=CUyEpFnemRMdVgGVX7vMf4hVShtCLC4hk+cQg@mail.gmail.com>

I think https://github.com/matplotlib/matplotlib/pull/5910 should fix it.

On Mon, Jan 25, 2016 at 11:59 AM, Benjamin Root <ben.v.root at gmail.com>
wrote:

> Mike, this is where I noticed this before:
> https://github.com/matplotlib/basemap/issues/242
>
> Simple example:
>
> import matplotlib.pyplot as plt
> from mpl_toolkits.basemap import Basemap
>
> m=Basemap(projection='cyl',llcrnrlon=-90,llcrnrlat=30,urcrnrlon=-60,urcrnrlat=60)
> m.arcgisimage(verbose=True)
> plt.show()
>
>
> Ben Root
>
>
>
> On Mon, Jan 25, 2016 at 11:32 AM, Michael Droettboom <
> mdroettboom at continuum.io> wrote:
>
>> Can you provide a standalone example to reproduce, or fire up the
>> debugger and let me know that the value of "basemap_url" is on line 4270 of
>> basemap/__init__.py?  Were that to point to somewhere that fails, one would
>> expect this error.  (Though in the case of 1.5.1 something additionally
>> funky is going on, I'm not necessarily surprised by the result with 1.4.3
>> without additional information).
>>
>> Mike
>>
>> On Mon, Jan 25, 2016 at 10:53 AM, Benjamin Root <ben.v.root at gmail.com>
>> wrote:
>>
>>> Yes, I recently noticed this, too. CC-ing Mike Droettboom, I think this
>>> is caused by our recent changes to _image.cpp to add error-checking.
>>>
>>> Ben Root
>>>
>>> On Fri, Jan 22, 2016 at 3:43 AM, Mike Tercek via Matplotlib-devel <
>>> matplotlib-devel at python.org> wrote:
>>>
>>>> When I make a map with the basemap and try to insert a background image
>>>> from acrgis servers, the following code works ok if I have maplotlib
>>>> version 1.3.1 installed:
>>>>
>>>> m =
>>>> Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz,
>>>> fix_aspect = False)
>>>> m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose=
>>>> False, dpi = 80)
>>>>
>>>> However, if I have matplotlib version 1.4.3 installed I get the
>>>> following error:
>>>>
>>>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>>>> [GCC 4.8.4] on linux
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>>>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>>>> Content-Type: text/html
>>>>
>>>> Traceback (most recent call last):
>>>>   File "<stdin>", line 1, in <module>
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>>> line 680, in runfile
>>>>     execfile(filename, namespace)
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>>> line 85, in execfile
>>>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>>>> namespace)
>>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>>>> <module>
>>>>     m,fig =
>>>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>>>> make_base_map
>>>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>>>> verbose= False, dpi = 80)
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>>>> line 4270, in arcgisimage
>>>>     return
>>>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py",
>>>> line 1270, in imread
>>>>     return handler(fname)
>>>> RuntimeError: _image_module::readpng: file not recognized as a PNG file
>>>>
>>>> And if I install matplotlib 1.5.1, I get this error:
>>>>
>>>> Python 3.4.3 (default, Oct 14 2015, 20:28:29)
>>>> [GCC 4.8.4] on linux
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py',
>>>> wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')
>>>> Content-Type: text/html
>>>>
>>>> Traceback (most recent call last):
>>>>   File "<stdin>", line 1, in <module>
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>>> line 680, in runfile
>>>>     execfile(filename, namespace)
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py",
>>>> line 85, in execfile
>>>>     exec(compile(open(filename, 'rb').read(), filename, 'exec'),
>>>> namespace)
>>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in
>>>> <module>
>>>>     m,fig =
>>>> make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)
>>>>   File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in
>>>> make_base_map
>>>>     m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000,
>>>> verbose= False, dpi = 80)
>>>>   File
>>>> "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py",
>>>> line 4270, in arcgisimage
>>>>     return
>>>> self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')
>>>>   File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py",
>>>> line 1326, in imread
>>>>     return handler(fname)
>>>> SystemError: error return without exception set
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at python.org
>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>>>
>>>>
>>>
>>
>>
>> --
>> Michael Droettboom
>> Continuum Analytics
>>
>
>


-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160125/bf87c5a2/attachment.html>

From miketercek at yahoo.com  Mon Jan 25 12:44:20 2016
From: miketercek at yahoo.com (Mike Tercek)
Date: Mon, 25 Jan 2016 17:44:20 +0000 (UTC)
Subject: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and
 higher with basemap arcgisimage imagery
In-Reply-To: <CANNq6Fm6cp4m==FH8ogTbN4my_dzoyanzY2nB5kbs88wSj7tMA@mail.gmail.com>
References: <CANNq6Fm6cp4m==FH8ogTbN4my_dzoyanzY2nB5kbs88wSj7tMA@mail.gmail.com>
Message-ID: <1262536350.804673.1453743860801.JavaMail.yahoo@mail.yahoo.com>

Yes, this is the same issue that I am having.
Thanks,
Mike
 

      From: Benjamin Root <ben.v.root at gmail.com>
 To: Michael Droettboom <mdroettboom at continuum.io> 
Cc: Mike Tercek <miketercek at yahoo.com>; "matplotlib-devel at python.org" <matplotlib-devel at python.org>
 Sent: Monday, January 25, 2016 9:59 AM
 Subject: Re: [Matplotlib-devel] Possible bug in matplotlib versions 1.4 and higher with basemap arcgisimage imagery
   
Mike, this is where I noticed this before: https://github.com/matplotlib/basemap/issues/242

Simple example:

import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap
m=Basemap(projection='cyl',llcrnrlon=-90,llcrnrlat=30,urcrnrlon=-60,urcrnrlat=60)
m.arcgisimage(verbose=True)
plt.show()

Ben Root

On Mon, Jan 25, 2016 at 11:32 AM, Michael Droettboom <mdroettboom at continuum.io> wrote:

Can you provide a standalone example to reproduce, or fire up the debugger and let me know that the value of "basemap_url" is on line 4270 of basemap/__init__.py?? Were that to point to somewhere that fails, one would expect this error. ?(Though in the case of 1.5.1 something additionally funky is going on, I'm not necessarily surprised by the result with 1.4.3 without additional information).
Mike
On Mon, Jan 25, 2016 at 10:53 AM, Benjamin Root <ben.v.root at gmail.com> wrote:

Yes, I recently noticed this, too. CC-ing Mike Droettboom, I think this is caused by our recent changes to _image.cpp to add error-checking.

Ben Root

On Fri, Jan 22, 2016 at 3:43 AM, Mike Tercek via Matplotlib-devel <matplotlib-devel at python.org> wrote:

When I make a map with the basemap and try to insert a background image from acrgis servers, the following code works ok if I have maplotlib version 1.3.1 installed:
m = Basemap(llcrnrlon=ll_lon,llcrnrlat=ll_lat,urcrnrlon=ur_lon,urcrnrlat=ur_lat,epsg=3857,lat_0=latz,lon_0=lonz, fix_aspect = False)m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)
However, if I have matplotlib version 1.4.3 installed I get the following error:
Python 3.4.3 (default, Oct 14 2015, 20:28:29)?[GCC 4.8.4] on linuxType "help", "copyright", "credits" or "license" for more information.>>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py', wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')Content-Type: text/html
Traceback (most recent call last):? File "<stdin>", line 1, in <module>? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 680, in runfile? ? execfile(filename, namespace)? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 85, in execfile? ? exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in <module>? ? m,fig = make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in make_base_map? ? m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)? File "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py", line 4270, in arcgisimage? ? return self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')? File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line 1270, in imread? ? return handler(fname)RuntimeError: _image_module::readpng: file not recognized as a PNG file
And if I install matplotlib 1.5.1, I get this error:
Python 3.4.3 (default, Oct 14 2015, 20:28:29)?[GCC 4.8.4] on linuxType "help", "copyright", "credits" or "license" for more information.>>> runfile('/media/mt/7670100C700FD1B3/vegviz/contain/xv.py', wdir=r'/media/mt/7670100C700FD1B3/vegviz/contain')Content-Type: text/html
Traceback (most recent call last):? File "<stdin>", line 1, in <module>? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 680, in runfile? ? execfile(filename, namespace)? File "/usr/local/lib/python3.4/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 85, in execfile? ? exec(compile(open(filename, 'rb').read(), filename, 'exec'), namespace)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 401, in <module>? ? m,fig = make_base_map(title,frame_bound,park_bound,inset,inset_location,inset_alignment,ll_lon,ll_lat,ur_lon,ur_lat,latz,lonz,True)? File "/media/mt/7670100C700FD1B3/vegviz/contain/xv.py", line 110, in make_base_map? ? m.arcgisimage(service='ESRI_Imagery_World_2D', xpixels = 2000, verbose= False, dpi = 80)? File "/usr/local/lib/python3.4/dist-packages/mpl_toolkits/basemap/__init__.py", line 4270, in arcgisimage? ? return self.imshow(imread(urllib.request.urlopen(basemap_url)),origin='upper')? File "/usr/local/lib/python3.4/dist-packages/matplotlib/image.py", line 1326, in imread? ? return handler(fname)SystemError: error return without exception set


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







-- 
Michael DroettboomContinuum Analytics



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

From mdroettboom at continuum.io  Mon Jan 25 16:59:10 2016
From: mdroettboom at continuum.io (Michael Droettboom)
Date: Mon, 25 Jan 2016 16:59:10 -0500
Subject: [Matplotlib-devel] Matplotlib meeting minutes 2016-01-25
Message-ID: <CADsn3C3SU=ndJ_Xd6F5MWuQm-fc5WynyZbC5QbKsvC-+2daA7w@mail.gmail.com>

In attendance: Michael Droettboom, Thomas Caswell, Jens Nielsen and Erik
Firing

- Jan Schulz (working on AppVeyor integration and all things Windowsy and
annoying) have been offered some help by the Anaconda team at Continuum to
make building Windows conda packages easier and using conda in the AppVeyor
environment easier.  Windows integration testing is a major pain point, so
this is all very welcome.

- We are all in favor of creating a matplotlib-nogui package for Anaconda.
The existing matplotlib package would become a metapackage that would bring
in Qt and Tkinter.  It's an open question as to how far the Anaconda
distribution wants to go with using matplotlib-nogui instead (Jupyter could
reasonably be changed to depend only on matplotlib-nogui, for example).

- The style omnibus PR is essentially feature complete -- Mike will
investigate and fix test failures

- The overriding of defaults by `%matplotlib inline` mode in Jupyter
notebook remains a major source of user bugs.  Not sure how to resolve,
though.

-- 
Michael Droettboom
Continuum Analytics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160125/63cf3cca/attachment.html>

From pelson.pub at gmail.com  Thu Jan 28 04:19:13 2016
From: pelson.pub at gmail.com (Phil Elson)
Date: Thu, 28 Jan 2016 09:19:13 +0000
Subject: [Matplotlib-devel] Install of matplotlib into Python 3.4
 virtual env
In-Reply-To: <1453268807243-46664.post@n5.nabble.com>
References: <1453268807243-46664.post@n5.nabble.com>
Message-ID: <CA+L60sDbqsp-GDzxArvymvYFhcHtB6e8YG93E2Nv_U2ekTSJiQ@mail.gmail.com>

Given the C dependencies of matplotlib, have you considered installing
matplotlib with conda?
That said, the pip solution should work, so it would be interesting to see
what the issues were.

Cheers,

On 20 January 2016 at 05:46, pstarrett <paulstar at msn.com> wrote:

> I have tried numerous ways to install matplotlib into a Python 3.4 virtual
> environment with no luck. I have tried many variations of pip, easy_install
> and apt-get (which installs globally automatically so is not useful). Thank
> you!
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/Install-of-matplotlib-into-Python-3-4-virtual-env-tp46664.html
> Sent from the matplotlib - devel mailing list archive at Nabble.com.
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160128/b243513a/attachment.html>

From mp21 at sanger.ac.uk  Fri Jan 29 06:53:09 2016
From: mp21 at sanger.ac.uk (My Phan)
Date: Fri, 29 Jan 2016 11:53:09 +0000
Subject: [Matplotlib-devel] CTFontLogSuboptimalRequest
Message-ID: <D2D10322.10A57%mp21@sanger.ac.uk>

Hello,

I have recently re-installed Matplotlib v1.5.1 because of Segmentation Fault 11. This seg fault was fixed with the new installation, however there is a bug in Font used as shown below. Can you please advise how I should fix this font issue? Many thanks and Best wishes, My.


/Users/mp21/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/matplotlib/font_manager.py:273: UserWarning: Matplotlib is building the font cache using fc-list. This may take a moment.
  warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.')
2016-01-29 10:37:46.808 Python[9897:d0f] CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
2016-01-29 10:37:46.808 Python[9897:d0f] CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.



-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

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

From pmhobson at gmail.com  Fri Jan 29 11:38:42 2016
From: pmhobson at gmail.com (Paul Hobson)
Date: Fri, 29 Jan 2016 08:38:42 -0800
Subject: [Matplotlib-devel] CTFontLogSuboptimalRequest
In-Reply-To: <D2D10322.10A57%mp21@sanger.ac.uk>
References: <D2D10322.10A57%mp21@sanger.ac.uk>
Message-ID: <CADT3MEBZGKantK07h_ftum5rh2WW5SOnLuSqiJx_9Akn6tE6zg@mail.gmail.com>

The warning is just that -- a warning,  It's not an error and after the
font cache has been built, you shouldn't see it again.

On Fri, Jan 29, 2016 at 3:53 AM, My Phan <mp21 at sanger.ac.uk> wrote:

> Hello,
>
> I have recently re-installed Matplotlib v1.5.1 because of Segmentation
> Fault 11. This seg fault was fixed with the new installation, however there
> is a bug in Font used as shown below. Can you please advise how I should
> fix this font issue? Many thanks and Best wishes, My.
>
>
> /Users/mp21/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/matplotlib/font_manager.py:273:
> UserWarning: Matplotlib is building the font cache using fc-list. This may
> take a moment.
>   warnings.warn('Matplotlib is building the font cache using fc-list. This
> may take a moment.')
> 2016-01-29 10:37:46.808 Python[9897:d0f] CoreText performance note: Client
> called CTFontCreateWithName() using name "Lucida Grande" and got font with
> PostScript name "LucidaGrande". For best performance, only use PostScript
> names when calling this API.
> 2016-01-29 10:37:46.808 Python[9897:d0f] CoreText performance note: Set a
> breakpoint on CTFontLogSuboptimalRequest to debug.
>
> -- The Wellcome Trust Sanger Institute is operated by Genome Research
> Limited, a charity registered in England with number 1021457 and a company
> registered in England with number 2742969, whose registered office is 215
> Euston Road, London, NW1 2BE.
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160129/08b72aac/attachment.html>