From tune.kamae at gmail.com Mon Oct 2 04:20:38 2017 From: tune.kamae at gmail.com (tune.kamae at gmail.com) Date: Mon, 2 Oct 2017 17:20:38 +0900 Subject: [Matplotlib-devel] feature request In-Reply-To: References: <82B4C2EE-90F3-4E14-A4AF-7DED20A30DE6@uvic.ca>

Message-ID: <66e201d33b57$55de4560$019ad020$@gmail.com> Dear Developers, I have been developing sound-guided matplotlib to assist blind students to trace curves on the 2D plots. I figured out to implement what I want for plotted curves but still struggling to enable tracing the x and y axes. The sample plot I am working with is Axes.pickable. What I cannot figure out is to get majoraxislabels when a finger-touch event occurs within a fixed distance, eg. Picker=5 of x-axis. First I have to figure out if the event is onaxes. I am using what I found in Matplotlib tutorials. How should I modified the codes below? def onpick(event): thisline = event.artist xdata = thisline.get_xdata() ydata = thisline.get_ydata() ind = event.ind points = tuple(zip(xdata[ind], ydata[ind])) print('onpick points:', points) if onpick: print ("Data points picked") winsound.Beep(Freq,Dur) Thank you for the assistance, Tune Kamae -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Tue Oct 3 04:44:37 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 03 Oct 2017 08:44:37 +0000 Subject: [Matplotlib-devel] v2.1 tagged Message-ID: Folks, Just pushed the v2.1.0 tag. There is still a bit of work to be done on docs. Will do wider announcement once that is done and binaries are available. Moved all of the un-closed issues to the 2.2 milestone. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From tune.kamae at gmail.com Tue Oct 3 05:13:54 2017 From: tune.kamae at gmail.com (tune.kamae at gmail.com) Date: Tue, 3 Oct 2017 18:13:54 +0900 Subject: [Matplotlib-devel] v2.1 tagged In-Reply-To: References: Message-ID: <33d401d33c27$f0cdda10$d2698e30$@gmail.com> Tom Thank you for the email. Through many rounds of trial-and-error I managed to do more than half of my immediate goal. If done, I will share with other devlopers. Tune Kamae From: Matplotlib-devel [mailto:matplotlib-devel-bounces+tune.kamae=gmail.com at python.org] On Behalf Of Thomas Caswell Sent: Tuesday, October 3, 2017 5:45 PM To: matplotlib development list Subject: [Matplotlib-devel] v2.1 tagged Folks, Just pushed the v2.1.0 tag. There is still a bit of work to be done on docs. Will do wider announcement once that is done and binaries are available. Moved all of the un-closed issues to the 2.2 milestone. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniele at grinta.net Tue Oct 3 17:13:56 2017 From: daniele at grinta.net (Daniele Nicolodi) Date: Tue, 3 Oct 2017 15:13:56 -0600 Subject: [Matplotlib-devel] [Matplotlib-users] How to make \mathdefault{} the default? In-Reply-To: References: Message-ID: On 10/3/17 2:59 PM, Daniele Nicolodi wrote: > Hello, > > when adding LaTeX symbols to labels on my figures, most often I use > \mathdefault{} to make Matplotlib use the same fond for the regular text > and for the LaTeX part. Is there a way to configure Matplotlib to use > the regular text by default? Looking at the configuration file I > haven't found anything hinting to it. After staring a bit more at the example configuration file, I can answer my own question. This does the trick: matplotlib.rcParams['mathtext.fontset'] = 'custom' I'm a bit worried by the note next to this setting in the example configuration file, though: # The following settings allow you to select the fonts in math mode. # They map from a TeX font name to a fontconfig font pattern. # These settings are only used if mathtext.fontset is 'custom'. # Note that this "custom" mode is unsupported and may go away in the # future. Why is it unsupported? I find this functionality very neat. Thanks. Cheers, Daniele From tcaswell at gmail.com Tue Oct 3 13:07:05 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 03 Oct 2017 17:07:05 +0000 Subject: [Matplotlib-devel] LIGO nobel prize Message-ID: Folks, This years Nobel prize in physics was awarded for the work done by LIGO/VIRGO [1] project. We know that Matplotlib is used for some of the LIGO analysis (see the notebooks published at https://losc.ligo.org/tutorials/ ). Just a reminder that our work on Matplotlib does have an impact! Tom [1] https://www.nobelprize.org/nobel_prizes/physics/laureates/2017/press.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Tue Oct 3 21:02:54 2017 From: ben.v.root at gmail.com (Benjamin Root) Date: Tue, 3 Oct 2017 21:02:54 -0400 Subject: [Matplotlib-devel] LIGO nobel prize In-Reply-To: References: Message-ID: Yeah, I tried convincing my wife that I very indirectly won a Nobel Prize... She asked if I get any money. I told her no. She congratulated me on my no-money Nobel prize. On Tue, Oct 3, 2017 at 1:07 PM, Thomas Caswell wrote: > Folks, > > This years Nobel prize in physics was awarded for the work done by > LIGO/VIRGO [1] project. We know that Matplotlib is used for some of the > LIGO analysis (see the notebooks published at https://losc.ligo.org/ > tutorials/ ). > > Just a reminder that our work on Matplotlib does have an impact! > > Tom > > [1] https://www.nobelprize.org/nobel_prizes/physics/ > laureates/2017/press.html > > _______________________________________________ > 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: From tcaswell at gmail.com Sat Oct 7 19:30:11 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 07 Oct 2017 23:30:11 +0000 Subject: [Matplotlib-devel] [ANN] Matplotlib 2.1 released Message-ID: We are happy to announce the release of Matplotlib 2.1. This is the second minor release in the Matplotlib 2.x series and the first release with major new features since 1.5. This release contains approximately 2 years worth of work by 275 contributors across over 950 pull requests. Highlights from this release include: - support for string categorical values - export of animations to interactive javascript widgets - major overhaul of polar plots - reproducible output for ps/eps, pdf, and svg backends - performance improvements in drawing lines and images - GUIs show a busy cursor while rendering the plot along with many other enhancements and bug fixes. The gallery, examples, and tutorials have been overhauled and consolidated: Examples: http://matplotlib.org/gallery/index.html Tutorials: http://matplotlib.org/tutorials/index.html A big thank you to everyone who contributed to this release! Wheels are available on pypi for win/mac/manylinux and for conda via conda-forge. Full whats new: http://matplotlib.org/users/whats_new.html#new-in-matplotlib-2-1 Full API changes: http://matplotlib.org/api/api_changes.html#api-changes-in-2-1-0 github stats: http://matplotlib.org/users/github_stats.html Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sun Oct 8 15:26:08 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Sun, 08 Oct 2017 19:26:08 +0000 Subject: [Matplotlib-devel] PR review / new contributors Message-ID: Folks, Between 2.1.0 be released and my interview with NumFOCUS [1] we will hopefully be getting an influx of new contributors. We should always be kind and respectful in pull requests (even if the person you are talking to 'can take it', potential contributors will read it and may be turned away), but please be extra patient with new contributors. I think everyone with commit rights can see "new contributor" next to the users name in the GH UI. Remember that first contribution to a big project can be intimidating for many reasons, they may be simultaneously learning git, github, python, and the conventions of Matplotlib in addition to asking their work to be publicly judged by strangers! At least for my self, my first PR to Matplotlib was to change a 4 to a 7 [2] and it still took me most of an afternoon to work up the nerve to open the PR. For documentation only changes please use the threshold "Is it better than in was?" and avoid copy-editing-via-github comments. Tom [1] https://www.numfocus.org/blog/matplotlib-lead-developer-explains-why-he-cant-fix-the-docs-but-you-can/ [2] https://github.com/matplotlib/matplotlib/pull/1062 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat Oct 14 17:56:30 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 14 Oct 2017 21:56:30 +0000 Subject: [Matplotlib-devel] release schedule Message-ID: Folks, Re-addressing the long-term release schedule first discussed in May 2016 [1] (which we are now about a year behind on). 2018-01/02 : 2.2 LTS - this will be the LTS release and get patch level fixes until 2020 2018-07 : 3.0 - first release which is python 3 only. The level of backporting to 2.2 will depend on if someone champions it. I am personally only willing to do critical (failure to import and segfault fixes) backports. If functionality bug fixes are important to people, I am happy to delegate all responsibility of the 2.2.x series. For 3.0, I would like to start with python 3.6+ only. The release schedule for 3.7 is 2018-06 so that would return us to, what I understand used to be the standard, support for the last 2 versions of python. Further, both python 3.4 and 3.5 already have no planned future releases. Tom [1] https://mail.python.org/pipermail/matplotlib-devel/2016-May/000374.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Mon Oct 23 11:26:06 2017 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 23 Oct 2017 15:26:06 +0000 Subject: [Matplotlib-devel] Agenda for 2017-10-23 call Message-ID: Folks, Trying to plan ahead today! This is what I would like to talk about on the call (with the goal of getting 2.1.1 tagged this week). Sorry for leaking a bit of my internal state with the formatting (it looks nice with org-mode in emacs). Tom * call agenda ** REV [[mpl:9262]] Minor doc markup fixes. - State "WAIT" from "REV" [2017-10-22 Sun 20:28] ** REV [[mpl:9257]] FIX: segfault on truncated png *** REV [[mpl:9256]] reading truncated png can segfault python ** REV [[mpl:9534]] Fix webagg *** REV [[mpl:9380]] Cannot import pyplot. NameError: 'FigureManagerWebAgg' is not defined ** REV [[mpl:9477]] In LogTransform, clip after log, not before. *** REV [[mpl:9288]] Histograms disappear with logarithmic y-axis *** REV [[mpl:9457]] ax.fill_between broken for log scale and values below zero ** REV [[mpl:9324]] Allow kwarg handles and labels figure.legend and make doc for kwargs the same *** REV [[mpl:9320]] 2.1 figure.legend broken ** REV [[mpl:9304]] Fedora build patches *** WAIT [[mpl:6538]] On armv7hl, some get_cursor_data calls return 0 instead of None. - State "WAIT" from "REV" [2017-10-22 Sun 17:39] *** REV [[mpl:7158]] Arrays are not equal in 2.0.0b4 testsuite on Fedora rawhide/aarch64 (ARM v8 64bit) ** REV [[mpl:9359]] Keep track of axes in interactive navigation. *** REV [[mpl:9358]] zoom/pan stack bug in 2.1.0 ** REV [[mpl:9389]] Assign event to later Axes if zorders are tied. *** REV [[mpl:9388]] Mouse events have incorrect inaxes/data properties when axes overlap (matplotlib 2.1.0) ** [0/5] categoricals *** REV [[mpl:9336]] Integer Categorical Values Not Getting Mapped Correctly *** REV [[mpl:9340]] bugfix/test for #9336 integer overwrite in categorical *** REV [[mpl:9350]] Data types not preserved in categoricals *** REV [[mpl:9318]] Don't sort categorical keys. *** REV [[mpl:9494]] Categorical not hitting update path on fill_between ** REV [[mpl:8122]] keyword labelrotation is not recognized ** REV [[mpl:8947]] Different result, slower runtime of heatmap between 2.0.0 and 2.0.1 ** REV [[mpl:9429]] Undefined name `baseline`? ** REV [[mpl:9436]] Instance of 'TextBox' has no 'observers' member? ** REV [[mpl:9521]] fix xkcd context ** REV [[mpl:8069]] backend_driver.py overhaul *** REV [[mpl:9284]] Restore something like backend_driver -------------- next part -------------- An HTML attachment was scrubbed... URL: