Mailman 3 November 2016 - Matplotlib-devel

Confusion about draw_artist
by Matthew Brett April 1, 2017

April 1, 2017

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

2 5

our tests
by Eric Firing Jan. 28, 2017

Jan. 28, 2017

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 =============================================== 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/py/mpl/matplotlib/lib/matplotlib/tests/test_axes.py::test_hist_steplog (no name '/Users/efiring/work/programs/py/mpl/matplotlib/lib/matplotlib/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

4 3

matplotlib versus Matplotlib?
by Nelle Varoquaux Jan. 5, 2017

Jan. 5, 2017

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. Once we formally agree, I'll update #7387 correspondingly. N

3 2

Fwd: [matplotlib-devel] The GitHub labels
by Paul Hobson Nov. 3, 2016

Nov. 3, 2016

Here's Nelle's email re: the current usage of GH labels. ---------- Forwarded message ---------- From: Nelle Varoquaux <nelle.varoquaux(a)gmail.com> Date: Sat, Oct 29, 2016 at 2:45 PM Subject: [matplotlib-devel] The GitHub labels To: "matplotlib-devel(a)lists.sourceforge.net" < matplotlib-devel(a)lists.sourceforge.net> Hi team, We've been discussing at several occasions of cleaning up our GitHub labels, and merging some. In order to guide the discussion of which labels to keep and to move, I've analysed a bit what where the labels we were using. Attached is a plot of the number of issues (including PRs) open and closed for each labels. Maybe we have too many labels? Most of them don't seem actively used. For example, py3k seem to be used 4 times, only on closed tickets/PR. I've done a similar analysis on scikit-image, scikit-learn and ipython. Some labels seem to be consistently used quite highly across all projects: the 3 difficulty levels, bug, ENH, DOC. I'm playing a bit with the github API this afternoon, so if any other statistics is useful, just let me know. Cheers, N ------------------------------------------------------------ ------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

2 1