[matplotlib-devel] ANN: Michael Droettboom, matplotlib lead developer

It is a great honor for me to announce that Michael Droettboom has agreed to take on the role of lead developer of matplotlib. Since Michael joined the project in 2007, he has been responsible for much of the code that brought matplotlib from being an excellent tool to a world class one. No one i

[matplotlib-devel] python3 release

I would like to discuss a timetable towards a python3 release (1.2 or 2.0). I'll throw this out there, and am happy to make modifications according to feedback Aug 20th : feature freeze and branch. bugfixes only going forward from this point Sept 15th: rc1 Oct 7th: rc2 Oct 15th release I kno

Re: [matplotlib-devel] [Matplotlib-users] ANN: mpltools 0.1 release

On Jul 13, 2012, at 7:57 AM, Benjamin Root wrote: > There was talk of this living in mlab or cbook. Is there a preference? > > > Neither. cbook is really meant more for the devs. Half of it is converter > functions that are probably completely unneeded now, while the other half is > the

Re: [matplotlib-devel] [Matplotlib-users] ANN: mpltools 0.1 release

On Wed, Jul 11, 2012 at 10:09 AM, Damon McDougall wrote: > > Well, as Ben said, that error fill plot is neato! It doesn't look too > complicated, either. I'd be more than happy to port it over later today > when I get bored of typing up my thesis. It'll probably only take me > about 30 minutes. >

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen wrote: > > When I tested on Mac OS X 10.6 I found that most unit tests were somehow > missing. Rather than try to diagnose the problem, I built a new binary > on 10.6, confirmed that it installed properly (with all unit tests) on > 10.6 and 10.7, th

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Jun 30, 2012, at 6:27 PM, Derek Homeier wrote: >> >> And none of the rules match this situation. RC2 will be :) > > What about the very last one? > > "For packages which missed the freeze only for reasons outside of the control > of the maintainers, we might be generous, but you need to c

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Jun 30, 2012, at 4:35 PM, Sandro Tosi wrote > > I've just reviewed the rules, and sadly realized the final mpl release > doesn't match them, so it's not worth asking for the exception. >> But I thought this is exactly when an *exception* is needed: when one doesn't match the rules. ---

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Jun 30, 2012, at 3:46 PM, Fernando Perez > Wow, I guess it paid off for us to stay up until 2am last night to get > IPython in... Our diff was enormous so we would have not been allowed > in at al. Whew :) Yeah, the diff Sandro is referring to for us is just between rc2 and final. Hope

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Jun 30, 2012, at 3:42 PM, Sandro Tosi wrote: > Hello John, > thanks for your effort! but... > > > ... we're already too late for the Debian freeze :( the diff is quite > small, so I'll ask for a freeze exception. Ouch. Sorry for the screwup. Good luck with the exception request: all tha

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez wrote: > On Sat, Jun 30, 2012 at 11:46 AM, John Hunter wrote: > > Well, looks like we better get moving then ;-) > > Go MPL! It would be great to have matching releases of IPython and > MPL, just in time for the Debian fre

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

al release and will put something out later today Sandro. On Thu, Jun 21, 2012 at 1:01 PM, Sandro Tosi wrote: > Hi all, > > On Sat, Jun 9, 2012 at 11:14 PM, John Hunter wrote: > > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > Is there a timeline for the f

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Wed, Jun 13, 2012 at 1:03 PM, Michael Droettboom wrote: > Is there a slight mix-up in the commits?  In the email John sent out, it had > commit f763cd11f50437568f8146b822ca8f25647cbb61 at the top of the log > (alternative baseline image for mathfont_stix_14.png). The tag is correct, the email

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboom wrote: > John: Do you know which git revision you made the tarballs from?  I'll go > ahead and tag it. https://github.com/matplotlib/matplotlib/commit/97f713098a71c70d70c46602794c2a0fd126b614 ---

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

gt; > Christoph > > > > On 6/9/2012 2:14 PM, John Hunter wrote: >> >> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site >> >> >> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ >> >> As soon as

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Sat, Jun 9, 2012 at 5:33 PM, John Hunter wrote: > On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing wrote: >> It also has backend_gdk.c (supposed to be a temporary copy of >> _backend_gdk.c) and some others like it. > > OK, I'll rebuild them super clean...  I know what w

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing wrote: > It also has backend_gdk.c (supposed to be a temporary copy of > _backend_gdk.c) and some others like it. OK, I'll rebuild them super clean... I know what went wrong.

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On Sat, Jun 9, 2012 at 5:11 PM, Eric Firing wrote: > On 06/09/2012 11:14 AM, John Hunter wrote: >> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > John, > > Is it intentional that the tarballs include doc/build? It isn't intentional and it looks

