From tcaswell at gmail.com  Wed Jan  4 21:58:45 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 05 Jan 2017 02:58:45 +0000
Subject: [Matplotlib-devel] Confusion about draw_artist
In-Reply-To: <CAH6Pt5pNcbAHONKuvDs6gwcLFhdnwoXtiDq-wNsNRPMO373faA@mail.gmail.com>
References: <CAH6Pt5pNcbAHONKuvDs6gwcLFhdnwoXtiDq-wNsNRPMO373faA@mail.gmail.com>
Message-ID: <CAA48SF_RCrwUm8LBj0JNYdM+q28TJXkBnzaZaYs-b-c5V4_i6w@mail.gmail.com>

Unless you have flagged the artist as `animated` (via `set_animated` or by
kwarg), it will be drawn as part of the next re-draw.  You are better off
just changing the `fig.canvas.draw()` to `fig.canvas.draw_idle()` and
letting the GUI decide when to re-draw things.

If you want to get any performance gain from animated artists + draw_artist
you will need to use blitting (which will work with the OSX backend in 2.0).

Tom

On Wed, Nov 30, 2016 at 2:11 PM Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> We're using 'draw_artist' in an image viewer, and I just found that
> our viewer is crashing using the macosx backend.  Here's a minimal
> example:
>
> import matplotlib
> matplotlib.use('macosx')
> import matplotlib.pyplot as plt
>
> fig, ax = plt.subplots(1, 1)
> im = plt.imshow([[1, 2], [3, 4]])
> fig.canvas.draw()
> ax.draw_artist(im)
>
> This generates:
>
> Traceback (most recent call last):
>   File "draw_artist.py", line 8, in <module>
>     ax.draw_artist(im)
>   File "/Users/mb312/dev_trees/matplotlib/lib/matplotlib/axes/_base.py",
> line 2423, in draw_artist
>     raise AttributeError(msg)
> AttributeError: draw_artist can only be used after an initial draw
> which caches the render
>
> for the macosx backend, and works correctly for the tkagg backend.
>
> I can't see any way to cache the renderer here - could someone give me
> a pointer?
>
> Cheers,
>
> Matthew
> _______________________________________________
> 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/20170105/c1202187/attachment.html>

From tcaswell at gmail.com  Wed Jan  4 22:00:01 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 05 Jan 2017 03:00:01 +0000
Subject: [Matplotlib-devel] matplotlib versus Matplotlib?
In-Reply-To: <CAH6Pt5rMJZf+9obfUVeG5eXL-GJ83j65oep9D_cBxdq_CQD8DA@mail.gmail.com>
References: <CAE-UAvTLk1-u=RmH5GqhLwsBH9K0xXaOkLSLJaJnwgsdr8AaLA@mail.gmail.com>
 <CAH6Pt5rMJZf+9obfUVeG5eXL-GJ83j65oep9D_cBxdq_CQD8DA@mail.gmail.com>
Message-ID: <CAA48SF8_8snV5L5dvSVmWj+St10vmpz2Oxy8_=tuEwzd4=ncuA@mail.gmail.com>

Due to some off-line discussions, the consensus seems to be on Matplotlib
in text.

Tom

On Thu, Nov 3, 2016 at 3:34 AM Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> On Wed, Nov 2, 2016 at 9:02 PM, Nelle Varoquaux
> <nelle.varoquaux at gmail.com> wrote:
> > Hi everyone,
> >
> > important question of the day? Is it matplotlib or Matplotlib?
> > I remember having this discussion with Mike at scipy 2013 and I sort
> > of recall that matplotlib was the correct capitalization.
> > I personally much prefer Matplotlib, but either way, we should make a
> > decision and stick to it.
> >
> > The 2005 paper (http://adsabs.harvard.edu/full/2005ASPC..347...91B)
> > seems to point with lower case matplotlib.
>
> I believe standard grammatical rules would suggest Matplotlib, as it's
> a proper noun.
>
> Best,
>
> Matthew
> _______________________________________________
> 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/20170105/a9571569/attachment.html>

From morph at debian.org  Fri Jan  6 19:07:57 2017
From: morph at debian.org (Sandro Tosi)
Date: Fri, 6 Jan 2017 19:07:57 -0500
Subject: [Matplotlib-devel] v2.0.0rc1 is tagged
In-Reply-To: <CAA48SF9-VXyNu8JtyttEv3NnqK7i_2VVEnoN1Z6XHk0=uVM+DA@mail.gmail.com>
References: <CAA48SF9hMRjBCx-kg_ZzPWyqX9+N4L3oaHsq8O+2wPTUYcOoiA@mail.gmail.com>
 <CAB4XWXyV=A9rMqC5ZQ5d3JAyc1pyXz3Cov4NunZs0Mdg=xddcg@mail.gmail.com>
 <CAA48SF9-VXyNu8JtyttEv3NnqK7i_2VVEnoN1Z6XHk0=uVM+DA@mail.gmail.com>
Message-ID: <CAB4XWXzH3JxuMQLkQ6283EPWX6HMHpM2O-_dg3=SUQjS+mZqnw@mail.gmail.com>

Hey there!

On Mon, Dec 12, 2016 at 8:37 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> The goal is late December / early January, but we have not been great about
> hitting those recently.

gentle ping to check the status of the final release - do you think we
are still in a good position to release in early/mid Jan? thanks!

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

From akkana at shallowsky.com  Sat Jan  7 14:09:33 2017
From: akkana at shallowsky.com (Akkana Peck)
Date: Sat, 7 Jan 2017 12:09:33 -0700
Subject: [Matplotlib-devel] mpl_finance maintenance
Message-ID: <20170107190933.xobzcwmajdjpsx75@shallowsky.com>

Hi, I'm new here (waves).

I occasionally use matplotlib.finance (primarily for the historical
quotes functions) and discovered that it's deprecated in matplotlib
2.0and has been split off into a separate module,
https://github.com/matplotlib/mpl_finance
whose README says that it's basically unmaintained, and to help, get
in touch on matplotlib-users. Since I use it and would like to see
it continue to be available, I'm willing to help maintain it.

A helpful person on #matplotlib suggested that matplotlib-devel was
probably a better place than -users, so here I am. I am not by any
means a finance expert, but most of mpl_finance is basic functions
like fetching historical quotes and plotting them.

Anyway, if the current contributors want help maintaining mpl_finance,
I'm akkana on GitHub, or send me email. Or let me know if I should
re-post to matplotlib-users like the README said.

And thanks for all the ongoing work in maintaining matplotlib!

        ...Akkana

From efiring at hawaii.edu  Sat Jan  7 15:18:29 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Sat, 7 Jan 2017 10:18:29 -1000
Subject: [Matplotlib-devel] mpl_finance maintenance
In-Reply-To: <20170107190933.xobzcwmajdjpsx75@shallowsky.com>
References: <20170107190933.xobzcwmajdjpsx75@shallowsky.com>
Message-ID: <b27cfafd-fa01-bdcc-8f7e-39c697830487@hawaii.edu>

Akkana,

Yes! Welcome!  (And this is the right mailing list.) Tom Caswell will 
know what to do to provide appropriate access and advice, but in the 
meantime I want to thank you for volunteering.  I think that financial 
applications can be important for Matplotlib.  Indeed, the original 
author of Matplotlib, John D. Hunter, worked in the finance industry 
after his academic training in neuroscience.

See https://github.com/matplotlib/matplotlib/pull/7762; I think it needs 
more specific information for the user on where mpl_finance *is*.

A PyPi release is also needed.

I don't know what the status is with respect to any bugs in the package 
as it stands now.

A question that just popped into my head is, does it make sense in the 
long run for mpl_finance to build on pandas, which is designed to handle 
the types of data encountered in finance?

Eric

On 2017/01/07 9:09 AM, Akkana Peck wrote:
> Hi, I'm new here (waves).
>
> I occasionally use matplotlib.finance (primarily for the historical
> quotes functions) and discovered that it's deprecated in matplotlib
> 2.0and has been split off into a separate module,
> https://github.com/matplotlib/mpl_finance
> whose README says that it's basically unmaintained, and to help, get
> in touch on matplotlib-users. Since I use it and would like to see
> it continue to be available, I'm willing to help maintain it.
>
> A helpful person on #matplotlib suggested that matplotlib-devel was
> probably a better place than -users, so here I am. I am not by any
> means a finance expert, but most of mpl_finance is basic functions
> like fetching historical quotes and plotting them.
>
> Anyway, if the current contributors want help maintaining mpl_finance,
> I'm akkana on GitHub, or send me email. Or let me know if I should
> re-post to matplotlib-users like the README said.
>
> And thanks for all the ongoing work in maintaining matplotlib!
>
>         ...Akkana
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>


From tcaswell at gmail.com  Sat Jan  7 15:28:57 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 07 Jan 2017 20:28:57 +0000
Subject: [Matplotlib-devel] mpl_finance maintenance
In-Reply-To: <20170107190933.xobzcwmajdjpsx75@shallowsky.com>
References: <20170107190933.xobzcwmajdjpsx75@shallowsky.com>
Message-ID: <CAA48SF_Ytt0prKanVcRD+W1abr94-bA+5rSvr_4UNkDzOskKJQ@mail.gmail.com>

Great!

I think mpl-finance being explicitly pandas aware would be a reasonable
thing to do (and the ability to do that is one of the selling points of
spinning the mpl-* projects out of core mpl), but will make importing the
functions back a bit tricky.

Akkana: you should have an invitation to join the mpl org with push right
to mpl_finance.  In addition to doing a release on pypi I think the first
critical task is to get sphinx docs for the project set up and hosted.
Even though you have push rights, please go through the standard PR review
process.

Tom

On Sat, Jan 7, 2017 at 2:18 PM Akkana Peck <akkana at shallowsky.com> wrote:

> Hi, I'm new here (waves).
>
> I occasionally use matplotlib.finance (primarily for the historical
> quotes functions) and discovered that it's deprecated in matplotlib
> 2.0and has been split off into a separate module,
> https://github.com/matplotlib/mpl_finance
> whose README says that it's basically unmaintained, and to help, get
> in touch on matplotlib-users. Since I use it and would like to see
> it continue to be available, I'm willing to help maintain it.
>
> A helpful person on #matplotlib suggested that matplotlib-devel was
> probably a better place than -users, so here I am. I am not by any
> means a finance expert, but most of mpl_finance is basic functions
> like fetching historical quotes and plotting them.
>
> Anyway, if the current contributors want help maintaining mpl_finance,
> I'm akkana on GitHub, or send me email. Or let me know if I should
> re-post to matplotlib-users like the README said.
>
> And thanks for all the ongoing work in maintaining matplotlib!
>
>         ...Akkana
> _______________________________________________
> 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/20170107/b713ab7b/attachment.html>

From akkana at shallowsky.com  Sat Jan  7 16:33:21 2017
From: akkana at shallowsky.com (Akkana Peck)
Date: Sat, 7 Jan 2017 14:33:21 -0700
Subject: [Matplotlib-devel] mpl_finance maintenance
In-Reply-To: <CAA48SF_Ytt0prKanVcRD+W1abr94-bA+5rSvr_4UNkDzOskKJQ@mail.gmail.com>
 <b27cfafd-fa01-bdcc-8f7e-39c697830487@hawaii.edu>
Message-ID: <20170107213320.zgrsas7kducbjikk@shallowsky.com>

Eric Firing writes:
> See https://github.com/matplotlib/matplotlib/pull/7762; I think it needs
> more specific information for the user on where mpl_finance *is*.

Right now, I agree; it could use a pointer to the GitHub repository.
But if we put it on PyPI that becomes a lot less important.

Who should be the owner on PyPI? It's easy enough to submit it since
it already has a working setup.py, though the README/documentation
needs to be better (I can work on that). Should it be owned on PyPI
by the matplotlib project?

When I built mpl_finance from setup.py and pip installed it (--user),
pip pulled in version 1.5.3 of matplotlib rather than using my
system-installed matplotlib 2.0.0rc2, and nothing worked. I had to
comment out the install_requires line in setup.py. Once matplotlib
2.0 is the default on PyPI that won't be an issue, but it might be now.

> A question that just popped into my head is, does it make sense in the long
> run for mpl_finance to build on pandas, which is designed to handle the
> types of data encountered in finance?

It would be great to work with pandas if we add better stats
routines, things that could compete with R's finance packages.

It should still be able to run without pandas if all the user wants
is simple fetches and plots like it does now.

Thomas Caswell writes:
> Akkana: you should have an invitation to join the mpl org with push right
> to mpl_finance.  In addition to doing a release on pypi I think the first
> critical task is to get sphinx docs for the project set up and hosted.
> Even though you have push rights, please go through the standard PR review
> process.

Great! I'll start on sphinx docs first and submit a pull request
when I have something ready. I'm somewhat new to both pull requests
and sphinx, so I'll apologize in advance if my first submissions
need a little help. I'll try to use matplotlib as a model for where
to put the sphinx files, what theme to use, etc.

        ...Akkana

From tcaswell at gmail.com  Sat Jan  7 17:05:58 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 07 Jan 2017 22:05:58 +0000
Subject: [Matplotlib-devel] mpl_finance maintenance
In-Reply-To: <20170107213320.zgrsas7kducbjikk@shallowsky.com>
References: <CAA48SF_Ytt0prKanVcRD+W1abr94-bA+5rSvr_4UNkDzOskKJQ@mail.gmail.com>
 <b27cfafd-fa01-bdcc-8f7e-39c697830487@hawaii.edu>
 <20170107213320.zgrsas7kducbjikk@shallowsky.com>
Message-ID: <CAA48SF_H53205FA=0wTgCi4LnsA1gF+f7CevzpUi0iQDZN9bPA@mail.gmail.com>

Can you add me as an additional owner on pypi (Thomas.Caswell is my
username there)?

https://github.com/matplotlib/cycler is a better model to follow for the
docs (it is much simpler).  See
http://www.sphinx-doc.org/en/1.5.1/tutorial.html for how to get started
with sphinx (which is iirc what I did for cycler).

See http://matplotlib.org/2.0.0rc2/devel/gitwash/development_workflow.html for
git / PR details.

Tom

On Sat, Jan 7, 2017 at 4:33 PM Akkana Peck <akkana at shallowsky.com> wrote:

> Eric Firing writes:
> > See https://github.com/matplotlib/matplotlib/pull/7762; I think it needs
> > more specific information for the user on where mpl_finance *is*.
>
> Right now, I agree; it could use a pointer to the GitHub repository.
> But if we put it on PyPI that becomes a lot less important.
>
> Who should be the owner on PyPI? It's easy enough to submit it since
> it already has a working setup.py, though the README/documentation
> needs to be better (I can work on that). Should it be owned on PyPI
> by the matplotlib project?
>
> When I built mpl_finance from setup.py and pip installed it (--user),
> pip pulled in version 1.5.3 of matplotlib rather than using my
> system-installed matplotlib 2.0.0rc2, and nothing worked. I had to
> comment out the install_requires line in setup.py. Once matplotlib
> 2.0 is the default on PyPI that won't be an issue, but it might be now.
>
> > A question that just popped into my head is, does it make sense in the
> long
> > run for mpl_finance to build on pandas, which is designed to handle the
> > types of data encountered in finance?
>
> It would be great to work with pandas if we add better stats
> routines, things that could compete with R's finance packages.
>
> It should still be able to run without pandas if all the user wants
> is simple fetches and plots like it does now.
>
> Thomas Caswell writes:
> > Akkana: you should have an invitation to join the mpl org with push right
> > to mpl_finance.  In addition to doing a release on pypi I think the first
> > critical task is to get sphinx docs for the project set up and hosted.
> > Even though you have push rights, please go through the standard PR
> review
> > process.
>
> Great! I'll start on sphinx docs first and submit a pull request
> when I have something ready. I'm somewhat new to both pull requests
> and sphinx, so I'll apologize in advance if my first submissions
> need a little help. I'll try to use matplotlib as a model for where
> to put the sphinx files, what theme to use, etc.
>
>         ...Akkana
> _______________________________________________
> 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/20170107/e94b5524/attachment-0001.html>

From tcaswell at gmail.com  Tue Jan 10 00:19:39 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 10 Jan 2017 05:19:39 +0000
Subject: [Matplotlib-devel] tests+baseline images no longer installed by
 default
Message-ID: <CAA48SF_DSUBw8Z3Oi8KzuBQgfyJNT1nWQuNLvkmfo3hY5P2syQ@mail.gmail.com>

Folks (particularly down-stream packagers),

As of https://github.com/matplotlib/matplotlib/pull/7757 (which is
currently on master and I am in the process of backporting for 2.0) the
test images are not installed by default.  We already are stripping the
test images from the official wheels and conda-forge packages.  This change
greatly reduces the resultant file size :


