From tcaswell at gmail.com  Sat Jul 15 18:26:24 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 15 Jul 2017 22:26:24 +0000
Subject: [Matplotlib-devel] documentation / example review
Message-ID: <CAA48SF-bnFXteNe6RDAxtQKEqHaoU0siHg05O==1HwrKFwDwzg@mail.gmail.com>

Folks,

We have recently been getting a lot of contributions around the prose
documentation and examples (which is great!) however our review process can
be very frustrating, particularly for new contributors.   I propose that we
use the review threshold for documentation and examples of "Is it better
than it was before?".

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

Please remember to be kind and patient with new contributors!

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

From quantum.analyst at gmail.com  Sat Jul 15 18:48:15 2017
From: quantum.analyst at gmail.com (Elliott Sales de Andrade)
Date: Sat, 15 Jul 2017 18:48:15 -0400
Subject: [Matplotlib-devel] documentation / example review
In-Reply-To: <CAA48SF-bnFXteNe6RDAxtQKEqHaoU0siHg05O==1HwrKFwDwzg@mail.gmail.com>
References: <CAA48SF-bnFXteNe6RDAxtQKEqHaoU0siHg05O==1HwrKFwDwzg@mail.gmail.com>
Message-ID: <CAJP_izfjrBU9WJGSeSNOzWMssJ5qZ9BcZYh9636PJ1fHPGMtpA@mail.gmail.com>

Hi all,

In related matters, I think I should point out the possibility of building
docs on Circle CI again [1]. This has two benefits:
a) reduced load on Travis, meaning faster feedback for PRs, and;
b) browseable built docs *before* merging, so if someone makes a change on
GitHub, they can see the actual effect on the website, or the reviewer can
see it before hand, instead of waiting for a devdocs build later/building
locally.

[1] https://github.com/QuLogic/matplotlib/tree/circle-docs

On 15 July 2017 at 18:26, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> We have recently been getting a lot of contributions around the prose
> documentation and examples (which is great!) however our review process can
> be very frustrating, particularly for new contributors.   I propose that we
> use the review threshold for documentation and examples of "Is it better
> than it was before?".
>
> https://github.com/matplotlib/matplotlib/pull/8889
>
> Please remember to be kind and patient with new contributors!
>
> Tom
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


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

From tcaswell at gmail.com  Sat Jul 15 20:54:28 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 16 Jul 2017 00:54:28 +0000
Subject: [Matplotlib-devel] documentation / example review
In-Reply-To: <CAJP_izfjrBU9WJGSeSNOzWMssJ5qZ9BcZYh9636PJ1fHPGMtpA@mail.gmail.com>
References: <CAA48SF-bnFXteNe6RDAxtQKEqHaoU0siHg05O==1HwrKFwDwzg@mail.gmail.com>
 <CAJP_izfjrBU9WJGSeSNOzWMssJ5qZ9BcZYh9636PJ1fHPGMtpA@mail.gmail.com>
Message-ID: <CAA48SF-F3Oz9LknECSXOxTHBybEzs7j8C1Aox75P84Q=HO65TQ@mail.gmail.com>

I think Nelle and Chris Holdgraf will be working on circleci related things
tomorrow.

I have become :+1: on using circle for the docs to get the previews since
the last time we talked about this.

Room

On Sat, Jul 15, 2017 at 5:48 PM Elliott Sales de Andrade <
quantum.analyst at gmail.com> wrote:

> Hi all,
>
> In related matters, I think I should point out the possibility of building
> docs on Circle CI again [1]. This has two benefits:
> a) reduced load on Travis, meaning faster feedback for PRs, and;
> b) browseable built docs *before* merging, so if someone makes a change on
> GitHub, they can see the actual effect on the website, or the reviewer can
> see it before hand, instead of waiting for a devdocs build later/building
> locally.
>
> [1] https://github.com/QuLogic/matplotlib/tree/circle-docs
>
> On 15 July 2017 at 18:26, Thomas Caswell <tcaswell at gmail.com> wrote:
>
>> Folks,
>>
>> We have recently been getting a lot of contributions around the prose
>> documentation and examples (which is great!) however our review process can
>> be very frustrating, particularly for new contributors.   I propose that we
>> use the review threshold for documentation and examples of "Is it better
>> than it was before?".
>>
>> https://github.com/matplotlib/matplotlib/pull/8889
>>
>> Please remember to be kind and patient with new contributors!
>>
>> Tom
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Elliott
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170716/15436137/attachment.html>

From tcaswell at gmail.com  Fri Jul 21 17:00:20 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Fri, 21 Jul 2017 21:00:20 +0000
Subject: [Matplotlib-devel] new committer
Message-ID: <CAA48SF-SP5BgkQXZMUTzJpxdM2Y559rMJoSF8fE0VZHWFBn4vQ@mail.gmail.com>

Folks,

At scipy we gave commit rights to Chris Holdgraf
(@choldgraf).

Welcome to the dev team!

Tom

PS I should be better about sending out announcements when people get
commit rights.  To those of you who got them recently I apologize for being
bad about it in the past.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170721/badde86b/attachment.html>

From story645 at gmail.com  Sun Jul 23 11:36:59 2017
From: story645 at gmail.com (Hannah)
Date: Sun, 23 Jul 2017 11:36:59 -0400
Subject: [Matplotlib-devel] new committer
In-Reply-To: <CAA48SF-SP5BgkQXZMUTzJpxdM2Y559rMJoSF8fE0VZHWFBn4vQ@mail.gmail.com>
References: <CAA48SF-SP5BgkQXZMUTzJpxdM2Y559rMJoSF8fE0VZHWFBn4vQ@mail.gmail.com>
Message-ID: <CAOuQ7j3as3ygttLGiHjNRHPQbzUiuMyw06FdJ2CzFDtqfZEhAQ@mail.gmail.com>

Yay! *Happy dance*

On Fri, Jul 21, 2017 at 5:00 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> At scipy we gave commit rights to Chris Holdgraf
> (@choldgraf).
>
> Welcome to the dev team!
>
> Tom
>
> PS I should be better about sending out announcements when people get
> commit rights.  To those of you who got them recently I apologize for being
> bad about it in the past.
>
> _______________________________________________
> 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/20170723/94d0b74f/attachment.html>

From tcaswell at gmail.com  Sat Jul 29 20:44:55 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 30 Jul 2017 00:44:55 +0000
Subject: [Matplotlib-devel] 2017-07-25 notes
Message-ID: <CAA48SF-GwUJJ+6tfUEk9tKKoyB7NCof95U9-np88Z2ievm15OA@mail.gmail.com>

Folks,

My self, anntzer and efiring.

We discussed a plans for 2.1 (another email is coming), details of several
PRs, and anntzer's recent work on implementing qt5cairo.

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

From tcaswell at gmail.com  Sat Jul 29 21:31:07 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 30 Jul 2017 01:31:07 +0000
Subject: [Matplotlib-devel] Matplotlib 2.1 plans
Message-ID: <CAA48SF_r3LOzAUC89kur9yBGzKzU-iYRYbXa3RP_UwUC02HdEg@mail.gmail.com>

Folks,

This is a follow up to this weeks phone call notes (but with a better
subject line).

We currently have about 2 years worth of new feature development on the
master branch waiting to be released!  We need to get 2.1 tagged and out
the door which means we need to triage what will go in the release.  The
goal is an RC by the end of August [1].

One of the hard decisions is to delay the MEP 22/27 work to the next
release [2].

There are currently 651 issues and PRs tagged as 2.1 (and 162 as 2.0.3) so
obviously not all of them are going to be fixed / merged for 2.1.  To that
end, the current blockers for the release are tagged 'release critical'
https://github.com/matplotlib/matplotlib/labels/Release%20critical and I am
going to:

 - rename the 2.0.3 milestone to 2.1.1
 - start moving things from the 2.1 -> 2.2 milestones