[matplotlib-devel] v1.1.1rc2 tarballs are up

I just uploaded the v1.1.1rc2 tarballs to the sourceforge site https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ As soon as we get binaries, I'll send out another call for testing on the users list. Russell and Christoph, easiest if you just upload the binaries direc

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On Thu, Jun 7, 2012 at 2:57 PM, Christoph Gohlke wrote: > Is there time for another release candidate? > > With the latest github branch on win-amd64-py2.7 I get both, a segfault > and a test failure in "matplotlib.tests.test_text.test_font_styles.test". If you are getting a segfault, is there o

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing wrote: > I did not see any replies to Sandro's reasonable question. > > Wasn't there at least a plan for a 1.1.x release soon? > > There are quite a few open pull requests for master--not many for > 1.1.x--but I don't know that any are blockers. There

[matplotlib-devel] Added Phil Elson as a developer

Phil Elson has been making pull requests for some time now on matters great and small, from hairy transformations improvements to minor docstring cleanups to GUI fixes. Given his prolific work, I thought it would be suitable to recognize him as a core matplotlib developer by adding him to the gith

Re: [matplotlib-devel] 1.1.1rc RuntimeError: underlying C/C++ object has been deleted

On Wed, Mar 28, 2012 at 1:22 PM, Neal Becker wrote: > > > import matplotlib > > matplotlib.use('pdf') > > > > It looks like you are inadvertently importing the qt library in a > headless > > script run. > > > > JDH > > Thanks, but should that cause a (scary looking) error? Or is there a real > p

Re: [matplotlib-devel] 1.1.1rc RuntimeError: underlying C/C++ object has been deleted

