From anntzer.lee at gmail.com Fri Apr 2 09:09:14 2021 From: anntzer.lee at gmail.com (Antony Lee) Date: Fri, 2 Apr 2021 15:09:14 +0200 Subject: [Matplotlib-devel] ANN: mplcairo 0.4 release Message-ID: Dear all, I am pleased to announce the release of mplcairo 0.4. mplcairo is a Matplotlib backend based on the well-known cairo library, supporting output to both raster (including interactively) and vector formats. In other words, it provides the functionality of Matplotlib's {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. Per Matplotlib's standard API, the backend can be selected by calling matplotlib.use("module://mplcairo.qt") or setting your MPLBACKEND environment variable to `module://mplcairo.qt` for Qt5, and similarly for other toolkits. mplcairo 0.4 adds support for Matplotlib 3.4, support for retrieving underlying cairo contexts, as well as the usual bugfixes over 0.3. Enjoy, Antony Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: From antony.lee at institutoptique.fr Fri Apr 2 09:09:51 2021 From: antony.lee at institutoptique.fr (Antony Lee) Date: Fri, 2 Apr 2021 15:09:51 +0200 Subject: [Matplotlib-devel] mpl-3.4 vs. mplcairo? In-Reply-To: References: Message-ID: mplcairo 0.4 is out now, and should fix the problem. Antony On Mon, Mar 29, 2021 at 4:59 PM Neal Becker wrote: > Thanks, looking forward to it! > > On Mon, Mar 29, 2021 at 10:38 AM Antony Lee > wrote: > > > > I need to make a new release for mplcairo. Will try to get it out in > the coming days... > > Antony > > > > On Mon, Mar 29, 2021 at 2:11 PM Neal Becker wrote: > >> > >> Just updated out-of-date python modules including mpl. Now if I try a > >> simple plot I get: > >> -------------- > >> In [2]: Traceback (most recent call last): > >> File > "/home/nbecker/.local/lib/python3.9/site-packages/mplcairo/qt.py", > >> line 12, in paintEvent > >> if self._update_dpi(): > >> AttributeError: 'FigureCanvasQTCairo' object has no attribute > '_update_dpi' > >> ----------- > >> > >> if using backend: module://mplcairo.qt, which is my default. > >> Removing this from matplotlibrc the plot works fine. > >> > >> fedora 33 > >> python 3.9.2 > >> mplcairo 0.3.post38+g3bcf15c > >> matplotlib 3.4.0 > >> PyQt5 5.15.4 > >> PyQt5-Qt5 5.15.2 > >> > >> -- > >> Those who don't understand recursion are doomed to repeat it > >> _______________________________________________ > >> Matplotlib-devel mailing list > >> Matplotlib-devel at python.org > >> https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > -- > Those who don't understand recursion are doomed to repeat it > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndbecker2 at gmail.com Fri Apr 2 09:36:56 2021 From: ndbecker2 at gmail.com (Neal Becker) Date: Fri, 2 Apr 2021 09:36:56 -0400 Subject: [Matplotlib-devel] [Matplotlib-users] ANN: mplcairo 0.4 release In-Reply-To: References: Message-ID: Thanks, and confirm this fixes the issue. Hopefully mplcairo will be incorporated into mpl soon and such breakage will be avoided. On Fri, Apr 2, 2021 at 9:09 AM Antony Lee wrote: > > Dear all, > > I am pleased to announce the release of mplcairo 0.4. > > mplcairo is a Matplotlib backend based on the well-known cairo library, supporting output to both raster (including interactively) and vector formats. In other words, it provides the functionality of Matplotlib's {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. > > Per Matplotlib's standard API, the backend can be selected by calling > > matplotlib.use("module://mplcairo.qt") > > or setting your MPLBACKEND environment variable to `module://mplcairo.qt` for Qt5, and similarly for other toolkits. > > mplcairo 0.4 adds support for Matplotlib 3.4, support for retrieving underlying cairo contexts, as well as the usual bugfixes over 0.3. > > Enjoy, > > Antony Lee > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users at python.org > https://mail.python.org/mailman/listinfo/matplotlib-users -- Those who don't understand recursion are doomed to repeat it From tcaswell at gmail.com Fri Apr 2 20:00:51 2021 From: tcaswell at gmail.com (Thomas Caswell) Date: Fri, 2 Apr 2021 20:00:51 -0400 Subject: [Matplotlib-devel] Major refactor of Axes internals just merged Message-ID: Folks, We just merged a major refactor of how the Axes object stores its children [1]. Previously the children were stored across several lists by type and were sorted and merged at draw time (which is the source of the long standing bug [2]) whereas now there is a single list of children and back-compatibility shims to access the children by type. We expect this to be very good thing going forward, however in the short time we expect that there are going to be some unforeseen consequences due to this change. Because of this, we held of on merging this until after we got 3.4 release so that we have ~6 months of this being on the default branch before it is released. If you have any issues please reach out to us! It is unlikely that we will revert this change, but we will definitely extend and improve the shims as needed :) Thank you to Elliott for getting this work done! Tom [1] https://github.com/matplotlib/matplotlib/pull/18216 [2] https://github.com/matplotlib/matplotlib/issues/1622 -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Sat Apr 3 08:33:22 2021 From: pmhobson at gmail.com (Paul Hobson) Date: Sat, 3 Apr 2021 05:33:22 -0700 Subject: [Matplotlib-devel] Major refactor of Axes internals just merged In-Reply-To: References: Message-ID: Wow. Congrats on such a big milestone. Great work, Elliot. It's nuts seeing issue #1612 closed by #18216. I'm going to be cleaning up all of my repos at work (I found a new job) for the next week. So I'm sure all of my CI will let me know if any big issues come up. -Paul On Fri, Apr 2, 2021 at 5:01 PM Thomas Caswell wrote: > Folks, > > We just merged a major refactor of how the Axes object stores its children > [1]. Previously the children were stored across several lists by type and > were sorted and merged at draw time (which is the source of the long > standing bug [2]) whereas now there is a single list of children and > back-compatibility shims to access the children by type. > > We expect this to be very good thing going forward, however in the short > time we expect that there are going to be some unforeseen consequences due > to this change. Because of this, we held of on merging this until after we > got 3.4 release so that we have ~6 months of this being on the default > branch before it is released. > > If you have any issues please reach out to us! It is unlikely that we > will revert this change, but we will definitely extend and improve the > shims as needed :) > > Thank you to Elliott for getting this work done! > > Tom > > [1] https://github.com/matplotlib/matplotlib/pull/18216 > [2] https://github.com/matplotlib/matplotlib/issues/1622 > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > 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 pmhobson at gmail.com Sun Apr 25 23:17:13 2021 From: pmhobson at gmail.com (Paul Hobson) Date: Sun, 25 Apr 2021 20:17:13 -0700 Subject: [Matplotlib-devel] Query In-Reply-To: References: Message-ID: Aditya, Thanks for your interest in contributing to matplotlib. The top-level navigation bar at matplotlib's website (https://matplotlib.org) has a section titled "Contributing". Give that a read and let us know if you have any questions. Cheers, -Paul On Sun, Apr 25, 2021 at 8:00 PM Aditya Gupta wrote: > Dear sir, > > I Aditya Kumar Gupta , I am 1st year student at VIT and wanted to > contribute in your matplotlib project . Can you tell me how I can > contribute in this in a better way? > _______________________________________________ > 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: