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:58 PM, John Hunter wrote: > 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 lu

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

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. -- Russell On Sep 27, 2011, at 9:32 AM, John Hunter wrote: > On Tue, Sep 27, 2011 at 11:30 AM, Sandro Tosi wrote: >> On Tue, Sep 27, 2011 at 18:23, Jo

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 12:20 PM, Sandro Tosi wrote: > On Tue, Sep 27, 2011 at 18:30, 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 t

Re: [matplotlib-devel] mpl release candidate branch

On Tue, Sep 27, 2011 at 18:30, 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. > > It was announced here: > > http://so

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 9/27/2011 9:32 AM, John Hunter wrote: > 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 parti

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. > > It was announced here: > > http:/

Re: [matplotlib-devel] mpl release candidate branch

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. It was announced here: http://sourceforge.net/mailarchive/message.php?msg_id=28136691 I'm test

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 09/24/2011 03:33 PM, Jouni K. Seppänen wrote: > Jouni K. Seppänen writes: > >> Jouni K. Seppänen writes: >> >>> The light and condensed fonts are DejaVuSans, which happened to be >>> installed on the system on which that test was created. I think the test >>> should only rely on the fonts deli

Re: [matplotlib-devel] mpl release candidate branch

On 09/24/2011 08:22 AM, John Hunter wrote: > 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 chang

Re: [matplotlib-devel] mpl release candidate branch

Jouni K. Seppänen writes: > Jouni K. Seppänen writes: > >> The light and condensed fonts are DejaVuSans, which happened to be >> installed on the system on which that test was created. I think the test >> should only rely on the fonts delivered with matplotlib. > > I created a github issue: > >

Re: [matplotlib-devel] mpl release candidate branch

Benjamin Root writes: >> FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip > > I am seeing this one on my 64-bit machine, but not on my 32-bit machine > (both Linux). Fix in https://github.com/matplotlib/matplotlib/pull/490 The uninitialized memory being written to disk sometimes con

Re: [matplotlib-devel] mpl release candidate branch

Jouni K. Seppänen writes: > The light and condensed fonts are DejaVuSans, which happened to be > installed on the system on which that test was created. I think the test > should only rely on the fonts delivered with matplotlib. I created a github issue: https://github.com/matplotlib/matplotlib

Re: [matplotlib-devel] mpl release candidate branch

Jouni K. Seppänen writes: >>> FAIL: matplotlib.tests.test_text.test_font_styles.test >>> FAIL: matplotlib.tests.test_text.test_font_styles.test >>> >> How much was the difference? > > Large: in all three result images, the condensed and light fonts look > the same as normal, and there are differe

Re: [matplotlib-devel] mpl release candidate branch

Jouni K. Seppänen writes: >>> FAIL: no_testCreateLocaltime (test_tzinfo.LocalTestCase) >>> >> Any info provided on this failure? > > AssertionError: '2004-10-31 02:00:00 AMT+0020' != '2004-10-31 02:00:00 > CET+0100' That test has a comment "It would be nice if this worked, but it doesn't." and

Re: [matplotlib-devel] mpl release candidate branch

Benjamin Root writes: >> I'm seeing five test failures on my Mac (Python 2.7): >> >> FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip >> > > I am seeing this one on my 64-bit machine, but not on my 32-bit machine > (both Linux). > > >> FAIL: matplotlib.tests.test_text.test_font_styles

Re: [matplotlib-devel] mpl release candidate branch

On Sat, Sep 24, 2011 at 8:25 AM, Jouni K. Seppänen wrote: > I'm seeing five test failures on my Mac (Python 2.7): > > FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip > I am seeing this one on my 64-bit machine, but not on my 32-bit machine (both Linux). > FAIL: matplotlib.tests.te

Re: [matplotlib-devel] mpl release candidate branch

I'm seeing five test failures on my Mac (Python 2.7): FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip FAIL: matplotlib.tests.test_text.test_font_styles.test FAIL: matplotlib.tests.test_text.test_font_styles.test FAIL: matplotlib.tests.test_tightlayout.test_tight_layout5.test FAIL: no_

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 11:54 PM, Benjamin Root wrote: > On Fri, Sep 23, 2011 at 6:35 PM, Benjamin Root wrote: > >> >> On Fri, Sep 23, 2011 at 4:46 PM, Benjamin Root wrote: >> >>> >>> >>> On Friday, September 23, 2011, John Hunter wrote: >>> > On Fri, Sep 23, 2011 at 4:19 PM, Benjamin Root >>

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 6:35 PM, Benjamin Root wrote: > > On Fri, Sep 23, 2011 at 4:46 PM, Benjamin Root wrote: > >> >> >> On Friday, September 23, 2011, John Hunter wrote: >> > On Fri, Sep 23, 2011 at 4:19 PM, Benjamin Root wrote: >> > >> >> I wanted to do some changes to doc/users/installing

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 4:46 PM, Benjamin Root wrote: > > > On Friday, September 23, 2011, John Hunter wrote: > > 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 inf

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 Friday, September 23, 2011, 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 the matpl

Re: [matplotlib-devel] mpl release candidate branch

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 the matplotlib-py3 branch. The py3 branch has changes to the loc

Re: [matplotlib-devel] mpl release candidate branch

On Friday, September 23, 2011, John Hunter wrote: > 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 .

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 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 pull requests. If you kn

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 afternoon.  This will give people a last

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 pull requests.  If you kno

Re: [matplotlib-devel] mpl release candidate branch

On 9/23/2011 6: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 pull requests. If you know you are

Re: [matplotlib-devel] mpl release candidate branch

On Fri, Sep 23, 2011 at 9:59 AM, Benjamin Root wrote: > > > On Friday, September 23, 2011, 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 peopl

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

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.py). The default is 1e-3 -- we just need to find the minimum valu

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

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 difference in the freetype library/settings is causing enough di

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 pull requests.  If you kno

Re: [matplotlib-devel] mpl release candidate branch

On Friday, September 23, 2011, 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 pull requests. If you know

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

Re: [matplotlib-devel] mpl release candidate branch

John Hunter writes: > 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. This pull request fixes a test failure:

[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