On Wed, Mar 28, 2012 at 8:57 AM, Neal Becker wrote: > qt-x11-4.8.0-7.fc16.x86_64 > PyQt4-4.8.6-1.fc16.x86_64 > > But interestingly, I'm not actually using the display in this script. I'm > using > pdfpages. At the beginning of your script (before importing pylab/pyplot) you should be doing im

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Mar 26, 2012, at 7:37 PM, Derek Homeier wrote: > Hi Sandro, > >> yes, Debian has a separate package for documentation (since it >> requires to be build just on time, whilc mpl requires to be built on >> each architecture we support, so splitting the package results in a >> lot of saved s

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Mon, Mar 26, 2012 at 12:00 PM, Russell Owen wrote: > On Mar 24, 2012, at 12:16 PM, Sandro Tosi wrote: > > > On Sat, Mar 24, 2012 at 18:13, Derek Homeier > > wrote: > >> I used the 1.1.0 version to build with the fink Python installation on > MaxOS X > >> and everything seems to work there, pa

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Mon, Mar 26, 2012 at 7:08 AM, Rui DaCosta wrote: > Attached is the testing output on both Win7x64 and WinXPx32. > > FAILED (KNOWNFAIL=268, errors=144) > > In case anybody else is having issues, the head version of nose is > required to run the tests due to multiprocessing issues in the stable

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen wrote: > > I have uploaded the Mac builds (no Python 2.6 yet; do we really need > that?). They pass all unit tests and the 32-bit version seems to work > well with my software. > > Might be nice to upload some python2.6 builds for the actual relea

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen wrote: > > The included pytz is outdated (and I did not bother to uprev it in the > binaries I uploaded); would somebody be willing to update that before we > cut the final releases, or is that considered too risky at this late > date? > > It feel

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Fri, Mar 23, 2012 at 12:21 PM, Sandro Tosi wrote: > > I'll start testing debian packaging right away; for our package we > also need the sampledata tarball: can I reuse the one for 1.1.0 or is > a new one needed? > > You can use the same one -- because this is a bugfix release, we have not int

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Thu, Mar 22, 2012 at 10:57 PM, Christoph Gohlke wrote: > > > Windows binaries, including the test files, are at < > http://www.lfd.uci.edu/~**gohlke/pythonlibs/#matplotlib > >**. > > All my attempts to upload the files to SF failed (no err

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

On Mon, Mar 19, 2012 at 12:58 PM, John Hunter wrote: > I think we are pretty close to cleaning up issues and PRs related to > v1.1.x, so I'd like to cut the release candidate this Thursday. Let's > continue to hammer on closing open issues and pull requests, and flag > any

[matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

I think we are pretty close to cleaning up issues and PRs related to v1.1.x, so I'd like to cut the release candidate this Thursday. Let's continue to hammer on closing open issues and pull requests, and flag anything that needs to be addressed before the release as "release_critical" in the issue

Re: [matplotlib-devel] colorbar extensions

On Wed, Mar 14, 2012 at 2:44 PM, Andrew Dawson wrote: > I implemented a new feature for colorbars, allowing the user to control > the length of the triangular extensions at either end. This is useful for > making plots consistent with those produced with other graphics packages. > > The URL for t

Re: [matplotlib-devel] GSOC mentoring organization

r. > > The timeline at http://www.google-melange.com/gsoc/events/google/gsoc2012says March 6th is the "[GSOC] Mentoring organization application deadline". How do you interpret "mentoring organization" there? As the PSF or someone under their umbrella such as statsmodels or

Re: [matplotlib-devel] GSOC mentoring organization

On Tue, Mar 6, 2012 at 9:57 AM, Nicolas Rougier wrote: > > And this page seems to gather all relevant links: > > > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/userguide > > One thing I am unclear on. They make a distinction between being mentors and organization

[matplotlib-devel] GSOC mentoring organization

Can anyone find the link to the form to fill out to become a GSOC mentoring application? The deadline is today and I'd like to participate. I've waded through the FAQ and other documents, but I seem to be running in circles. JDH ---

Re: [matplotlib-devel] matplotlib and Google Summer of Code

On Mar 1, 2012, at 9:01 AM, Nick Barnes wrote: > May I ask whether matplotlib is taking part in this year's GSoC? I'm > canvassing ideas for the Climate Code Foundation's participation, and > some scientists have suggested matplotlib-related improvements (e.g. a > GUI tool for constructing a

Re: [matplotlib-devel] faulty design for Lasso widget?

On Tue, Feb 28, 2012 at 10:44 AM, Benjamin Root wrote: > > The Lasso disconnects itself after the button_release event because that's > what indicates that you are done. The user gets back a single Line2D > object that is assumed to represent a single path with no breaks. Reusing > the Lasso wi

Re: [matplotlib-devel] re lease schedule for next version

On Sun, Feb 26, 2012 at 6:16 PM, Mark Lawrence wrote: > On 25/02/2012 17:13, John Hunter wrote: > > > After we get the bugfix out I'd like to gear up for a major python3 > release. > > Huge +1. > > I understand that the majority of Python and hence matplotlib pe

Re: [matplotlib-devel] re lease schedule for next version

On Sun, Feb 26, 2012 at 9:26 AM, Pierre Raybaut wrote: > I found out that a similar issue was reported for Spyder the same day > as this one... > > So I just posted something about this bug on PyQt mailing list: > http://www.riverbankcomputing.com/pipermail/pyqt/2012-February/031166.html > > I ad

Re: [matplotlib-devel] re lease schedule for next version

On Sat, Feb 25, 2012 at 1:54 PM, Benjamin Root wrote: > >> > I would be interested in accelerating the schedule. Since this is a >> > bug-fix release and not a major release, we can presume the tree is >> > pretty stable. How about we aim for an release candidate rc1 the >> > we

Re: [matplotlib-devel] re lease schedule for next version

On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root wrote: > > > On Thursday, February 23, 2012, RuiDC wrote: > >> >> Hi, >> There's a number of bugs fixed that would be nice to have without running >> git versions. >> Is there a release schedule for the next version? > > > There is not one in place r

Re: [matplotlib-devel] Should we update sample_data in the old SVN repo?

> my SF username is fer_perez, by the time I joined fperez was taken on > SF. If you have a chance of fixing this, I'll try to push again. Did you test? I did enable the same old fer_perez sf account you've always had. I was just referring to you by your email moniker in the post above. If it

Re: [matplotlib-devel] Should we update sample_data in the old SVN repo?

On Fri, Dec 16, 2011 at 7:17 PM, Fernando Perez wrote: > OK, thanks for trying.  Next week we can see if John can reopen it for > this.  I think there's no danger of anyone mistakenly committing any > real work there anymore. I've selectively enabled your (fperez) write access to the repo. Give

Re: [matplotlib-devel] tagging releases (v1.1.0 tag missing)

On Nov 12, 2011, at 2:47 AM, Paul Ivanov wrote: > On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root wrote: >> On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root wrote: >>> >>> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov wrote: Just wanted to re-ping the list, but include John and Ben

Re: [matplotlib-devel] Keybinding doc & close window

On Sat, Oct 29, 2011 at 2:52 PM, Antoine Levitt wrote: > Just typing f = gcf() displays a figure, which I don't want to do. I > want to be able to put something in my ipython init file that'd set my > bindings, without changing anything else. This is a reasonable request, though there are some im

Re: [matplotlib-devel] which to fork from?

On Tue, Oct 25, 2011 at 5:58 PM, Paul Ivanov wrote: > On Tue, Oct 25, 2011 at 3:52 PM, Daniel Hyams wrote: >> For small bugfixes, am I supposed to fork from v1.1.x, or master? > > I say 'master'  (Mike's been pushing some things to v1.1.x, but as he > said in a comment to #551, "Pushed to v1.1.x

Re: [matplotlib-devel] draw() in Figure does not obey get_animated()

On Fri, Oct 14, 2011 at 9:11 PM, Daniel Hyams wrote: > This could be intentional...I don't know much about the history of > matplotlib, so it's hard to guess at these things.  Anyway, the figure > container does not care about the "animated" state of its artists when it > does its drawing. > To fi

Re: [matplotlib-devel] Patch: Reorder #includes in ttconv/pprdrv_tt2.cpp

On Fri, Oct 14, 2011 at 6:30 AM, Wesley Emeneker wrote: > Attached is patch that moves > #include > to before > #include > > The Portland group compiler (v 11.8) won't build ttconv/pprdrv_tt2.cpp with > the original ordering. > This is most likely a compiler bug, but changing the include order s

Re: [matplotlib-devel] blurry images at native resolution with images.BboxImage: patch to fix

On Thu, Oct 13, 2011 at 10:06 AM, Daniel Hyams wrote: > Isn't the purpose of interpolation to handle situations where the image is > being displayed at a different size than its native resolution?  It seems Not solely, it can also be used to do local average of noisy images to get a smoother vie

[matplotlib-devel] ANN: matplotlib-1.1.0

A new release of matplotlib is available for download at https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.0 There are lots of nifty new features like Sankey diagrams, an API for animations and movie making, enhanced 3D support, support for auto-layout of subplots with

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 12:42 PM, Benjamin Root wrote: > What happens if someone tries to test without having the baseline images?  I > guess it hasn't been an issue before. Tests will fail. But the tests are already pretty dependent on things like freetype version so it might be more trouble th

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 11:43 AM, Christoph Gohlke wrote: > Is it really intended to include ~36 MB of tests/baseline_images in the > binary distributions for end users? I'm OK with excluding the test images from the binaries. Does anyone disagree? > Do you need eggs (not tested; without pytz a

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 11:04 AM, Sandro Tosi wrote: > On Thu, Oct 6, 2011 at 16:57, John Hunter wrote: >> Great -- they tarballs for the mpl src and sample_data are at >> >> https://github.com/matplotlib/matplotlib/archives/master > > I got an access denied for sa

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 9:57 AM, John Hunter wrote: > Great -- they tarballs for the mpl src and sample_data are at > > https://github.com/matplotlib/matplotlib/archives/master > > if Sandro would like to start with the debian packaging.  Russell and > Christoph, if you coul

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 9:48 AM, Michael Droettboom wrote: > On 10/06/2011 10:46 AM, John Hunter wrote: >> >> On Thu, Oct 6, 2011 at 9:44 AM, John Hunter  wrote: >>> >>> On Thu, Oct 6, 2011 at 9:17 AM, Michael Droettboom >>>  wrote: >>&

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 9:44 AM, John Hunter wrote: > On Thu, Oct 6, 2011 at 9:17 AM, Michael Droettboom wrote: > >> Pretty simple.  I have a pull request here: >> >> https://github.com/matplotlib/matplotlib/pull/509 > > I confirmed the qt bugs Eric and Michael we

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Thu, Oct 6, 2011 at 9:17 AM, Michael Droettboom wrote: > Pretty simple.  I have a pull request here: > > https://github.com/matplotlib/matplotlib/pull/509 I confirmed the qt bugs Eric and Michael were working on and tested the fixes, so i merged and closed these two. The only remaining issue

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Wed, Oct 5, 2011 at 1:49 PM, Eric Firing wrote: > Sorry to be holding things up after having nagged about getting a > release out, but I just now marked #506 "release_critical".  It looks > like a pretty fundamental bug in blitting on qt4agg, and I think I > introduced it back in January, righ

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On Mon, Oct 3, 2011 at 12:06 PM, Michael Droettboom wrote: > I'm just getting back from vacation, so excuse me if I'm late to the party. > This sounds fine to me, but there was one pretty serious report about the Qt > backend.  I haven't had a chance to investigate this yet, but will do so > soon

[matplotlib-devel] propose 1.1.0 release tomorrow

We made some additional progress over the weekend closing pull requests and issues, and I think we are ready to release tomorrow if no one objects. I want to hold off for a day to give people who do most of their work during the week a chance to close/finish/polish any lingering issues. The only

Re: [matplotlib-devel] Animation.save not working?

On Sun, Oct 2, 2011 at 10:27 AM, John Hunter wrote: > I am trying to make an animation of the double pendulum using the > attached script (v1.1.x branch).  It creates all the files _tmp*.png, > and creates the mpg but it has zero file size.  If I manually make the > movie with the re

[matplotlib-devel] Animation.save not working?

I am trying to make an animation of the double pendulum using the attached script (v1.1.x branch). It creates all the files _tmp*.png, and creates the mpg but it has zero file size. If I manually make the movie with the resultant PNGs, it works fine mencoder mf://_tmp*.png -mf type=png:fps=15 -o

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 4:00 PM, Benjamin Root wrote: > No, I couldn't figure out how to do that on sourceforge. OK, I'm working on this and will send out the ANN when it is done. Thanks everyone for their help, and Ben especially for herding the cats and pushing us forward. JDH --

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 3:23 PM, Russell Owen wrote: > I just uploaded a Mac binary for 32-bit Python 2.7. I propose to leave it at > that unless the 2.6 version is required for the release candidate. Great. Ben, did you have any luck getting the 1.1.0 docs hosted in some temp location? --

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 11:41 AM, Christoph Gohlke wrote: > matplotlib-1.1.0.win installers are at > . They were built > against numpy 1.6.1. Ahh, yes, I would have seen that if I had read Sandro's link to the end. Must read more carefully

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 11:30 AM, Sandro Tosi wrote: > On Tue, Sep 27, 2011 at 18:23, John Hunter wrote: >> On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root wrote: >> >>> Working through the checklist, I am wary of cutting an RC at this particular >>> moment. &g

Re: [matplotlib-devel] mpl release candidate branch

On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root wrote: > Working through the checklist, I am wary of cutting an RC at this particular > moment.  Why is just about a quarter of all the tests coming back as known > fails?  Also, running unit/memleak_hawaii3.py is showing what seems to be a > memory

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 11:54 PM, Benjamin Root wrote: > I will see about cutting the release, but I won't be able to upload any > files to SF, unless somebody can give me that permission for my account. I have made you a project admin on the sf site. That means you have full permission to do an

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 5:04 PM, Benjamin Root wrote: > Personally, my vote is to live with the deprecation warnings.  They only > happen if you turn warnings on in python 2.7 (by default, they are off).  I > am not that comfortable with such a change this close to release for a minor > issue (unl

Re: [matplotlib-devel] mpl release candidate branch

On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root wrote: > Working through the checklist, I am wary of cutting an RC at this particular > moment.  Why is just about a quarter of all the tests coming back as known There are only two legit known fails, one in test_basic and one in test_dates and thes

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 4:46 PM, Michael Droettboom wrote: > I haven't seen any of these warnings: DeprecationWarnings and > PendingDeprecationWarnings are supposed to be turned of by default in a > vanilla Python build.  However, I'm familiar with the PyCObject/PyCapsule > issue from working on t

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 4:19 PM, Benjamin Root wrote: > I wanted to do some changes to doc/users/installing.rst, but it is ignored > by the .gitignore file.  Is this information autogenerated somewhere else? This looks like an error in .gitignore. i wrote that file, and can assure you it was no

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 3:42 PM, John Hunter wrote: > On Fri, Sep 23, 2011 at 8:02 AM, John Hunter wrote: >> Today is the "go-live" date for the mpl release candidate. There are >> no more open issues tagged release_critical, so I suggest we branch >> this afte

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 8:02 AM, John Hunter wrote: > Today is the "go-live" date for the mpl release candidate. There are > no more open issues tagged release_critical, so I suggest we branch > this afternoon.  This will give people a last chance to merge in > remaining

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 11:56 AM, Michael Droettboom wrote: > I agree with your assessment -- it seems like a low-level difference in the > freetype renderer.  I guess we should increase the tolerance on these tests > (by passing a tol keyword to the image_comparison decorator in > test_mathtext.p

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 10:34 AM, Michael Droettboom wrote: > I'm not able to reproduce this here (git/master on Ubuntu 10.4, Python > 2.7).  Can you send and/or link to an example broken image?  The way in > which it is failing may illustrate the cause of the problem.  It could > also be that the

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 8:02 AM, John Hunter wrote: > Today is the "go-live" date for the mpl release candidate. There are > no more open issues tagged release_critical, so I suggest we branch > this afternoon.  This will give people a last chance to merge in > remaining

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 9:11 AM, Jouni K. Seppänen wrote: > This pull request fixes a test failure: > > https://github.com/matplotlib/matplotlib/pull/476 > > Should I just merge it myself, or does someone still want to review it? Since you and Mike have both looked at it, it is probably good to g

[matplotlib-devel] mpl release candidate branch

Today is the "go-live" date for the mpl release candidate. There are no more open issues tagged release_critical, so I suggest we branch this afternoon. This will give people a last chance to merge in remaining pull requests. If you know you are planning to handle a given pull request before the

Re: [matplotlib-devel] release: stalled again?

On Sun, Sep 18, 2011 at 4:02 PM, Eric Firing wrote: > There is a way to deal with this now: define our own copyto which uses > np.copyto if it exists, and falls back on putnav otherwise.  I think this > can be done with reasonable safety and no loss of performance.  The only > question is where to

Re: [matplotlib-devel] release: stalled again?

> putmask was deprecated in favor of copyto only 2 months ago; copyto > didn't even exist before that. So we certainly can't replace putmask > with copyto in mpl. > > http://currents.soest.hawaii.edu/hgstage/numpy_from_git/rev/26533521322b The putmasks in colors.py are simple and could be replace

Re: [matplotlib-devel] release: stalled again?

On Sun, Sep 18, 2011 at 1:17 AM, Christoph Gohlke wrote: > The master branch builds OK on Windows and so far almost everything > worked well. > > I have trouble receiving the sample_data from github via cbook.py. There > are frequent HTTP 304 (Not Modified) and 500 (Internal Server Error) > excep

Re: [matplotlib-devel] release: stalled again?

On Sun, Sep 18, 2011 at 1:44 PM, Fernando Perez wrote: > I'm not sure why, but as of a few weeks ago, with recent builds of > numpy/mpl I always get these warnings: > > In [1]: imshow(rand(10,10)) > Out[1]: > > In [2]: > /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/colors.py:519:

Re: [matplotlib-devel] [Basemap] Please explicit mention copyright and license

On Sun, Sep 18, 2011 at 9:46 AM, Sandro Tosi wrote: > Hello, > I'm packaging basemap for Debian, but as you know, we always have some > problems :) > > One important part of Debian packaging is the license/copyright > checks, but for basemap I can't find any explicit indication of them: > > for li

Re: [matplotlib-devel] release: stalled again?

On Sat, Sep 17, 2011 at 7:01 PM, Benjamin Root wrote: > Agreed.  Let's declare a feature freeze at this point.  Unless you already > have a pull, no new features, and even those with existing pulls need to be > carefully considered.  I already have to make some updates to the "what's > new" sectio

Re: [matplotlib-devel] release: stalled again?

On Sat, Sep 17, 2011 at 4:08 PM, Benjamin Root wrote: > I think it will take a declaration of a firm deadline.  How about this? > > Cut RC release Friday, Sept 23rd > Release v1.1.0 Friday, Sept. 30th. > (Barring any major significant changes) Works for me; should we branch on the rc cut or befor

Re: [matplotlib-devel] Initialising projections in matplotlib

On Thu, Sep 15, 2011 at 1:19 PM, Phil Elson wrote: > I have made a change to matplotlib which would enable this capability, which > can be found at > https://github.com/PhilipElson/matplotlib/commit/9c7b1b27d0245a752d010bd03ae66dc6c000d8e499 > . Any feedback and thoughts would be really appreciate

Re: [matplotlib-devel] github workflow

On Wed, Aug 31, 2011 at 10:16 PM, Matthew Brett wrote: > Yo, > > On Wed, Aug 31, 2011 at 7:54 PM, John Hunter wrote: >> github workflow: this seems to present a different workflow than that >> espoused in gitwash used by mpl and other projects >> >> http://

[matplotlib-devel] github workflow

github workflow: this seems to present a different workflow than that espoused in gitwash used by mpl and other projects http://scottchacon.com/2011/08/31/github-flow.html I like the idea of lots of feature branches off upstream/master and master always being deployable (nightly builds?). What

Re: [matplotlib-devel] Issue with colored latex text on plots

On Wed, Aug 31, 2011 at 8:49 PM, John Hunter wrote: >> Note that I'm not subscribed to this list, so please CC me on replies. > > That won't work because mpl converts all tex png raster to black and > white and handles color on its own in post-processing.  The followin

Re: [matplotlib-devel] Issue with colored latex text on plots

On Sat, Aug 27, 2011 at 4:15 PM, Michael Gilbert wrote: > Hi, > > I'm trying to generate colored text on my plots, but   can only seem > to get black and white.  I've attached an example python scriptx > (test.py) that demonstrates the problem.  This produces a plot > (test.png) with black and whi

Re: [matplotlib-devel] boilerplate.py

On Wed, Aug 31, 2011 at 7:34 PM, Benjamin Root wrote: > Hello all, > > In my continuing quest to get style cycles working, I wanted to get > errorbar() to support it as well.  Unfortunately, errorbar() has a default > kwarg 'fmt' that takes a value of '-', and *None* already has a special > meanin

Re: [matplotlib-devel] Calling all Mac OSX users!

On Wed, Aug 17, 2011 at 3:42 PM, Andy Somogyi wrote: > Why do you need to download and build png, zlib, freetype? I build matplotlib > semi-regularly on 10.6.8 using the built in libraries and it works perfectly > fine. I built with both gcc 4.2 / 4.6 and llvm and all work fine. I use > officia

Re: [matplotlib-devel] Calling all Mac OSX users!

On Mon, Aug 15, 2011 at 9:34 PM, Benjamin Root wrote: > The mpl developers are getting very close to the long-awaited v1.1.0 release > of matplotlib.  Before we do so, we are doing some final checking of the > documentation to make sure that all critical pieces of information iss > correct and up

Re: [matplotlib-devel] Fwd: Re: [matplotlib] Provide ipython 0.11 compatibility (#411)

On Wed, Aug 3, 2011 at 2:53 PM, Benjamin Root wrote: > On Wed, Aug 3, 2011 at 2:42 PM, Eric Firing wrote: >> >> Can we please just release something now, so Debian doesn't have to come >> up with their own modification of 1.0.1? >> >> Eric >> > > As far as I am concerned, the only thing stopping

Re: [matplotlib-devel] Plan for cutting v1.1.0?

On Wed, Jul 13, 2011 at 2:54 PM, Eric Firing wrote: > As I recall, John had time to help in June, but less after that.  I > don't think we ever reached an agreement as to schedule.  It simply went > into slide mode. I am back from my vacation so I have time again. I figured since I was leaving

Re: [matplotlib-devel] adding valid signals to a CallbackRegistry?

On Thu, Jun 23, 2011 at 3:11 PM, Michael Droettboom wrote: > On 06/23/2011 03:49 PM, Benjamin Root wrote: > > Hello all, > > I am working to make mplot3d feature-parity with regular axes objects.  I > have come across a possible design flaw with the CallbackRegistry. > > Many of the Axes3D methods

Re: [matplotlib-devel] [Matplotlib-users] Plan to merge the matplotlib-py3 branch?

On Wed, Jun 15, 2011 at 9:02 AM, Darren Dale wrote: > I suggest we make a 1.1.x branch from the current state of master, and > consider it as a placeholder for now. Then we bump the version number > in the py3 repo to *2.0*, merge py3/master back into mpl/master, and > delete the py3 repo. The re

Re: [matplotlib-devel] Sankey diagram toolkit

On Tue, Jun 14, 2011 at 8:46 AM, Kevin Davies wrote: > Hello, > I should have sent the original email in plain text rather than HTML, so I am > resending it.  Please give me suggestions regarding my email below.  Thanks. Hey Kevin, the toolkit looks quite nice and we would be happy to distribu

  1   2   3   4   5   6   7   8   9   10   >