Until we tag the RC anything is still fair game to be merged.  If you know
of any issues that you think are blockers please label them as such (or
leave a comment).


Tom

[1] This is driven because I will be off the internet for the first 2 weeks
of Sept and very busy with day-job the last two weeks of Sept so missing
this deadline means pushing the release back at least another month.
[2] Despite my best intentions, I have not been able to devote enough time
to review this, sorry oceanwolf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170730/18ace8db/attachment.html>

From tcaswell at gmail.com  Sat Jul 29 23:20:59 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 30 Jul 2017 03:20:59 +0000
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
Message-ID: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>

Folks,

With 2.0 we picked up subprocess32 (
https://pypi.python.org/pypi/subprocess32/) to be able to use the improved
subprocess module, however this has caused several problem with [1, 2] due
to a bug in the release version and wheels not being published on pypi.
The bug is reportedly fixed on master [4] and Mathew Brett has provided
them with wheel-building machinery [3], but there has been no motion on
that sense May.

I think our options are:

 - document the known issues (meaning wheel-installing mac users have to
install xcode and people on very old linux need to install from the
subprocess32 master branch, and general linux users need to have a gcc
installed)
 - hope subprocess32 does a release and adopt Matthew's wheels in the next
month
 - vendor the master branch (is there a way we can do this _just_ for the
wheels without actually vendoring it in the source tree?)
 - change dependencies

After 2.1 we won't have the last option until 2.2 so if we want to do that,
it needs to be done this month.

If anyone is motivated to work on changing the dependency, please do so
otherwise I am inclined to go with the first option.

Tom


[1] https://github.com/matplotlib/matplotlib/issues/8361
[2] https://github.com/matplotlib/matplotlib/issues/8433
[3] https://github.com/google/python-subprocess32/issues/14
[4] https://github.com/google/python-subprocess32/issues/12
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170730/adc804f9/attachment.html>

From ben.v.root at gmail.com  Mon Jul 31 11:20:16 2017
From: ben.v.root at gmail.com (Benjamin Root)
Date: Mon, 31 Jul 2017 11:20:16 -0400
Subject: [Matplotlib-devel] Matplotlib 2.1 plans
In-Reply-To: <CAA48SF_r3LOzAUC89kur9yBGzKzU-iYRYbXa3RP_UwUC02HdEg@mail.gmail.com>
References: <CAA48SF_r3LOzAUC89kur9yBGzKzU-iYRYbXa3RP_UwUC02HdEg@mail.gmail.com>
Message-ID: <CANNq6FnQ6tnaDsrXOcg2x0Mc4n_X2Y2cVX-1tRvB=mZ0B3e5Ng@mail.gmail.com>

Do we want to fix the prop-cycling issues/fill_between/bar issues I
discovered during SciPy, or might that be too invasive this close to
cutting the rc?

On Sat, Jul 29, 2017 at 9:31 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> This is a follow up to this weeks phone call notes (but with a better
> subject line).
>
> We currently have about 2 years worth of new feature development on the
> master branch waiting to be released!  We need to get 2.1 tagged and out
> the door which means we need to triage what will go in the release.  The
> goal is an RC by the end of August [1].
>
> One of the hard decisions is to delay the MEP 22/27 work to the next
> release [2].
>
> There are currently 651 issues and PRs tagged as 2.1 (and 162 as 2.0.3) so
> obviously not all of them are going to be fixed / merged for 2.1.  To that
> end, the current blockers for the release are tagged 'release critical'
> https://github.com/matplotlib/matplotlib/labels/Release%20critical and I
> am going to:
>
>  - rename the 2.0.3 milestone to 2.1.1
>  - start moving things from the 2.1 -> 2.2 milestones
>
> Until we tag the RC anything is still fair game to be merged.  If you know
> of any issues that you think are blockers please label them as such (or
> leave a comment).
>
>
> Tom
>
> [1] This is driven because I will be off the internet for the first 2
> weeks of Sept and very busy with day-job the last two weeks of Sept so
> missing this deadline means pushing the release back at least another month.
> [2] Despite my best intentions, I have not been able to devote enough time
> to review this, sorry oceanwolf
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170731/4379a361/attachment.html>

From aaq219 at nyu.edu  Mon Jul 17 02:27:15 2017
From: aaq219 at nyu.edu (Ahlam Al Qasim)
Date: Mon, 17 Jul 2017 06:27:15 -0000
Subject: [Matplotlib-devel] GEOS installation for Basemap package
Message-ID: <CAOe_Q4JOCYfhrntU8dM1Eia_y1u3+CRgQ+v2N+YzsmOACtaiKg@mail.gmail.com>

To whom it may concern,

I hope this email finds you well. I am trying to get the Basemap package on
my mac, and have been following the instructions based on this webpage:
https://matplotlib.org/basemap/users/installing.html. I don't have GEOS
already installed so I tried following steps on the website to download it
with Basemap:

cd geos-3.3.3
export GEOS_DIR=<where you want the libs and headers to go>
# A reasonable choice on a Unix-like system is /usr/local, or
# if you don't have permission to write there, your home directory.
./configure --prefix=$GEOS_DIR
make; make install


However, I am getting errors at the third step (make; make install).
Attached is a copy of what I get on my python console, if it helps. I think
the error occurs when trying to create the /include directory, but I'm not
sure how to fix it. I'm still new to python so any help would be much
appreciated!

Best regards,
Ahlam Al Qasim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170717/f3c32a94/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python console.rtf
Type: application/rtf
Size: 7188 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170717/f3c32a94/attachment-0001.rtf>

From st970703 at gmail.com  Sun Jul 23 20:42:51 2017
From: st970703 at gmail.com (Mike Lee)
Date: Mon, 24 Jul 2017 12:42:51 +1200
Subject: [Matplotlib-devel] IndexError: invalid index to scalar
 variable. in /matplotlib/ticker.py
Message-ID: <CAOvhWJynM9w8Rs1HHu_DpnGs8HwUJH-bN-2U3fv_0pE5kV2JqQ@mail.gmail.com>

Dear Sir or Madam,

I recently posted a bug report on the GitHub discussion page.
https://github.com/matplotlib/matplotlib/issues/8881

I am recently working on updating auto07p to work with matplotlib 2.0.
auto07p is software written for ordinary differential equations.
I encountered the 'IndexError: invalid index to scalar variable.' in
'/matplotlib/ticker.py'

It appeared that the
istep = np.nonzero(steps >= raw_step)[0][0]
was trying to access a 1D array without checking its array dimension.

I replaced the line in ticker.py:
istep = np.nonzero(steps >= raw_step)[0][0]

With the following:
arr_dim = np.nonzero(steps >= raw_step).ndim
if arr_dim == 1:

istep = np.nonzero(steps >= raw_step)[0]

elif arr_dim == 2:

istep = np.nonzero(steps >= raw_step)[0][0]

It worked after the above changes. However, I am not absolutely sure
correctness of this fix.


May I suggest the developers look further into this issue and resolve this
in the future release?




Kind regards,


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

From keith.briggs at bt.com  Mon Jul 31 07:06:53 2017
From: keith.briggs at bt.com (keith.briggs at bt.com)
Date: Mon, 31 Jul 2017 11:06:53 +0000
Subject: [Matplotlib-devel] documentation error at
 https://matplotlib.org/api/colorbar_api.html
In-Reply-To: <1501497630701.69273@bt.com>
References: <1501497630701.69273@bt.com>
Message-ID: <1501499266564.59447@bt.com>

"shrink 1.0; fraction by which to shrink the colorbar"


should be something like


"shrink 1.0; fraction by which to scale the size size of the colorbar"


since the original wording implies that a bigger shrink causes a smaller size.



Keith



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