From pi at berkeley.edu  Wed Jul  3 18:19:26 2019
From: pi at berkeley.edu (Paul Ivanov)
Date: Wed, 3 Jul 2019 15:19:26 -0700
Subject: [Matplotlib-devel] REL: Matplotlib 3.1.1
Message-ID: <CAKCGbV4f+ho46ETX3q=jwH5VW4XYXdCboKk2bwxbUWXLwAb6bg@mail.gmail.com>

Hi everyone,

We are happy to announce the release of Matplotlib 3.1.1!

Matplotlib 3.1.1 supports Python 3.6+.

This is mostly a bug-fix release, with one API change involving
Locator.nonsingular return order.
Locator.nonsingular (introduced in matplotlib 3.1.0) now returns a range
v0, v1 with v0 <= v1. This behavior is consistent with the implementation
of nonsingular by the LogLocator and LogitLocator subclasses.

Thanks to everyone who contributed to this release, including 29 folks and
one robot who worked together to get 120 pull requests in [1], as well as
all the amazing users who reported and raised the issues in the first place.

Also a personal thank you to the matplotlib developers who were patient
with me making my first solo release. I promise I'll be faster the next go
around. :)

best,
pi

1. https://matplotlib.org/users/github_stats.html
-- 
                   _
                  / \
                A*   \^   -
             ,./   _.`\\ / \
            / ,--.S    \/   \
           /  `"~,_     \    \
     __o           ?
   _ \<,_         /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
https://pirsquared.org <http://pirsquared.org> | GPG/PGP key id: 0x0F3E28F7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190703/8e23cb67/attachment.html>

From swfiua at gmail.com  Mon Jul  8 18:59:27 2019
From: swfiua at gmail.com (swfiua at gmail.com)
Date: Mon, 8 Jul 2019 18:59:27 -0400
Subject: [Matplotlib-devel] Table and blume
Message-ID: <CAO4m3cL7ESZKw=v1MV-5tc71yCgEnEvRL4GNb-PaEx028giQJQ@mail.gmail.com>

Hi,

I just wanted to give an update on where I am with the table code.

I've been away from the code much of the last month.

I've started a project https://github.com/swfiua/blume  which has my
preferred version of the table code.

It's got basic instructions on how to use and then a bunch of questions of
where to go from here.   The docs folder has some history.

I'm at the point now where I think you have better behaviour for most of
the known issues, but with some potential impact on users.

Those that just use the table function and don't probe into the insides
will likely only notice more legible tables.

It would be good to think about the end goal here, as that has some bearing
on how blume should proceed.

I've not got too much further forward beyond a bunch of thinking on what
belongs where and how to get there.   And also I've been spending some time
in my karma pi project looking for other pieces that are in the wrong
place.

Primarily, it would be good to give everyone access to a better table, just
a question of how to get there and are there any precedents for splitting
stuff into side projects?

Once we have a plan I'll tidy up the issues on github accordingly and work
to move the plan along.

Johnny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190708/814425dd/attachment.html>

From tcaswell at gmail.com  Wed Jul 10 02:34:57 2019
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 10 Jul 2019 02:34:57 -0400
Subject: [Matplotlib-devel] Using towncrier to generate changelogs
In-Reply-To: <CAGm9cHDpBwL6kO0Nm7N1x0i+LBp+YC+h+WfKf9-Sq6cm6RyowA@mail.gmail.com>
References: <CAGm9cHDpBwL6kO0Nm7N1x0i+LBp+YC+h+WfKf9-Sq6cm6RyowA@mail.gmail.com>
Message-ID: <CAA48SF9K7GR_owVz8wxjcWrrAjLtbVU=QQkATDKjeBwwYOt14A@mail.gmail.com>

I think this is a great idea, however I am a bit concerned about "should
contain a single sentence or paragraph describing the change".  Does this
mean we can not include plot directives it the what_new?

Tom

On Tue, Jun 25, 2019 at 1:45 PM David Stansby <dstansby at gmail.com> wrote:

