Mailman 3 December 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

v2.0.0rc1 is tagged
by Thomas Caswell Jan. 7, 2017

Jan. 7, 2017

Folks, I have just finished tagging rc1! https://github.com/matplotlib/matplotlib/releases/tag/v2.0.0rc1 Holding off on uploading to pypi and announcing to the user lists until wheels are ready for the three big platform. The wheels have been started on conda-forge. Thanks again to everyone who has worked on this. We are definitely converging! Tom

3 4

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

jupyter code of conduct
by Thomas Caswell Dec. 29, 2016

Dec. 29, 2016

Folks, Jupyter is working on finalizing a code of conduct: https://github.com/jupyter/governance/pull/23 I will likely suggest we adopt the same document (after they have some time to work out the kinks) in 6-9mo time frame. Please have a look at it and bring up any concerns now so they can be worked through with the jupyter folks in the loop. Tom

1 0

[REL] matplotlib 2.0.0rc2
by Thomas Caswell Dec. 21, 2016

Dec. 21, 2016

Folks, We are happy to announce matplotlib v2.0.0rc2 ! Please re-distribute this widely. This is the final planned release candidate for the long awaited mpl v2.0 release. For the full details of what is new please see http://matplotlib.org/2.0.0rc2/users/whats_new.html Some of the highlights: - new default style (see http://matplotlib.org/2.0.0rc2/users/dflt_style_changes.html ) - new default color map (viridis) - default font includes most western alphabets - performance improvements in text and image rendering - many bug fixes and documentation improvements - many new rcparams Please help us by testing the release candidate! We would like to hear about any uses where the new defaults are significantly worse, any changes we failed to documents, or (as always) any bugs and regressions. To make this easy we have both wheels and conda packages for mac, linux and windows. You can install pre-releases via pip: pip install --pre matplotlib or via conda: conda update --all -c conda-forge conda install -c conda-forge/label/rc -c conda-forge matplotlib For more details see http://matplotlib.org/style_changes.html . Please report any issues to https://github.com/matplotlib/matplotlib/issues or matplotlib-users at python.org . The target for v2.0 final is early Jan 2017. This release is the work of over 200 individual code contributors and many more who took part in the discussions, tested the pre-releases, and reported bug reports. Thank you to everyone who contributed! Tom

2 2

need wxPython reviewers for PR
by Eric Firing Dec. 21, 2016

Dec. 21, 2016

We have a PR to fix a problem in backend_wx.py, and as far as I know most of us who have been reviewing PRs recently are not WX users. Hence this call for assistance: if you use the wxagg backend, and can build matplotlib from source, please try out the patch and review it: https://github.com/matplotlib/matplotlib/pull/7652 Thanks. Eric

1 0

v2.0.0rc2
by Thomas Caswell Dec. 18, 2016

Dec. 18, 2016

Folks, rc2 has been tagged an the various CI tools are spinning to build the binaries. I will upload to pypi and announce widely once they are all done. Tom

1 0

v2.0 release plans
by Thomas Caswell Dec. 15, 2016

Dec. 15, 2016

Folks, We have heard remarkably little back about rc1 (which is either a very good or very bad sign). I propose we do an rc2 this weekend and in addition to announcing to our lists (plus twitter) we also hit the pandas, jupyter, numpy, and scipy mailing lists. I would target a final release the first week of Jan 2017. Seems like a good way to start the new year :) Thoughts? Tom

2 1

v2.2 milestone
by Thomas Caswell Dec. 11, 2016

Dec. 11, 2016

Folks, As we are approaching the 2.0 release, we need to start thinking about the 2.1. Previously, I have advocated for holding 2.1 for traitlets and the GUI refactor, however given the time delays, this needs to be re-addressed. There is already a tremendous amount of work sitting on master that we need to get out to the world (for example story645's work on plotting against string-categoricals). To start organizing for this I have created a 2.2 milestone, please move any issues that you do not think should block 2.1 to 2.2. Things that you can not be done with out a major API break, please move to the 3.0 milestone. I will commit to reviewing the GUI overhaul (once 2.0 final is out) so that should stay in 2.1 (sorry oceanwolf and fariza!). There should probably be a wider discussion / rethink of how we use milestones/projects, but I think we should defer that until github's current rash of UI / PM changes settles down. Tom

1 0