23:41 $ python setup.py sdist bdist_wheel
23:41 $ du -hs dist/*
11M     dist/matplotlib-2.0.0rc2+60.ge83e108ef-cp36-cp36m-linux_x86_64.whl
51M     dist/matplotlib-2.0.0rc2+60.ge83e108ef.tar.gz


To restore installing the tests and images have a `setup.cfg` with

[packages]
tests = True
toolkit_tests = True

in the source directory at build / install time.

A consequence of this change is that by default `pip install ./` or
`setup.py install` will not install the tests (and hence `python
run_tests.py` will not work).  We suggest using `pip install -v -e ./` or
using a `setup.cfg` file.

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

From tcaswell at gmail.com  Tue Jan 10 00:53:57 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 10 Jan 2017 05:53:57 +0000
Subject: [Matplotlib-devel] v2.0 home stretch
Message-ID: <CAA48SF_wWogOVaKs3ENg4wDoF+S7=n_+S6hgHQKiuYTP8snLhQ@mail.gmail.com>

Folks,

We are getting very close to the end :)

https://github.com/matplotlib/matplotlib/milestone/14

The tableau color namespace needs to be merged.  I think 'tc' is the best
of the options that were proposed (the full name is too long and too hard
to spell).

There are 3 PR/issue pairs that I think are ready for final review (7779 /
7745 , 7780 / 7746, 7740 / 7704).

One path issue that we are having trouble reproducing (7715).  Can someone
who uses a non-english locale by default take a look at that one?  This
might be a python2 only bug as well.

One documentation issue (7661) that people may have been relying on the
convenient but wrong behavior of imshow on non-linear axes.  Had hoped to
get to this tonight, but did not :(

Two jupyter related issues (a failure of notebook that I can not reproduce
and issues with the inline on retina which may be on the jupyter side)

I think tagging this coming weekend (2017-01-14 or 2017-01-15) is a
distinct possibility.

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

From matthew.brett at gmail.com  Tue Jan 10 05:33:17 2017
From: matthew.brett at gmail.com (Matthew Brett)
Date: Tue, 10 Jan 2017 10:33:17 +0000
Subject: [Matplotlib-devel] v2.0 home stretch
In-Reply-To: <CAA48SF_wWogOVaKs3ENg4wDoF+S7=n_+S6hgHQKiuYTP8snLhQ@mail.gmail.com>
References: <CAA48SF_wWogOVaKs3ENg4wDoF+S7=n_+S6hgHQKiuYTP8snLhQ@mail.gmail.com>
Message-ID: <CAH6Pt5oypPUiFCMJhi4+u8+T4e6SNyTKu7a78ZMAOHoUPoYFBA@mail.gmail.com>

On Tue, Jan 10, 2017 at 5:53 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Folks,
>
> We are getting very close to the end :)
>
> https://github.com/matplotlib/matplotlib/milestone/14
>
> The tableau color namespace needs to be merged.  I think 'tc' is the best of
> the options that were proposed (the full name is too long and too hard to
> spell).

'tc' - nice!

:)

Matthew

From matthew.brett at gmail.com  Sat Jan 14 13:10:17 2017
From: matthew.brett at gmail.com (Matthew Brett)
Date: Sat, 14 Jan 2017 10:10:17 -0800
Subject: [Matplotlib-devel] Python 3.6 wheels uploaded - need testing
Message-ID: <CAH6Pt5pymCtp65e2pi048gd=0zKRhQjp2f8JZV1q1V+9jXLybw@mail.gmail.com>

Hi,

I just uploaded pypi wheels for Python 3.6 on OSX and Linux; I think
we're going to be uploading Windows wheels soon as well.

We have an odd test error for the Python 3.6 wheels on OSX :
https://github.com/matplotlib/matplotlib/issues/7799 .  We're guessing
that this error will be uncommon in practice, but we'd love feedback
on your experience of using these wheels:

pip install --user -U matplotlib

Cheers,

Matthew

From max.linke88 at gmail.com  Mon Jan 16 10:23:05 2017
From: max.linke88 at gmail.com (Max Linke)
Date: Mon, 16 Jan 2017 16:23:05 +0100
Subject: [Matplotlib-devel] GSOC 2017: NumFOCUS will be an umbrella
 organization
Message-ID: <40f85dfb-0635-a042-79b7-039d3dd347a9@gmail.com>

Hi

Organizations can start submitting applications for Google Summer of Code
2017 on January 19 (and the deadline is February 9)

https://developers.google.com/open-source/gsoc/timeline?hl=en

NumFOCUS will be applying again this year. If you want to work with us
please let me know and if you apply as an organization yourself or under a
different umbrella organization please tell me as well. If you participate
with us it would be great if you start to add possible projects to the
ideas page on github soon. We some general information for mentors on
github.

https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-mentors.md

We also have a template for ideas that might help. It lists the things
Google likes to see.

https://github.com/numfocus/gsoc/blob/master/2017/ideas-list-skeleton.md

In case you participated in earlier years with NumFOCUS there are some
small changes this year. Raniere won't be the admin this year. Instead I'm
going to be the admin. We are also planning to include two explicit rules
when a student should be failed, they have to communicate regularly and
commit code into your development branch at the end of the summer.

best, Max

From tcaswell at gmail.com  Mon Jan 16 17:33:24 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 16 Jan 2017 22:33:24 +0000
Subject: [Matplotlib-devel] 2017-01-16 dev phone call
Message-ID: <CAA48SF9+VKyjt2KR5OZ+Qower_-q=ke6DMZ-PHOrmW2AU=bT3Q@mail.gmail.com>

Folks,

Today we had tacaswell, efiring, nellev, dopplershift, story645,
and phobson (went with github handles) on the call.

We discussed the outstanding issues for 2.0

 - punted the hatch changes  (#7750) issue to 2.2
 - merged the color names with the prefix 'tab' for the tableau color
palette
 - merged the supression of numpy warnings, this should result in a report
upstream to numpy
 - tweaked the imshow-now-is-scale-aware docs,

With that, everything we had tagged for 2.0 is done, so I will create the
tag tonight.  If you have any last-minute issues you only have a few hours
to raise them!

The very short term release schedule is a 2.0.1 if needed (1wk-1mo time
scale) with any critical bugs or regressions and 2.1 in March-April.

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

From tcaswell at gmail.com  Mon Jan 16 18:12:46 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 16 Jan 2017 23:12:46 +0000
Subject: [Matplotlib-devel] 2016-01-16 phone call
Message-ID: <CAA48SF-N85N9XDZYth3TKOyTEi_tOW4DNXG+MT2TNkEYsLsP2A@mail.gmail.com>

Folks,

Sorry, got distracted writing the first email and forget to include:

 - discussed moving https://phobson.github.io/mpl-probscale/ into the
matplotlib organization
 - numFOCUS is going to participate in google summer of code again this
year, we should mentor again this summer.  A follow on email will be coming
about this.
 - suggested that I screen-capture the process of doing a release.

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

From tcaswell at gmail.com  Mon Jan 16 22:16:31 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 17 Jan 2017 03:16:31 +0000
Subject: [Matplotlib-devel] 2.0 is tagged
Message-ID: <CAA48SF-mG18-Zsj44P5X0oxRDxynvpW0MzBxjdVnrn_je0OkUg@mail.gmail.com>

Folks,

At long last, 2.0 has been tagged :)  A BIG "thank you" to everyone who
help with this!

Wide-spread announcement will go out once all of the binaries are built and
available.  The docs will be available at matplotlib.org/2.0.0 and the main
landing page will be updated once all of the binaries are available and the
release is announced.

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

From efiring at hawaii.edu  Mon Jan 16 22:30:12 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Mon, 16 Jan 2017 17:30:12 -1000
Subject: [Matplotlib-devel] 2.0 is tagged
In-Reply-To: <CAA48SF-mG18-Zsj44P5X0oxRDxynvpW0MzBxjdVnrn_je0OkUg@mail.gmail.com>
References: <CAA48SF-mG18-Zsj44P5X0oxRDxynvpW0MzBxjdVnrn_je0OkUg@mail.gmail.com>
Message-ID: <06c3209f-e69a-7464-82aa-e74c8726e5d5@hawaii.edu>

And a triple-BIG thanks to *you*, Tom, for all your suburb work on the 
management as well as the technical side.

Eric

On 2017/01/16 5:16 PM, Thomas Caswell wrote:
> Folks,
>
> At long last, 2.0 has been tagged :)  A BIG "thank you" to everyone who
> help with this!
>
> Wide-spread announcement will go out once all of the binaries are built
> and available.  The docs will be available at matplotlib.org/2.0.0
> <http://matplotlib.org/2.0.0> and the main landing page will be updated
> once all of the binaries are available and the release is announced.
>
> Tom
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>


From tcaswell at gmail.com  Mon Jan 16 23:33:50 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 17 Jan 2017 04:33:50 +0000
Subject: [Matplotlib-devel] branches going forward
Message-ID: <CAA48SF9nNsGsuuTLF62n2bRCuJ0mMxiOptUoWhMHpm2zx4Ky-w@mail.gmail.com>

Folks,

One last house keeping thing, we have reverted to our 'standard' branch
structure

2.0.x : where 2.0.1 will be cut from
2.0.0-doc : can be used to rebuild the main webpage, rst and example
changes only

master : where 2.1 will be cut from

The 2.x branch will be deleted tomorrow.

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

From vincent.adrien at gmail.com  Tue Jan 17 02:45:31 2017
From: vincent.adrien at gmail.com (vincent.adrien at gmail.com)
Date: Tue, 17 Jan 2017 08:45:31 +0100
Subject: [Matplotlib-devel] 2.0 is tagged
In-Reply-To: <06c3209f-e69a-7464-82aa-e74c8726e5d5@hawaii.edu>
References: <CAA48SF-mG18-Zsj44P5X0oxRDxynvpW0MzBxjdVnrn_je0OkUg@mail.gmail.com>
 <06c3209f-e69a-7464-82aa-e74c8726e5d5@hawaii.edu>
Message-ID: <587DCB9B.9080606@gmail.com>

I would like to join Eric and Tom to thank everyone (including them !)
who got involded in making 2.0 possible. I am very happy to see it going
out, and I am pretty sure I am not the only one :) !

Regards,

Adrien

On 17/01/2017 04:30, Eric Firing wrote:
> And a triple-BIG thanks to *you*, Tom, for all your suburb work on the
> management as well as the technical side.
> 
> Eric
> 
> On 2017/01/16 5:16 PM, Thomas Caswell wrote:
>> Folks,
>>
>> At long last, 2.0 has been tagged :)  A BIG "thank you" to everyone who
>> help with this!
>>
>> Wide-spread announcement will go out once all of the binaries are built
>> and available.  The docs will be available at matplotlib.org/2.0.0
>> <http://matplotlib.org/2.0.0> and the main landing page will be updated
>> once all of the binaries are available and the release is announced.
>>
>> Tom
>>
>>
>>
>> _______________________________________________
>> 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


From tcaswell at gmail.com  Tue Jan 17 11:55:12 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Tue, 17 Jan 2017 16:55:12 +0000
Subject: [Matplotlib-devel] [REL] matplotlib v2.0.0
Message-ID: <CAA48SF-ThsWTT6tnXzpqc70RVrcAxWp+aBRxhTeieoJJUmJpoA@mail.gmail.com>

Folks,

We are happy to announce the release of (long delayed) matplotlib 2.0!
This release completely overhauls the default style of the plots.

The source tarball and wheels for Mac, Win, and manylinux for python 2.7,
3.4-3.6 are available on pypi

   pip install --upgrade matplotlib

and conda packages for Mac, Win, linux for python 2.7, 3.4-3.6 are
available from conda-forge

   conda install matplotlib -c conda-forge


Highlights include:

 - 'viridis' is default color map instead of jet.
 - Modernized the default color cycle.
 - Many more functions respect the color cycle.
 - Line dash patterns scale with linewidth.
 - Change default font to DejaVu, now supports most Western alphabets
(including Greek, Cyrillic and Latin with diacritics), math symbols and
emoji out of the box.
 - Faster text rendering.
 - Improved auto-limits.
 - Ticks out and only on the right and bottom spines by default.
 - Improved auto-ticking, particularly for log scales and dates.
 - Improved image support (imshow respects scales and eliminated a class of
artifacts).

For a full list of the default changes (along with how to revert them)
please see http://matplotlib.org/users/dflt_style_changes.html and
http://matplotlib.org/users/whats_new.html#new-in-matplotlib-2-0.

There were a number of small API changes documented at
http://matplotlib.org/api/api_changes.html#api-changes-in-2-0-0

I would like to thank everyone who helped on this release in anyway.  The
people at 2015 scipy BOF where this got started, users who provided
feedback and suggestions along the way, the beta-testers, Nathaniel, Stefan
and Eric for the new color maps, and all of the documentation and code
contributors.

Please report any issues to matplotlib-users at python.org (will have to join
to post un-moderated) or https://github.com/matplotlib/matplotlib/issues .

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

From tcaswell at gmail.com  Wed Jan 18 23:55:24 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 19 Jan 2017 04:55:24 +0000
Subject: [Matplotlib-devel] repo for talk / tutorial material
Message-ID: <CAA48SF-+ZYRDsvRBPQvAgC6ihXif2O1NTd65Cg=FNUdXh3vAWw@mail.gmail.com>

Folks,

I think it would be good to collect material for all the talks we give
about Matplotlib in one place.

I have started by putting all of the material for the talks I have given in
the last 2 years or so in https://github.com/tacaswell/presentations (I am
still losing to the table markup in the README :( )

The two talks from 2016 (which are almost the same) may be good starting
points for people who want to give a talk about mpl 2.0!

If people think this is a good idea I will move it into the matplotlib org.

I would further propose that the merge criteria for this repo is 'talk was
actually given and author wants to submit material'.

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

From rmay31 at gmail.com  Thu Jan 19 10:27:20 2017
From: rmay31 at gmail.com (Ryan May)
Date: Thu, 19 Jan 2017 08:27:20 -0700
Subject: [Matplotlib-devel] repo for talk / tutorial material
In-Reply-To: <CAA48SF-+ZYRDsvRBPQvAgC6ihXif2O1NTd65Cg=FNUdXh3vAWw@mail.gmail.com>
References: <CAA48SF-+ZYRDsvRBPQvAgC6ihXif2O1NTd65Cg=FNUdXh3vAWw@mail.gmail.com>
Message-ID: <CAKH0P+XATy5eD7SqURseh1dpKVmbvaz3fN8z=wnK0hehhdsaTg@mail.gmail.com>

+1 to moving the repo to the organization.

Ryan

On Wed, Jan 18, 2017 at 9:55 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> I think it would be good to collect material for all the talks we give
> about Matplotlib in one place.
>
> I have started by putting all of the material for the talks I have given
> in the last 2 years or so in https://github.com/tacaswell/presentations (I
> am still losing to the table markup in the README :( )
>
> The two talks from 2016 (which are almost the same) may be good starting
> points for people who want to give a talk about mpl 2.0!
>
> If people think this is a good idea I will move it into the matplotlib org.
>
> I would further propose that the merge criteria for this repo is 'talk was
> actually given and author wants to submit material'.
>
> Tom
>
> _______________________________________________
> 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/20170119/aa6f97db/attachment.html>

From ben.v.root at gmail.com  Thu Jan 19 10:39:26 2017
From: ben.v.root at gmail.com (Benjamin Root)
Date: Thu, 19 Jan 2017 10:39:26 -0500
Subject: [Matplotlib-devel] repo for talk / tutorial material
In-Reply-To: <CAKH0P+XATy5eD7SqURseh1dpKVmbvaz3fN8z=wnK0hehhdsaTg@mail.gmail.com>
References: <CAA48SF-+ZYRDsvRBPQvAgC6ihXif2O1NTd65Cg=FNUdXh3vAWw@mail.gmail.com>
 <CAKH0P+XATy5eD7SqURseh1dpKVmbvaz3fN8z=wnK0hehhdsaTg@mail.gmail.com>
Message-ID: <CANNq6FnGCks-C_rv-DFuVwF62fgOqkBVjsSN65kpq8GWd1Vu1w@mail.gmail.com>

How would we handle things like my Anatomy of Matplotlib repo? It is
already an established repo, and people go there to pick up notebooks. Do
we do one of those sub-repo git thingys?

On Thu, Jan 19, 2017 at 10:27 AM, Ryan May <rmay31 at gmail.com> wrote:

> +1 to moving the repo to the organization.
>
> Ryan
>
> On Wed, Jan 18, 2017 at 9:55 PM, Thomas Caswell <tcaswell at gmail.com>
> wrote:
>
>> Folks,
>>
>> I think it would be good to collect material for all the talks we give
>> about Matplotlib in one place.
>>
>> I have started by putting all of the material for the talks I have given
>> in the last 2 years or so in https://github.com/tacaswell/presentations (I
>> am still losing to the table markup in the README :( )
>>
>> The two talks from 2016 (which are almost the same) may be good starting
>> points for people who want to give a talk about mpl 2.0!
>>
>> If people think this is a good idea I will move it into the matplotlib
>> org.
>>
>> I would further propose that the merge criteria for this repo is 'talk
>> was actually given and author wants to submit material'.
>>
>> Tom
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
> Ryan May
>
>
> _______________________________________________
> 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/20170119/db8a8949/attachment.html>

From tcaswell at gmail.com  Thu Jan 19 10:51:33 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 19 Jan 2017 15:51:33 +0000
Subject: [Matplotlib-devel] repo for talk / tutorial material
In-Reply-To: <CANNq6FnGCks-C_rv-DFuVwF62fgOqkBVjsSN65kpq8GWd1Vu1w@mail.gmail.com>
References: <CAA48SF-+ZYRDsvRBPQvAgC6ihXif2O1NTd65Cg=FNUdXh3vAWw@mail.gmail.com>
 <CAKH0P+XATy5eD7SqURseh1dpKVmbvaz3fN8z=wnK0hehhdsaTg@mail.gmail.com>
 <CANNq6FnGCks-C_rv-DFuVwF62fgOqkBVjsSN65kpq8GWd1Vu1w@mail.gmail.com>
Message-ID: <CAA48SF-=F2-o9LDhL=+hnYGToG2VHfydbZG9xZxwtGYnOStWiQ@mail.gmail.com>

I would deal with that via links from the README (to first order).  That is
the least maintenance, meaning it is the least likely to end up wrong ;)
 We should also consider moving Anatomy of Matplotlib into the org
(assuming Ben is game).

The pydata dc tutorial I dumped in there also has it's own existing repo
(hesitate to call it 'established') and I have gone back-and-forth on this
issue.

Tom

On Thu, Jan 19, 2017 at 10:39 AM Benjamin Root <ben.v.root at gmail.com> wrote:

> How would we handle things like my Anatomy of Matplotlib repo? It is
> already an established repo, and people go there to pick up notebooks. Do
> we do one of those sub-repo git thingys?
>
> On Thu, Jan 19, 2017 at 10:27 AM, Ryan May <rmay31 at gmail.com> wrote:
>
> +1 to moving the repo to the organization.
>
> Ryan
>
> On Wed, Jan 18, 2017 at 9:55 PM, Thomas Caswell <tcaswell at gmail.com>
> wrote:
>
> Folks,
>
> I think it would be good to collect material for all the talks we give
> about Matplotlib in one place.
>
> I have started by putting all of the material for the talks I have given
> in the last 2 years or so in https://github.com/tacaswell/presentations (I
> am still losing to the table markup in the README :( )
>
> The two talks from 2016 (which are almost the same) may be good starting
> points for people who want to give a talk about mpl 2.0!
>
> If people think this is a good idea I will move it into the matplotlib org.
>
> I would further propose that the merge criteria for this repo is 'talk was
> actually given and author wants to submit material'.
>
> Tom
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>
>
> --
> Ryan May
>
>
> _______________________________________________
> 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/20170119/8a55044d/attachment-0001.html>

From matthew.brett at gmail.com  Thu Jan 19 14:54:03 2017
From: matthew.brett at gmail.com (Matthew Brett)
Date: Thu, 19 Jan 2017 11:54:03 -0800
Subject: [Matplotlib-devel] Confusion about draw_artist
In-Reply-To: <CAA48SF_RCrwUm8LBj0JNYdM+q28TJXkBnzaZaYs-b-c5V4_i6w@mail.gmail.com>
References: <CAH6Pt5pNcbAHONKuvDs6gwcLFhdnwoXtiDq-wNsNRPMO373faA@mail.gmail.com>
 <CAA48SF_RCrwUm8LBj0JNYdM+q28TJXkBnzaZaYs-b-c5V4_i6w@mail.gmail.com>
Message-ID: <CAH6Pt5rVrn-MOySuEr=YRrwFRMDxAQRHL71ChXGu4uny=y66Ow@mail.gmail.com>

Hi,

Sorry to keep displaying my confusion on this one but...

On Wed, Jan 4, 2017 at 6:58 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Unless you have flagged the artist as `animated` (via `set_animated` or by
> kwarg), it will be drawn as part of the next re-draw.

Adding `set_animated` doesn't help in the example above;

fig, ax = plt.subplots(1, 1)
ax.set_animated(True)
im = plt.imshow([[1, 2], [3, 4]])
fig.canvas.draw()
ax.draw_artist(im)

> You are better off
> just changing the `fig.canvas.draw()` to `fig.canvas.draw_idle()` and
> letting the GUI decide when to re-draw things.

Changing to `fig.canvas.draw_idle()` above doesn't prevent the error
from `draw_artist`, but I guess I should not have expected it would.
So I guess my question is - how do I use `draw_artist` in this case?
Is there any way to make sure that the renderer is cached first?

> If you want to get any performance gain from animated artists + draw_artist
> you will need to use blitting (which will work with the OSX backend in 2.0).

Yup, the real code does use blitting, but thanks for the reminder,

Cheers,

Matthew

From tcaswell at gmail.com  Sat Jan 21 20:51:13 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sun, 22 Jan 2017 01:51:13 +0000
Subject: [Matplotlib-devel] [scikit-image] GSOC 2017: NumFOCUS will be
 an umbrella organization
In-Reply-To: <40f85dfb-0635-a042-79b7-039d3dd347a9@gmail.com>
References: <40f85dfb-0635-a042-79b7-039d3dd347a9@gmail.com>
Message-ID: <CAA48SF-gSJ=C7=99yk4hBw3FC8S7BkbuOGch3fWCRivZYHO8-Q@mail.gmail.com>

Max: Matplotlib is interested in participating again this year.

I have opened a PR https://github.com/numfocus/gsoc/pull/158 starting to
update our ideas list and there is an on-going discussion in gitter.

MPL folks:

Anyone who has ideas for projects or would like to (co)-mentor please speak
up!

Tom

On Mon, Jan 16, 2017 at 10:23 AM Max Linke <max.linke88 at gmail.com> wrote:

> Hi
>
> Organizations can start submitting applications for Google Summer of Code
> 2017 on January 19 (and the deadline is February 9)
>
> https://developers.google.com/open-source/gsoc/timeline?hl=en
>
> NumFOCUS will be applying again this year. If you want to work with us
> please let me know and if you apply as an organization yourself or under a
> different umbrella organization please tell me as well. If you participate
> with us it would be great if you start to add possible projects to the
> ideas page on github soon. We some general information for mentors on
> github.
>
> https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-mentors.md
>
> We also have a template for ideas that might help. It lists the things
> Google likes to see.
>
> https://github.com/numfocus/gsoc/blob/master/2017/ideas-list-skeleton.md
>
> In case you participated in earlier years with NumFOCUS there are some
> small changes this year. Raniere won't be the admin this year. Instead I'm
> going to be the admin. We are also planning to include two explicit rules
> when a student should be failed, they have to communicate regularly and
> commit code into your development branch at the end of the summer.
>
> best, Max
> _______________________________________________
> scikit-image mailing list
> scikit-image at python.org
> https://mail.python.org/mailman/listinfo/scikit-image
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170122/2e8083d8/attachment.html>

From tcaswell at gmail.com  Mon Jan 23 17:10:35 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 23 Jan 2017 22:10:35 +0000
Subject: [Matplotlib-devel] branch updates
Message-ID: <CAA48SF_Ng0S5KG=TD9h2mQh5Psx-ispfGct+XwKQybLdqqR4CQ@mail.gmail.com>

Folks,

Just a quick update about the current branch on upstream:

 - master : where 2.1 will be cut from.  This is open for new features.
 - 2.0.x : where 2.0.1 will be cut from.  Only bug-fixes should be
merged/backported.  If in doubt, ask!
 - 2.0.0-doc : can be used to rebuild the documentation.  Only changes to
the rst or examples can be merged/backported to this branch.

The 2.x branch has been deleted from upstream.  To make sure you do not
have stale references to this around please run

   git remote update --prune

to delete your local references.  It is strongly suggested to delete your
2.x branches (both on your local machines and on your personal github
clones).

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

From tcaswell at gmail.com  Mon Jan 23 17:43:16 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 23 Jan 2017 22:43:16 +0000
Subject: [Matplotlib-devel] 2017-01-23 phone call notes
Message-ID: <CAA48SF8uH_7Br_NXp0AerFrn3R7Phuo4ow2J4KMaWtwzfBW_Sw@mail.gmail.com>

Folks,

Today we had my self, nellev and efiring.

 - Discussed that we have had surprisingly few 2.0 related bug reports,
unclear if we have not had uptake yet or if we really didn't break all that
much

 - Discussed existing branches on upstream, tried to see if we could
restrict permissions to create new branches on upstream, seems like not
(coupled to write permissions).  Please be careful to not push new branches
to upstream!

 - CI is taking too long, how to speed up:
   - drop builds on PRs (and only do on master), candidates are dropping
3.4 or 3.5
   - reduce appveyor matrix on PRs
   - (not discussed on call) raise ~500$USD / yr to get 2 appveyor builds.
   - make the doc build faster (can we cache anything?)
   - auto-canceling super-ceded PR builds is in beta on travis. Just being
patient might work here.

 - BIDS is working on a distributed 'doc-a-thon', (Nelle will follow up
with details if mpl wants to participate).
   - discussed difficulty of reviewing doc changes (are they correct? is
english correct? is it formatted properly?)

 - discussed possibility of a in-person sprint (again Nelle will follow up)

Please correct me if I missed anything, wrote this from memory after the
fact.

Tom

PS Sorry for stealing some of your thunder Nelle :(
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170123/922143f6/attachment.html>

From vincent.adrien at gmail.com  Tue Jan 24 01:38:35 2017
From: vincent.adrien at gmail.com (vincent.adrien at gmail.com)
Date: Tue, 24 Jan 2017 07:38:35 +0100
Subject: [Matplotlib-devel] 2017-01-23 phone call notes
In-Reply-To: <CAA48SF8uH_7Br_NXp0AerFrn3R7Phuo4ow2J4KMaWtwzfBW_Sw@mail.gmail.com>
References: <CAA48SF8uH_7Br_NXp0AerFrn3R7Phuo4ow2J4KMaWtwzfBW_Sw@mail.gmail.com>
Message-ID: <460d30d6-422e-7dd6-8534-aefb9137577a@gmail.com>

Hi Tom,

Just to say that this kind of short summaries of what have been
discussed during the phone calls are appreciated (at least by myself,
but I am confident I am not the only one).

Regards

Adrien

Le 23/01/2017 ? 23:43, Thomas Caswell a ?crit :
> Folks,
> 
> Today we had my self, nellev and efiring.
> 
>  - Discussed that we have had surprisingly few 2.0 related bug reports,
> unclear if we have not had uptake yet or if we really didn't break all
> that much
> 
>  - Discussed existing branches on upstream, tried to see if we could
> restrict permissions to create new branches on upstream, seems like not
> (coupled to write permissions).  Please be careful to not push new
> branches to upstream!
> 
>  - CI is taking too long, how to speed up:
>    - drop builds on PRs (and only do on master), candidates are dropping
> 3.4 or 3.5
>    - reduce appveyor matrix on PRs
>    - (not discussed on call) raise ~500$USD / yr to get 2 appveyor builds.
>    - make the doc build faster (can we cache anything?) 
>    - auto-canceling super-ceded PR builds is in beta on travis. Just
> being patient might work here.
> 
>  - BIDS is working on a distributed 'doc-a-thon', (Nelle will follow up
> with details if mpl wants to participate). 
>    - discussed difficulty of reviewing doc changes (are they correct? is
> english correct? is it formatted properly?)
> 
>  - discussed possibility of a in-person sprint (again Nelle will follow up)
> 
> Please correct me if I missed anything, wrote this from memory after the
> fact.
> 
> Tom
> 
> PS Sorry for stealing some of your thunder Nelle :(
> 
> 
> _______________________________________________
> 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 24 13:28:07 2017
From: antony.lee at berkeley.edu (Antony Lee)
Date: Tue, 24 Jan 2017 10:28:07 -0800
Subject: [Matplotlib-devel] 2017-01-23 phone call notes
In-Reply-To: <460d30d6-422e-7dd6-8534-aefb9137577a@gmail.com>
References: <CAA48SF8uH_7Br_NXp0AerFrn3R7Phuo4ow2J4KMaWtwzfBW_Sw@mail.gmail.com>
 <460d30d6-422e-7dd6-8534-aefb9137577a@gmail.com>
Message-ID: <CAGRr6BHfE6jb0QSgArpo1ZUR3uzH8sbn098VaWnXH_P+7f_+wQ@mail.gmail.com>

I agree with Adrien regarding the helpfulness of these summaries.

Regarding CI, perhaps someone (cough BIDS cough) could write something to
skip builds when a patch only changes nonpython files or docstrings?
 (Especially if you compare both with the target branch and with the
previous built version of the PR, we should catch skip quite a few "small
add documentation" patches.)

Antony

2017-01-23 22:38 GMT-08:00 vincent.adrien at gmail.com <
vincent.adrien at gmail.com>:

> Hi Tom,
>
> Just to say that this kind of short summaries of what have been
> discussed during the phone calls are appreciated (at least by myself,
> but I am confident I am not the only one).
>
> Regards
>
> Adrien
>
> Le 23/01/2017 ? 23:43, Thomas Caswell a ?crit :
> > Folks,
> >
> > Today we had my self, nellev and efiring.
> >
> >  - Discussed that we have had surprisingly few 2.0 related bug reports,
> > unclear if we have not had uptake yet or if we really didn't break all
> > that much
> >
> >  - Discussed existing branches on upstream, tried to see if we could
> > restrict permissions to create new branches on upstream, seems like not
> > (coupled to write permissions).  Please be careful to not push new
> > branches to upstream!
> >
> >  - CI is taking too long, how to speed up:
> >    - drop builds on PRs (and only do on master), candidates are dropping
> > 3.4 or 3.5
> >    - reduce appveyor matrix on PRs
> >    - (not discussed on call) raise ~500$USD / yr to get 2 appveyor
> builds.
> >    - make the doc build faster (can we cache anything?)
> >    - auto-canceling super-ceded PR builds is in beta on travis. Just
> > being patient might work here.
> >
> >  - BIDS is working on a distributed 'doc-a-thon', (Nelle will follow up
> > with details if mpl wants to participate).
> >    - discussed difficulty of reviewing doc changes (are they correct? is
> > english correct? is it formatted properly?)
> >
> >  - discussed possibility of a in-person sprint (again Nelle will follow
> up)
> >
> > Please correct me if I missed anything, wrote this from memory after the
> > fact.
> >
> > Tom
> >
> > PS Sorry for stealing some of your thunder Nelle :(
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170124/fec6d996/attachment.html>

From nelle.varoquaux at gmail.com  Wed Jan 25 13:15:24 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Wed, 25 Jan 2017 10:15:24 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
Message-ID: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>

Hello everyone,

Now that the pytest migration is almost over (thanks Elliott!), I was
wondering if this could be a good opportunity to reorganize the test files
to follow a "normal" python package structure.
The recommended python package structure is to place a tests folder in each
submodule, and the relevant tests files in this folder.

To take a concrete example, it would for example require moving the tests
corresponding of matplotlib.sphinx_ext.mathmpl.py  to
matplotlib/sphinxext/tests/test_mathmpl.py

This would be a more or less incompatible change in the sense that
matplotlib.tests seems to be an importable module (it probably shouldn't),
with about a dozen functions. We could easily make this backward compatible
in case anyone does use this module anywhere.

['__builtins__',
 '__cached__',
 '__doc__',
 '__file__',
 '__loader__',
 '__name__',
 '__package__',
 '__path__',
 '__spec__',
 '_multiprocess_can_split_',
 'absolute_import',
 'assert_str_equal',
 'difflib',
 'division',
 'os',
 'print_function',
 'setup',
 'six',
 'unicode_literals']

If we go down that route, we need to completely finish the pytest migration
first.

Cheers,
N
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170125/09045d4b/attachment.html>

From tcaswell at gmail.com  Wed Jan 25 14:30:55 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 25 Jan 2017 19:30:55 +0000
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
Message-ID: <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>

I am against moving the test files into the sub-modules.

It seems like a lot of thrashing (on the down-stream packagers who package
the main library and tests separately and on peoples brains) for no obvious
gain.

Tom

On Wed, Jan 25, 2017 at 1:15 PM Nelle Varoquaux <nelle.varoquaux at gmail.com>
wrote:

Hello everyone,

Now that the pytest migration is almost over (thanks Elliott!), I was
wondering if this could be a good opportunity to reorganize the test files
to follow a "normal" python package structure.
The recommended python package structure is to place a tests folder in each
submodule, and the relevant tests files in this folder.

To take a concrete example, it would for example require moving the tests
corresponding of matplotlib.sphinx_ext.mathmpl.py  to
matplotlib/sphinxext/tests/test_mathmpl.py

This would be a more or less incompatible change in the sense that
matplotlib.tests seems to be an importable module (it probably shouldn't),
with about a dozen functions. We could easily make this backward compatible
in case anyone does use this module anywhere.

['__builtins__',
 '__cached__',
 '__doc__',
 '__file__',
 '__loader__',
 '__name__',
 '__package__',
 '__path__',
 '__spec__',
 '_multiprocess_can_split_',
 'absolute_import',
 'assert_str_equal',
 'difflib',
 'division',
 'os',
 'print_function',
 'setup',
 'six',
 'unicode_literals']

If we go down that route, we need to completely finish the pytest migration
first.

Cheers,
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/20170125/658f0919/attachment.html>

From nelle.varoquaux at gmail.com  Wed Jan 25 14:38:55 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Wed, 25 Jan 2017 11:38:55 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
Message-ID: <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>

> I am against moving the test files into the sub-modules.
>
> It seems like a lot of thrashing (on the down-stream packagers who package
> the main library and tests separately and on peoples brains) for no obvious
> gain.
>

Actually, it is really a pain that Matplotlib doesn't follow python
standards for any contributors that contributes to any other python
packages. I would suspect that it is also annoying for downstream packages
that Matplotlib does not follow standards.
The reason I brought this up in the first place is because it took me a
couple of minutes to look for a test for cbook.mkdirs function while
reviewing a PR, and had to resort to doing a git grep to convince me it
wasn't tested. If we had followed the standards in the first place, it
would probably have taken me 5seconds.

I have the same feeling for Matplotlib's unstandard  packaging layout.

N


>
> Tom
>
> On Wed, Jan 25, 2017 at 1:15 PM Nelle Varoquaux <nelle.varoquaux at gmail.com>
> wrote:
>
> Hello everyone,
>
> Now that the pytest migration is almost over (thanks Elliott!), I was
> wondering if this could be a good opportunity to reorganize the test files
> to follow a "normal" python package structure.
> The recommended python package structure is to place a tests folder in
> each submodule, and the relevant tests files in this folder.
>
> To take a concrete example, it would for example require moving the tests
> corresponding of matplotlib.sphinx_ext.mathmpl.py  to
> matplotlib/sphinxext/tests/test_mathmpl.py
>
> This would be a more or less incompatible change in the sense that
> matplotlib.tests seems to be an importable module (it probably shouldn't),
> with about a dozen functions. We could easily make this backward compatible
> in case anyone does use this module anywhere.
>
> ['__builtins__',
>  '__cached__',
>  '__doc__',
>  '__file__',
>  '__loader__',
>  '__name__',
>  '__package__',
>  '__path__',
>  '__spec__',
>  '_multiprocess_can_split_',
>  'absolute_import',
>  'assert_str_equal',
>  'difflib',
>  'division',
>  'os',
>  'print_function',
>  'setup',
>  'six',
>  'unicode_literals']
>
> If we go down that route, we need to completely finish the pytest
> migration first.
>
> Cheers,
> 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/20170125/4b027646/attachment-0001.html>

From morph at debian.org  Wed Jan 25 14:38:58 2017
From: morph at debian.org (Sandro Tosi)
Date: Wed, 25 Jan 2017 14:38:58 -0500
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
Message-ID: <CAB4XWXxSkD0us4mB9x+rP8DL1SUj+3i7R-X7L+vzvdj2L0PPGg@mail.gmail.com>

On Wed, Jan 25, 2017 at 1:15 PM, Nelle Varoquaux
<nelle.varoquaux at gmail.com> wrote:
> matplotlib.tests seems to be an importable module (it probably shouldn't)


there other external modules (cant recall which ones, but i can look
that up if you want) depending on mpl.tests being importable as they
are using its functions to run their tests

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

From tcaswell at gmail.com  Wed Jan 25 16:53:29 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 25 Jan 2017 21:53:29 +0000
Subject: [Matplotlib-devel] project email addresses
Message-ID: <CAA48SF94uSFyd94diMDCS=2Hhyi-hhtsZ-HeuYctjF1JNvLcSQ@mail.gmail.com>

Folks,

We just got matplotlib at numfocus.org as a usable email address.  The initial
impetus to get this address was for use with appveyor, but I suspect it may
be useful for other reasons.

If you would like / need access send me an email off-list and we will sort
how to get you the password.

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

From nelle.varoquaux at gmail.com  Wed Jan 25 16:53:58 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Wed, 25 Jan 2017 13:53:58 -0800
Subject: [Matplotlib-devel] Internation Matplotlib sprint
Message-ID: <CAE-UAvRDoF4Kid6Euu99vZ9EJLEO4ykjjz_8+q-FAFuSK+jdcw@mail.gmail.com>

Hello everyone,

As Thomas mentioned in the meeting summary report, we are considering
organizing a sprint. Because our team is so international, we need to find
a convenient location for all/most of us, and estimate how much funding we
need to organize such an event.

A possibility would be to organize it just after Scipy, in Austin, as some
of us will be funded to attend. Please note that the bathroom bill is
currently under discussion by the Texas Congress, and thus it is possible
that publicly funded organisation won't be able to reimburse travel to
Scipy 2016 this year.

In order to estimate the budget, please fill in this very short survey:
https://docs.google.com/forms/d/e/1FAIpQLSfUB86RsrYGkJoJEEPxmlS-VwYrAi8JtmukSNNs1eReZeMIKA/viewform

This is nothing definite: we're just trying to see what's possible :)

Thanks,
Nelle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170125/f49d6d8f/attachment.html>

From chris.barker at noaa.gov  Fri Jan 27 17:07:00 2017
From: chris.barker at noaa.gov (Chris Barker)
Date: Fri, 27 Jan 2017 17:07:00 -0500
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
 <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
Message-ID: <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>

On Wed, Jan 25, 2017 at 2:38 PM, Nelle Varoquaux <nelle.varoquaux at gmail.com>
wrote:

> Actually, it is really a pain that Matplotlib doesn't follow python
> standards for any contributors that contributes to any other python
> packages.
>

very true, but...

1) If we were starting from scratcth that would be one thing, but a lot of
thrash jsut to meet a "standard" is probably not worth it.

2) I don't know how standardized this concept is, and personally, I don''t
like it (if I understand it correctly, anyway)

I prefer that ALL tests be in one single directory tree, ideally with that
tree mtaching the package / subpacakge/module tree of the project, ie:

project
    __init__.py
    proj_mod1.py
    sub_package1
      __init__.py
      sub_mod1.py
    ...

test_project
    test_proj_mod1.py
    test_sub_package1
        test_sub_mod1.py

i.e. one test file for each module file.

With this method, it would not be hard to find the tests that correspond to
a particular python module.

I'm ambivalent about whether the test files should be importable packages,
and I think there is a lot to be said for keeping the test code outside the
installable package tree altogether, but I definitely don't like them all
intermingled.

though I still don't advocate a lot of churn for this...

-CHB

-- 

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/20170127/964e95b1/attachment.html>

From tom.howard at metoffice.gov.uk  Tue Jan 10 10:14:05 2017
From: tom.howard at metoffice.gov.uk (Howard, Tom)
Date: Tue, 10 Jan 2017 15:14:05 -0000
Subject: [Matplotlib-devel] typo in matplotlib docs
Message-ID: <2754E4738B1BD749A29975621E51954C3EC5367A@EXXCMPD1DAG4.cmpd1.metoffice.gov.uk>

Hi

I noticed a (fairly trivial) typo on page

http://matplotlib.org/users/recipes.html

I couldn't work out how to report it - hope this is a suitable forum.


Details:

ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
ax.plot(t, mu1, lw=2, label='mean population 2', color='yellow')

should be

ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
ax.plot(t, mu2, lw=2, label='mean population 2', color='yellow')


Then the image makes more sense, too!


================================================
Best wishes
Tom

https://drtomhoward.wordpress.com/about/

Tel: +44(0)1392 886678
Dr Tom Howard, Met Office Hadley Centre
FitzRoy Road, Exeter, EX1 3PB, UK

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

From tcaswell at gmail.com  Sat Jan 28 10:59:45 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 28 Jan 2017 15:59:45 +0000
Subject: [Matplotlib-devel] user mailing list policy
Message-ID: <CAA48SF-AVVhoDUhAcLfZtdaM2my7RZ3J0kdNiYXLT_Lh7hxpTQ@mail.gmail.com>

Going through the moderation backlog on matplolib-user we have a way high
false-negative rate of non-subscribing posting with reasonable emails (you
just got a pile of old emails because I cleared the queue).

I think we should either open the user list to any posters or get some sort
of rotation going so that the moderation queue gets handled (ideally) once
a day.

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

From efiring at hawaii.edu  Sat Jan 28 12:45:04 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Sat, 28 Jan 2017 07:45:04 -1000
Subject: [Matplotlib-devel] user mailing list policy
In-Reply-To: <CAA48SF-AVVhoDUhAcLfZtdaM2my7RZ3J0kdNiYXLT_Lh7hxpTQ@mail.gmail.com>
References: <CAA48SF-AVVhoDUhAcLfZtdaM2my7RZ3J0kdNiYXLT_Lh7hxpTQ@mail.gmail.com>
Message-ID: <8fd06482-89f7-1413-559d-9aeed6225daa@hawaii.edu>

Tom,

Is it possible to have it automatically reply to non-subscribers with a 
message telling them to subscribe and re-post?

If it were opened up, wouldn't it get quite a bit of spam?

Do you know how other lists handle this problem?

Eric

On 2017/01/28 5:59 AM, Thomas Caswell wrote:
> Going through the moderation backlog on matplolib-user we have a way
> high false-negative rate of non-subscribing posting with reasonable
> emails (you just got a pile of old emails because I cleared the queue).
>
> I think we should either open the user list to any posters or get some
> sort of rotation going so that the moderation queue gets handled
> (ideally) once a day.
>
> Tom
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>


From nelle.varoquaux at gmail.com  Sat Jan 28 13:27:50 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Sat, 28 Jan 2017 10:27:50 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
 <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
 <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>
Message-ID: <CAE-UAvQ-tnHVq-oNfAv4H-Ft5v=6ocw73yLPoy7xKHQ7GG+y5w@mail.gmail.com>

>
> Actually, it is really a pain that Matplotlib doesn't follow python
>> standards for any contributors that contributes to any other python
>> packages.
>>
>
> very true, but...
>
> 1) If we were starting from scratcth that would be one thing, but a lot of
> thrash jsut to meet a "standard" is probably not worth it.
>

The benefits of following standards for maintainability has been
demonstrated over and over.


> 2) I don't know how standardized this concept is, and personally, I don''t
> like it (if I understand it correctly, anyway)
>

It is extremely standard. Matplotlib is not the only project not following
standards, but it's probably in the 1% of projects not following standards.
More importantly, it is how we (the community) teach how to organize
packages and tests.

numpy, scipy, skimage, pandas, sklearn, sympy, ipython all follow this
standard.
The only other mainstream scientific python package that may not entirely
follow this convention is cython.


> I prefer that ALL tests be in one single directory tree, ideally with that
> tree mtaching the package / subpacakge/module tree of the project, ie:
>

The whole point of convention is to avoid  this.


>
> project
>     __init__.py
>     proj_mod1.py
>     sub_package1
>       __init__.py
>       sub_mod1.py
>     ...
>
> test_project
>     test_proj_mod1.py
>     test_sub_package1
>         test_sub_mod1.py
>
> i.e. one test file for each module file.
>
> With this method, it would not be hard to find the tests that correspond
> to a particular python module.
>
> I'm ambivalent about whether the test files should be importable packages,
> and I think there is a lot to be said for keeping the test code outside the
> installable package tree altogether, but I definitely don't like them all
> intermingled.
>
> though I still don't advocate a lot of churn for this...
>
> -CHB
>
> --
>
> 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/20170128/63357d1a/attachment.html>

From nelle.varoquaux at gmail.com  Sat Jan 28 13:32:50 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Sat, 28 Jan 2017 10:32:50 -0800
Subject: [Matplotlib-devel] typo in matplotlib docs
In-Reply-To: <2754E4738B1BD749A29975621E51954C3EC5367A@EXXCMPD1DAG4.cmpd1.metoffice.gov.uk>
References: <2754E4738B1BD749A29975621E51954C3EC5367A@EXXCMPD1DAG4.cmpd1.metoffice.gov.uk>
Message-ID: <CAE-UAvTZFN_uYYTgLU8Lg_wbDz1OnJKKhE5M34HpxpXQ2HN8OQ@mail.gmail.com>

Hi Tom,

Thanks for reporting. Do you mind opening a pull request to fix this? I am
happy to guide you through the process.

Cheers,
N

On 10 January 2017 at 06:42, Howard, Tom <tom.howard at metoffice.gov.uk>
wrote:

> Hi
>
>
>
> I noticed a (fairly trivial) typo on page
>
>
>
> http://matplotlib.org/users/recipes.html
>
>
>
> I couldn?t work out how to report it ? hope this is a suitable forum.
>
>
>
>
>
> Details:
>
>
>
> ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
>
> ax.plot(t, mu1, lw=2, label='mean population 2', color='yellow')
>
>
>
> should be
>
>
>
> ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
>
> ax.plot(t, mu2, lw=2, label='mean population 2', color='yellow')
>
>
>
>
>
> Then the image makes more sense, too!
>
>
>
>
>
> ================================================
>
> Best wishes
>
> Tom
>
>
>
> https://drtomhoward.wordpress.com/about/
>
>
>
> Tel: +44(0)1392 886678 <+44%201392%20886678>
>
> Dr Tom Howard, Met Office Hadley Centre
>
> FitzRoy Road, Exeter, EX1 3PB, UK
>
>
>
> _______________________________________________
> 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/20170128/f1888e7b/attachment-0001.html>

From tcaswell at gmail.com  Sat Jan 28 13:36:06 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 28 Jan 2017 18:36:06 +0000
Subject: [Matplotlib-devel] typo in matplotlib docs
In-Reply-To: <CAE-UAvTZFN_uYYTgLU8Lg_wbDz1OnJKKhE5M34HpxpXQ2HN8OQ@mail.gmail.com>
References: <2754E4738B1BD749A29975621E51954C3EC5367A@EXXCMPD1DAG4.cmpd1.metoffice.gov.uk>
 <CAE-UAvTZFN_uYYTgLU8Lg_wbDz1OnJKKhE5M34HpxpXQ2HN8OQ@mail.gmail.com>
Message-ID: <CAA48SF_RsZp2Z0AW5cAky6yJDvd4o_YMnPJ+hSaeNzs1xnNx=A@mail.gmail.com>

I think this got fixed in https://github.com/matplotlib/matplotlib/pull/7110

Tom

On Sat, Jan 28, 2017 at 1:33 PM Nelle Varoquaux <nelle.varoquaux at gmail.com>
wrote:

> Hi Tom,
>
> Thanks for reporting. Do you mind opening a pull request to fix this? I am
> happy to guide you through the process.
>
> Cheers,
> N
>
> On 10 January 2017 at 06:42, Howard, Tom <tom.howard at metoffice.gov.uk>
> wrote:
>
> Hi
>
>
>
> I noticed a (fairly trivial) typo on page
>
>
>
> http://matplotlib.org/users/recipes.html
>
>
>
> I couldn?t work out how to report it ? hope this is a suitable forum.
>
>
>
>
>
> Details:
>
>
>
> ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
>
> ax.plot(t, mu1, lw=2, label='mean population 2', color='yellow')
>
>
>
> should be
>
>
>
> ax.plot(t, mu1, lw=2, label='mean population 1', color='blue')
>
> ax.plot(t, mu2, lw=2, label='mean population 2', color='yellow')
>
>
>
>
>
> Then the image makes more sense, too!
>
>
>
>
>
> ================================================
>
> Best wishes
>
> Tom
>
>
>
> https://drtomhoward.wordpress.com/about/
>
>
>
> Tel: +44(0)1392 886678 <+44%201392%20886678>
>
> Dr Tom Howard, Met Office Hadley Centre
>
> FitzRoy Road, Exeter, EX1 3PB, UK
>
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170128/77574b07/attachment.html>

From nelle.varoquaux at gmail.com  Sat Jan 28 13:32:14 2017
From: nelle.varoquaux at gmail.com (Nelle Varoquaux)
Date: Sat, 28 Jan 2017 10:32:14 -0800
Subject: [Matplotlib-devel] our tests
In-Reply-To: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
References: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
Message-ID: <CAE-UAvS8TJ7LJAEsUxCFrRFSOGmKzwA9RExLhT5ad=x1HVK5uA@mail.gmail.com>

>
> Does anyone know why:
>
> 1) In our Travis suite, the USE_PYTEST run takes much longer than the
> others.
>

That's an easy one: the tests that are run with pytest are not run with
nose.  Now that we've migrated most of the tests to pytests, the nose
environment almost doesn't run any tests anymore.


> 2) On master (approximately), when I try to run a single function with
> py.test, it isn't found.  Example:
>

I can't help you on that one, but I'd like to know as well.
I usually run all the tests in a single module.


>
> py.test lib/matplotlib/tests/test_axes.py::test_hist_steplog
> =============================================== test session starts
> ================================================
> platform darwin -- Python 3.5.1, pytest-2.8.5, py-1.4.31, pluggy-0.3.1
> rootdir: /Users/efiring/work/programs/py/mpl/matplotlib, inifile:
> pytest.ini
> collecting 530 items
> =========================================== no tests ran in 0.39 seconds
> ===========================================
> ERROR: not found: /Users/efiring/work/programs/p
> y/mpl/matplotlib/lib/matplotlib/tests/test_axes.py::test_hist_steplog
> (no name '/Users/efiring/work/programs/py/mpl/matplotlib/lib/matplotl
> ib/tests/test_axes.py::test_hist_steplog' in any of [<Module
> 'lib/matplotlib/tests/test_axes.py'>])
>
> 3) Also on master, I get errors with tests.py.  Example:
>
> python tests.py lib/matplotlib/tests/test_axes.py
>
> [snip]
>
> ======================================================================
> ERROR: matplotlib.tests.test_axes.test_errorbar_inputs_shotgun
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/Users/efiring/anaconda/envs/test/lib/python3.5/site-packages/nose/case.py",
> line 198, in runTest
>     self.test(*self.arg)
>   File "/Users/efiring/work/programs/py/mpl/matplotlib/lib/matplotlib/testing/decorators.py",
> line 150, in wrapped_callable
>     func(*args, **kwargs)
> TypeError: test_errorbar_inputs_shotgun() missing 1 required positional
> argument: 'kwargs'
>
> ======================================================================
> ERROR: matplotlib.tests.test_axes.test_remove_shared_axes
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/Users/efiring/anaconda/envs/test/lib/python3.5/site-packages/nose/case.py",
> line 198, in runTest
>     self.test(*self.arg)
>   File "/Users/efiring/work/programs/py/mpl/matplotlib/lib/matplotlib/testing/decorators.py",
> line 150, in wrapped_callable
>     func(*args, **kwargs)
> TypeError: test_remove_shared_axes() missing 2 required positional
> arguments: 'shared_axes_generator' and 'shared_axis_remover'
>
> ----------------------------------------------------------------------
> Ran 437 tests in 142.437s
>
> FAILED (SKIP=1, errors=2)
> Exception ignored in: <generator object TestLoader.loadTestsFromGenerator.<locals>.generate
> at 0x108f40ca8>
> RuntimeError: generator ignored GeneratorExit
>
> Eric
>
> _______________________________________________
> 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/20170128/263854c4/attachment-0001.html>

From tcaswell at gmail.com  Sat Jan 28 13:39:32 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 28 Jan 2017 18:39:32 +0000
Subject: [Matplotlib-devel] user mailing list policy
In-Reply-To: <8fd06482-89f7-1413-559d-9aeed6225daa@hawaii.edu>
References: <CAA48SF-AVVhoDUhAcLfZtdaM2my7RZ3J0kdNiYXLT_Lh7hxpTQ@mail.gmail.com>
 <8fd06482-89f7-1413-559d-9aeed6225daa@hawaii.edu>
Message-ID: <CAA48SF_eD521w-2nAVsEW4f6ryPDyHWdWq-O_uwgj5qKMta+-w@mail.gmail.com>

For what ever reason, the user list gets way less spam than devel or
announce.

The bounce users get looks like:

------

Your mail to 'Matplotlib-users' with the subject

    test of what non-subscribed posters see

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

<url with uid to cancel post>

----

which does not include information on _how_to subscribe.  My random-walk
through the configuration pages on mailman are failing to sort out how to
customize this message.

Tom

On Sat, Jan 28, 2017 at 12:45 PM Eric Firing <efiring at hawaii.edu> wrote:

Tom,

Is it possible to have it automatically reply to non-subscribers with a
message telling them to subscribe and re-post?

If it were opened up, wouldn't it get quite a bit of spam?

Do you know how other lists handle this problem?

Eric

On 2017/01/28 5:59 AM, Thomas Caswell wrote:
> Going through the moderation backlog on matplolib-user we have a way
> high false-negative rate of non-subscribing posting with reasonable
> emails (you just got a pile of old emails because I cleared the queue).
>
> I think we should either open the user list to any posters or get some
> sort of rotation going so that the moderation queue gets handled
> (ideally) once a day.
>
> Tom
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170128/62656fe1/attachment.html>

From njs at pobox.com  Sat Jan 28 14:49:46 2017
From: njs at pobox.com (Nathaniel Smith)
Date: Sat, 28 Jan 2017 11:49:46 -0800
Subject: [Matplotlib-devel] our tests
In-Reply-To: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
References: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
Message-ID: <CAPJVwBkbBBtL2ZXokF5Zdjb=r5BWz1EWmH+dsYPttwNjJhDmVA@mail.gmail.com>

On Jan 28, 2017 8:06 AM, "Eric Firing" <efiring.ocean at gmail.com> wrote:

Does anyone know why:

1) In our Travis suite, the USE_PYTEST run takes much longer than the
others.

2) On master (approximately), when I try to run a single function with
py.test, it isn't found.  Example:

py.test lib/matplotlib/tests/test_axes.py::test_hist_steplog


I've never figured out the syntax for naming a single test -- I think it
might vary depending on things like whether your test directories are
packages? Pytest pulls configuration from the files and directories around
each test, so it kind of needs to "see" the whole test tree.

But, I did (after an embarrassingly long time) discover the fabulous -k
switch. The idea is you run pytest normally so it can see your whole test
suite, but then "-k hist_steplog" tells it to ignore any tests whose name
doesn't have that as a substring.

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

From antony.lee at berkeley.edu  Sat Jan 28 15:26:43 2017
From: antony.lee at berkeley.edu (Antony Lee)
Date: Sat, 28 Jan 2017 12:26:43 -0800
Subject: [Matplotlib-devel] our tests
In-Reply-To: <CAPJVwBkbBBtL2ZXokF5Zdjb=r5BWz1EWmH+dsYPttwNjJhDmVA@mail.gmail.com>
References: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
 <CAPJVwBkbBBtL2ZXokF5Zdjb=r5BWz1EWmH+dsYPttwNjJhDmVA@mail.gmail.com>
Message-ID: <CAGRr6BGhQeDHV9vvg_R5Hjkt_zdnJAvE60Rj32=cPH9VYY6mpw@mail.gmail.com>

FWIW there is an open issue (generally approved by the pytest devs) to
simplify selection of a single test:
https://github.com/pytest-dev/pytest/issues/2193

2017-01-28 11:49 GMT-08:00 Nathaniel Smith <njs at pobox.com>:

> On Jan 28, 2017 8:06 AM, "Eric Firing" <efiring.ocean at gmail.com> wrote:
>
> Does anyone know why:
>
> 1) In our Travis suite, the USE_PYTEST run takes much longer than the
> others.
>
> 2) On master (approximately), when I try to run a single function with
> py.test, it isn't found.  Example:
>
> py.test lib/matplotlib/tests/test_axes.py::test_hist_steplog
>
>
> I've never figured out the syntax for naming a single test -- I think it
> might vary depending on things like whether your test directories are
> packages? Pytest pulls configuration from the files and directories around
> each test, so it kind of needs to "see" the whole test tree.
>
> But, I did (after an embarrassingly long time) discover the fabulous -k
> switch. The idea is you run pytest normally so it can see your whole test
> suite, but then "-k hist_steplog" tells it to ignore any tests whose name
> doesn't have that as a substring.
>
> -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/20170128/0e924e22/attachment.html>

From quantum.analyst at gmail.com  Sat Jan 28 15:46:58 2017
From: quantum.analyst at gmail.com (Elliott Sales de Andrade)
Date: Sat, 28 Jan 2017 15:46:58 -0500
Subject: [Matplotlib-devel] Fwd:  our tests
In-Reply-To: <CAJP_izeqCtR6kfLuqvhN+_HiAzJnUSAqFfaBrPbqS3t-x7nEPg@mail.gmail.com>
References: <8e2b8f16-0491-f023-16ca-1b2c1c871584@gmail.com>
 <CAJP_izeqCtR6kfLuqvhN+_HiAzJnUSAqFfaBrPbqS3t-x7nEPg@mail.gmail.com>
Message-ID: <CAJP_izcBCyuOwAcn-nz59PHHs16ni5bE8jmmGPk1hQFKgT8fEA@mail.gmail.com>

Hi Eric,

Sorry if you receive this twice.

On 24 November 2016 at 18:49, Eric Firing <efiring.ocean at gmail.com> wrote:

> Does anyone know why:
>
> 1) In our Travis suite, the USE_PYTEST run takes much longer than the
> others.
>
>
Nelle has answered this one already.


> 2) On master (approximately), when I try to run a single function with
> py.test, it isn't found.  Example:
>
> py.test lib/matplotlib/tests/test_axes.py::test_hist_steplog
> =============================================== test session starts
> ================================================
> platform darwin -- Python 3.5.1, pytest-2.8.5, py-1.4.31, pluggy-0.3.1
> rootdir: /Users/efiring/work/programs/py/mpl/matplotlib, inifile:
> pytest.ini
> collecting 530 items
> =========================================== no tests ran in 0.39 seconds
> ===========================================
> ERROR: not found: /Users/efiring/work/programs/p
> y/mpl/matplotlib/lib/matplotlib/tests/test_axes.py::test_hist_steplog
> (no name '/Users/efiring/work/programs/py/mpl/matplotlib/lib/matplotl
> ib/tests/test_axes.py::test_hist_steplog' in any of [<Module
> 'lib/matplotlib/tests/test_axes.py'>])
>
>
This works for me; I think you need to update your version of pytest:

py.test lib/matplotlib/tests/test_axes.py::test_hist_steplog
============================= test session starts
=============================
platform linux -- Python 3.5.2, pytest-3.0.3, py-1.4.31, pluggy-0.4.0
rootdir: /home/elliott/code/matplotlib, inifile: pytest.ini
collected 505 items

lib/matplotlib/tests/test_axes.py ...

========================== 3 passed in 3.78 seconds
===========================

Note, there are 3 tests because of the 3 extensions that are checked by the
image_comparison decorator.


> 3) Also on master, I get errors with tests.py.  Example:
>
> python tests.py lib/matplotlib/tests/test_axes.py
>
> [snip]
>
>
>
This will not work at the moment. tests.py continues to use nose, so it
will not run pytest-based files. The list of files that only work with nose
is very short right now. As soon as my other PR is merged, I will open a PR
that should make this work again (there are conflicts).

-- 
Elliott



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

From bussonniermatthias at gmail.com  Sat Jan 28 20:40:10 2017
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Sat, 28 Jan 2017 17:40:10 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAE-UAvQ-tnHVq-oNfAv4H-Ft5v=6ocw73yLPoy7xKHQ7GG+y5w@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
 <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
 <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>
 <CAE-UAvQ-tnHVq-oNfAv4H-Ft5v=6ocw73yLPoy7xKHQ7GG+y5w@mail.gmail.com>
Message-ID: <CANJQusU2Ti4BGQJGGScNG5-QAWrRL3grQa5bZThNC8Xqob=KCw@mail.gmail.com>

> numpy, scipy, skimage, pandas, sklearn, sympy, ipython all follow this standard.

We do our best in IPython to try to "catch up" on standard, and right
now we are not the best example.
Like matplotlib our test harness is relatively complex (for different
reasons than matplotlib). But we are doing
our best to push things forward. Migrating to PyTest is one of the
things we hope to one day achieve (or already start).

"The bit split" helped, but in 2014 out tests layout was kind of horrible.

I am not involved enough in matplotlib to tell you whether you should
(or not) decide to change (that's your choice, and only core dev can
likely correctly weight on cost/benefits balance), but IMHO, and the
experience I have:

  - With IPython : non traditional package layout and test harness
make it difficult for new/occasional contributors.
     - E.g in IPython a couple of time per year, we have people
running `nosetest` from the root of the directory.
     - we have a specific guard against running iptest from source directory.
     - contributing to our test suite is harder

That does not seem much, but integrating something small through time
can lead to quite a lot.

  - You may not realise it but a lot of people when wondering how to
do things will look up to "core" packages.
     - They either will not understand, potentially giving up.
     - Or will replicate a complex setup

That add to the myth that "python packaging is hard", and I think that
weighting on the overall community impact is important.
I definitely feel a "layout context switching" when working on
matplotlib. Test layout is not the only one, but it definitively
interfere with my editor which smart search on nearby files.

Catching up on "Standard" does not mean either changing all at once.
AFAIU you do that for pep8 where the number of violation can only go down,
so you can perfectly start a policy:
   - new test need to be next to thing they test.

Sidenote: I don't see why a testing submodule should not be importable.
Don't you have utility function that would be useful for others ?
Wouldn't it bother you that only a test submodule can be imported but
only by testing tools ?

I'm going to guess "just post 2.0" might not be a good time to
actually shuffle things around, but looking at "what would it break"
(beyond people habits) can be a way to see a couple of assumptions
that are not supposed to be here*, and lay out the foundation to
moving things around if one day you decide to.

Thanks !
-- 
Matthias

[*] source: PyCon 2014, I deleted the test suite. IPython was refusing
to start.




On Sat, Jan 28, 2017 at 10:27 AM, Nelle Varoquaux
<nelle.varoquaux at gmail.com> wrote:
>>> Actually, it is really a pain that Matplotlib doesn't follow python
>>> standards for any contributors that contributes to any other python
>>> packages.
>>
>>
>> very true, but...
>>
>> 1) If we were starting from scratcth that would be one thing, but a lot of
>> thrash jsut to meet a "standard" is probably not worth it.
>
>
> The benefits of following standards for maintainability has been
> demonstrated over and over.
>
>>
>> 2) I don't know how standardized this concept is, and personally, I don''t
>> like it (if I understand it correctly, anyway)
>
>
> It is extremely standard. Matplotlib is not the only project not following
> standards, but it's probably in the 1% of projects not following standards.
> More importantly, it is how we (the community) teach how to organize
> packages and tests.
>
> numpy, scipy, skimage, pandas, sklearn, sympy, ipython all follow this
> standard.
> The only other mainstream scientific python package that may not entirely
> follow this convention is cython.
>
>>
>> I prefer that ALL tests be in one single directory tree, ideally with that
>> tree mtaching the package / subpacakge/module tree of the project, ie:
>
>
> The whole point of convention is to avoid  this.
>
>>
>>
>> project
>>     __init__.py
>>     proj_mod1.py
>>     sub_package1
>>       __init__.py
>>       sub_mod1.py
>>     ...
>>
>> test_project
>>     test_proj_mod1.py
>>     test_sub_package1
>>         test_sub_mod1.py
>>
>> i.e. one test file for each module file.
>>
>> With this method, it would not be hard to find the tests that correspond
>> to a particular python module.
>>
>> I'm ambivalent about whether the test files should be importable packages,
>> and I think there is a lot to be said for keeping the test code outside the
>> installable package tree altogether, but I definitely don't like them all
>> intermingled.
>>
>> though I still don't advocate a lot of churn for this...
>>
>> -CHB
>>
>> --
>>
>> 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
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>

From jks at iki.fi  Sun Jan 29 03:14:23 2017
From: jks at iki.fi (=?iso-8859-1?Q?Jouni_K=2E_Sepp=E4nen?=)
Date: Sun, 29 Jan 2017 10:14:23 +0200
Subject: [Matplotlib-devel] user mailing list policy
References: <CAA48SF-AVVhoDUhAcLfZtdaM2my7RZ3J0kdNiYXLT_Lh7hxpTQ@mail.gmail.com>
 <8fd06482-89f7-1413-559d-9aeed6225daa@hawaii.edu>
 <CAA48SF_eD521w-2nAVsEW4f6ryPDyHWdWq-O_uwgj5qKMta+-w@mail.gmail.com>
Message-ID: <m2tw8i471c.fsf@jks.iki.fi>

Thomas Caswell <tcaswell at gmail.com> writes:

> The bounce users get looks like:
>
[...]
>
> which does not include information on _how_to subscribe.  My random-walk
> through the configuration pages on mailman are failing to sort out how to
> customize this message.

I don't think this can be configured through the web interface. This
text comes from the postheld.txt template which (AFAIU) can be changed
by creating a new file /var/lib/mailman/lists/<listname>/en/postheld.txt
with custom contents. The original file is /etc/mailman/en/postheld.txt
or possibly /var/lib/mailman/templates/en/postheld.txt.


-- 
Jouni K. Sepp?nen
http://www.iki.fi/jks


From antony.lee at berkeley.edu  Sun Jan 29 04:44:02 2017
From: antony.lee at berkeley.edu (Antony Lee)
Date: Sun, 29 Jan 2017 01:44:02 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CANJQusU2Ti4BGQJGGScNG5-QAWrRL3grQa5bZThNC8Xqob=KCw@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
 <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
 <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>
 <CAE-UAvQ-tnHVq-oNfAv4H-Ft5v=6ocw73yLPoy7xKHQ7GG+y5w@mail.gmail.com>
 <CANJQusU2Ti4BGQJGGScNG5-QAWrRL3grQa5bZThNC8Xqob=KCw@mail.gmail.com>
Message-ID: <CAGRr6BHXK6k=WjbXi2JuPXangPeyhw0huyzo-E3eGBQU8Nyrrw@mail.gmail.com>

It looks like there are two issues at hand here.

- Should there be one test module per real module?  My opinion is that the
answer is generally yes, but there are cases where this would be awkward,
so we shouldn't make it a hard rule.  For example, `test_pickle.py` tests
the picklability of various objects, from simple ones to entire figures.
Of course, each of the tests could be moved to the test module
corresponding to the module where the object is defined, but I doubt this
would make things clearer.

- Should there be a `matplotlib.tests` package containing all the tests
(possibly replicating the matplotlib hierarchy) or one `.tests` subpackage
per package?  Let's realize that matplotlib has a very flat hierarchy
compared to the other projects Nelle mentioned.  Basically, the change
would entail moving
    - test_axes to axes/tests
    - test_backend_* to backends/tests
    - test_cbook to cbook/tests
    - test_triangulation to tri/tests
    - test_style to style/tests
The other subpackages are projections and sphinxext, for which there does
not appear to be a dedicated test module.  Frankly, which such a small
number of exceptions, I feel it would be more confusing to move the
corresponding tests out to their own subpackage.  The situation is not the
same as in numpy, scipy, skimage, pandas, sklearn and sympy, which (I just
checked) all have more subpackages (i.e. folders) than submodules (i.e.
files) directly under the main package.  (IPython has more direct
submodules, but many of them seem to be just shims left over from the big
split).  For these projects, subpackages provide a clear partitioning
between parts of the code, and it is thus natural to split the tests in the
same manner.

Antony

2017-01-28 17:40 GMT-08:00 Matthias Bussonnier <bussonniermatthias at gmail.com
>:

> > numpy, scipy, skimage, pandas, sklearn, sympy, ipython all follow this
> standard.
>
> We do our best in IPython to try to "catch up" on standard, and right
> now we are not the best example.
> Like matplotlib our test harness is relatively complex (for different
> reasons than matplotlib). But we are doing
> our best to push things forward. Migrating to PyTest is one of the
> things we hope to one day achieve (or already start).
>
> "The bit split" helped, but in 2014 out tests layout was kind of horrible.
>
> I am not involved enough in matplotlib to tell you whether you should
> (or not) decide to change (that's your choice, and only core dev can
> likely correctly weight on cost/benefits balance), but IMHO, and the
> experience I have:
>
>   - With IPython : non traditional package layout and test harness
> make it difficult for new/occasional contributors.
>      - E.g in IPython a couple of time per year, we have people
> running `nosetest` from the root of the directory.
>      - we have a specific guard against running iptest from source
> directory.
>      - contributing to our test suite is harder
>
> That does not seem much, but integrating something small through time
> can lead to quite a lot.
>
>   - You may not realise it but a lot of people when wondering how to
> do things will look up to "core" packages.
>      - They either will not understand, potentially giving up.
>      - Or will replicate a complex setup
>
> That add to the myth that "python packaging is hard", and I think that
> weighting on the overall community impact is important.
> I definitely feel a "layout context switching" when working on
> matplotlib. Test layout is not the only one, but it definitively
> interfere with my editor which smart search on nearby files.
>
> Catching up on "Standard" does not mean either changing all at once.
> AFAIU you do that for pep8 where the number of violation can only go down,
> so you can perfectly start a policy:
>    - new test need to be next to thing they test.
>
> Sidenote: I don't see why a testing submodule should not be importable.
> Don't you have utility function that would be useful for others ?
> Wouldn't it bother you that only a test submodule can be imported but
> only by testing tools ?
>
> I'm going to guess "just post 2.0" might not be a good time to
> actually shuffle things around, but looking at "what would it break"
> (beyond people habits) can be a way to see a couple of assumptions
> that are not supposed to be here*, and lay out the foundation to
> moving things around if one day you decide to.
>
> Thanks !
> --
> Matthias
>
> [*] source: PyCon 2014, I deleted the test suite. IPython was refusing
> to start.
>
>
>
>
> On Sat, Jan 28, 2017 at 10:27 AM, Nelle Varoquaux
> <nelle.varoquaux at gmail.com> wrote:
> >>> Actually, it is really a pain that Matplotlib doesn't follow python
> >>> standards for any contributors that contributes to any other python
> >>> packages.
> >>
> >>
> >> very true, but...
> >>
> >> 1) If we were starting from scratcth that would be one thing, but a lot
> of
> >> thrash jsut to meet a "standard" is probably not worth it.
> >
> >
> > The benefits of following standards for maintainability has been
> > demonstrated over and over.
> >
> >>
> >> 2) I don't know how standardized this concept is, and personally, I
> don''t
> >> like it (if I understand it correctly, anyway)
> >
> >
> > It is extremely standard. Matplotlib is not the only project not
> following
> > standards, but it's probably in the 1% of projects not following
> standards.
> > More importantly, it is how we (the community) teach how to organize
> > packages and tests.
> >
> > numpy, scipy, skimage, pandas, sklearn, sympy, ipython all follow this
> > standard.
> > The only other mainstream scientific python package that may not entirely
> > follow this convention is cython.
> >
> >>
> >> I prefer that ALL tests be in one single directory tree, ideally with
> that
> >> tree mtaching the package / subpacakge/module tree of the project, ie:
> >
> >
> > The whole point of convention is to avoid  this.
> >
> >>
> >>
> >> project
> >>     __init__.py
> >>     proj_mod1.py
> >>     sub_package1
> >>       __init__.py
> >>       sub_mod1.py
> >>     ...
> >>
> >> test_project
> >>     test_proj_mod1.py
> >>     test_sub_package1
> >>         test_sub_mod1.py
> >>
> >> i.e. one test file for each module file.
> >>
> >> With this method, it would not be hard to find the tests that correspond
> >> to a particular python module.
> >>
> >> I'm ambivalent about whether the test files should be importable
> packages,
> >> and I think there is a lot to be said for keeping the test code outside
> the
> >> installable package tree altogether, but I definitely don't like them
> all
> >> intermingled.
> >>
> >> though I still don't advocate a lot of churn for this...
> >>
> >> -CHB
> >>
> >> --
> >>
> >> 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
> >
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170129/7a17f3fb/attachment-0001.html>

From njs at pobox.com  Sun Jan 29 05:46:49 2017
From: njs at pobox.com (Nathaniel Smith)
Date: Sun, 29 Jan 2017 02:46:49 -0800
Subject: [Matplotlib-devel] Reorganising the test files?
In-Reply-To: <CAGRr6BHXK6k=WjbXi2JuPXangPeyhw0huyzo-E3eGBQU8Nyrrw@mail.gmail.com>
References: <CAE-UAvQF+JdpHF7mpoK5ug1SR0q7mN8Ta3uG6GmM92rkKAJmTQ@mail.gmail.com>
 <CAA48SF9=PJutuGZkY453e1932NGbDFZeePxL62kQ813LWVy7FA@mail.gmail.com>
 <CAE-UAvRonq5AVV+YL1Jp0vhV5ReVDkOG4wcFoqa-kHge7ee35w@mail.gmail.com>
 <CALGmxELpkr6YVMp6dWSsh4C3=0YAgYLBQ_ynyse8e1+qYtJ0dw@mail.gmail.com>
 <CAE-UAvQ-tnHVq-oNfAv4H-Ft5v=6ocw73yLPoy7xKHQ7GG+y5w@mail.gmail.com>
 <CANJQusU2Ti4BGQJGGScNG5-QAWrRL3grQa5bZThNC8Xqob=KCw@mail.gmail.com>
 <CAGRr6BHXK6k=WjbXi2JuPXangPeyhw0huyzo-E3eGBQU8Nyrrw@mail.gmail.com>
Message-ID: <CAPJVwB=ELX-HZycfrSUHxZ2kaJOrBYuxD5pNf-nNwo0AnUPyqg@mail.gmail.com>

On Jan 29, 2017 1:44 AM, "Antony Lee" <antony.lee at berkeley.edu> wrote:

It looks like there are two issues at hand here.

- Should there be one test module per real module?  My opinion is that the
answer is generally yes, but there are cases where this would be awkward,
so we shouldn't make it a hard rule.  For example, `test_pickle.py` tests
the picklability of various objects, from simple ones to entire figures.
Of course, each of the tests could be moved to the test module
corresponding to the module where the object is defined, but I doubt this
would make things clearer.

- Should there be a `matplotlib.tests` package containing all the tests
(possibly replicating the matplotlib hierarchy) or one `.tests` subpackage
per package?  Let's realize that matplotlib has a very flat hierarchy
compared to the other projects Nelle mentioned.  Basically, the change
would entail moving
    - test_axes to axes/tests
    - test_backend_* to backends/tests
    - test_cbook to cbook/tests
    - test_triangulation to tri/tests
    - test_style to style/tests


Another thing to consider here is that some pytest features are biased
towards layouts where all tests live in a single hierarchy. If you define a
custom fixture in a conftest.py file, that fixture is available to tests in
the directory and subdirectories, but not siblings. Maybe matplotlib
doesn't use these features though, or maybe there's some way around this in
pytest (if you figure it out I'd love to know! pytest is very, uh, "feature
rich", and I haven't looked into this in depth, it's just something I ran
into).

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

From tcaswell at gmail.com  Mon Jan 30 16:08:04 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 30 Jan 2017 21:08:04 +0000
Subject: [Matplotlib-devel] 2016-01-30 phone call notes
Message-ID: <CAA48SF8cMttTkaAx-3C7zRamM_nLojH7k03z7FRnD_Xeg8kRWg@mail.gmail.com>

In attendance were my self, Nelle Varoquaux, and Ryan May.

 - went over 2.0.1 release critical bugs
  - most have patches
  - imshow needs c level debugging :(
  - #7991 needs attention
  - the rest need minor fixes updates

 - discussed pytest convsion
   - issues with conftests.py
   - issues with pgf not failing when we expect
     - sorted it out, bugs in test framework, have been 'default' style
sense #6757

 - Ryan will update codecov to check that all tests are run
 - Ryan's talk went well
 - Discussed automating wheel building
 - plan for 2.0.1 next weekend (2017-02-04)

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