> Dear all,
>
> I am proposing to change up how Matplotlib's API changes/what's new pages
> are generated, in particular moving to using towncrier
> <https://github.com/hawkowl/towncrier> to add more automation to the
> process. This is motivated by the crazy amount of time it took me to
> combine all the API change and what's new fragments into a coherent page
> for the 3.1.0 release.
>
> The PR to change this process is here:
> https://github.com/matplotlib/matplotlib/pull/14589 The new process would
> be
>
>    - When a new feature or api change or code removal is implemented, add
>    a changelog file to the *changelog/* folder
>    - The changelog file should be named <PR number>.<type>.rst, and
>    should contain a single sentence or paragraph describing the change. <type>
>    is the type of change, ie. api_change, new_feature or removal
>    - towncrier can then automatically collate these fragments into a
>    single .rst page, which can be manually edited if needed before releasing
>
> I think this will significnatly reduce the burden of producing what's new
> pages each release, without adding any extra burden on those writing the
> what's new entries.
>
> Please take a look at the PR and leave comments/questions/suggestions! In
> particular, feedback on what "types" of changelog entry to include would be
> very welcome.
>
> All the best,
> David
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>


-- 
Thomas Caswell
tcaswell at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190710/6f100b78/attachment.html>

From dstansby at gmail.com  Mon Jul 15 12:45:14 2019
From: dstansby at gmail.com (David Stansby)
Date: Mon, 15 Jul 2019 17:45:14 +0100
Subject: [Matplotlib-devel] Using towncrier to generate changelogs
In-Reply-To: <CAA48SF9K7GR_owVz8wxjcWrrAjLtbVU=QQkATDKjeBwwYOt14A@mail.gmail.com>
References: <CAGm9cHDpBwL6kO0Nm7N1x0i+LBp+YC+h+WfKf9-Sq6cm6RyowA@mail.gmail.com>
 <CAA48SF9K7GR_owVz8wxjcWrrAjLtbVU=QQkATDKjeBwwYOt14A@mail.gmail.com>
Message-ID: <CAGm9cHA8TiCE9=8-x_agxY2DXHsQQJZtKs-jCAVrMV+kPgjboQ@mail.gmail.com>

I don't think this should be an issue - towncrier just reflows .rst
fragments in individual files into a complete list when it's run. Worst
case, it is possible to edit the final changelog file that is generated
before pushing it.

Thinking about this a bit, maybe it would be better anyway (from a
maintainability and discoverability point of view) to have examples showing
off new features get a new examples gallery entry instead of a plot
directive snippet on the what's new page.

David

On Wed, 10 Jul 2019 at 07:35, Thomas Caswell <tcaswell at gmail.com> wrote:

> I think this is a great idea, however I am a bit concerned about "should
> contain a single sentence or paragraph describing the change".  Does this
> mean we can not include plot directives it the what_new?
>
> Tom
>
> On Tue, Jun 25, 2019 at 1:45 PM David Stansby <dstansby at gmail.com> wrote:
>
>> Dear all,
>>
>> I am proposing to change up how Matplotlib's API changes/what's new pages
>> are generated, in particular moving to using towncrier
>> <https://github.com/hawkowl/towncrier> to add more automation to the
>> process. This is motivated by the crazy amount of time it took me to
>> combine all the API change and what's new fragments into a coherent page
>> for the 3.1.0 release.
>>
>> The PR to change this process is here:
>> https://github.com/matplotlib/matplotlib/pull/14589 The new process
>> would be
>>
>>    - When a new feature or api change or code removal is implemented,
>>    add a changelog file to the *changelog/* folder
>>    - The changelog file should be named <PR number>.<type>.rst, and
>>    should contain a single sentence or paragraph describing the change. <type>
>>    is the type of change, ie. api_change, new_feature or removal
>>    - towncrier can then automatically collate these fragments into a
>>    single .rst page, which can be manually edited if needed before releasing
>>
>> I think this will significnatly reduce the burden of producing what's new
>> pages each release, without adding any extra burden on those writing the
>> what's new entries.
>>
>> Please take a look at the PR and leave comments/questions/suggestions! In
>> particular, feedback on what "types" of changelog entry to include would be
>> very welcome.
>>
>> All the best,
>> David
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>
>
> --
> Thomas Caswell
> tcaswell at gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190715/1e94549d/attachment.html>

From tcaswell at gmail.com  Mon Jul 15 23:12:22 2019
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 15 Jul 2019 23:12:22 -0400
Subject: [Matplotlib-devel] triage rights for all contributors
Message-ID: <CAA48SF-9DbyW5Qd0f_qWPRr6S05RbM0gBxWi0nM-1ctwBhbfVQ@mail.gmail.com>

Folks,

Discussed on todays call, github has added some additional access levels to
orgs (see
https://help.github.com/en/articles/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization
and
we are proposing giving triage rights to people when they have their first
PR merged.

I have created a new team "Contributors" and given it triage power of
Matplotlib (https://github.com/orgs/matplotlib/teams/contributors).  If
there are no protests, I will write a script to invite anyone who has a
merged PR in the last 12 months and add them to that team.

Tom
-- 
Thomas Caswell
tcaswell at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190715/5257cea4/attachment.html>

From rmay31 at gmail.com  Tue Jul 16 13:57:11 2019
From: rmay31 at gmail.com (Ryan May)
Date: Tue, 16 Jul 2019 10:57:11 -0700
Subject: [Matplotlib-devel] triage rights for all contributors
In-Reply-To: <CAA48SF-9DbyW5Qd0f_qWPRr6S05RbM0gBxWi0nM-1ctwBhbfVQ@mail.gmail.com>
References: <CAA48SF-9DbyW5Qd0f_qWPRr6S05RbM0gBxWi0nM-1ctwBhbfVQ@mail.gmail.com>
Message-ID: <CAKH0P+VCpGPDs0dFo4jAet=teTekSwzH1F14eE7-6WvF8uK0Eg@mail.gmail.com>

That seems generally reasonable to me.

Ryan

On Mon, Jul 15, 2019 at 8:12 PM Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> Discussed on todays call, github has added some additional access levels
> to orgs (see
>
> https://help.github.com/en/articles/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization and
> we are proposing giving triage rights to people when they have their first
> PR merged.
>
> I have created a new team "Contributors" and given it triage power of
> Matplotlib (https://github.com/orgs/matplotlib/teams/contributors).  If
> there are no protests, I will write a script to invite anyone who has a
> merged PR in the last 12 months and add them to that team.
>
> Tom
> --
> Thomas Caswell
> tcaswell at gmail.com
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>


-- 
Ryan May
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20190716/1aa1b089/attachment.html>