Re: [matplotlib-devel] exception in sankey demo in examples

2011-09-24 Thread Benjamin Root
On Saturday, September 24, 2011, Mike Kaufman wrote: > Possible bug report: > > "Exception occurred rendering plot." > > http://matplotlib.github.com/examples/api/sankey_demo.html > > This is with firefox 6.0.2 > > M > This was discovered and fixed in master a couple of months ago. Essentially,

[matplotlib-devel] exception in sankey demo in examples

2011-09-24 Thread Mike Kaufman
Possible bug report: "Exception occurred rendering plot." http://matplotlib.github.com/examples/api/sankey_demo.html This is with firefox 6.0.2 M -- All of the data generated in your IT infrastructure is seriously valu

Re: [matplotlib-devel] mpl release candidate branch

2011-09-24 Thread Jouni K . Seppänen
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

2011-09-24 Thread Jouni K . Seppänen
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] v1.1.0 branch created

2011-09-24 Thread Christoph Gohlke
On 9/24/2011 11:41 AM, Benjamin Root wrote: > The source tarball for the rc can be found here: > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.0/ > > binary builders can use this and upload the binaries there. Please let > me know when the windows and mac binaries

Re: [matplotlib-devel] mpl release candidate branch

2011-09-24 Thread Jouni K . Seppänen
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

2011-09-24 Thread Jouni K . Seppänen
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] v1.1.0 branch created

2011-09-24 Thread Benjamin Root
The source tarball for the rc can be found here: https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.0/ binary builders can use this and upload the binaries there. Please let me know when the windows and mac binaries are ready so that we can make an official call for test

Re: [matplotlib-devel] mpl release candidate branch

2011-09-24 Thread Jouni K . Seppänen
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

2011-09-24 Thread Jouni K . Seppänen
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

[matplotlib-devel] v1.1.0 branch created

2011-09-24 Thread Benjamin Root
Ok, the v1.1.0 branch has been created, and I am in the process of doing the tarballs and such. Please file any pull requests against that branch. I will also tag v1.1.0-rc1 when I make the official announcement. Ben Root ---

Re: [matplotlib-devel] mpl release candidate branch

2011-09-24 Thread Benjamin Root
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

2011-09-24 Thread Jouni K . Seppänen
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] basemap_1.0.1-1_amd64.changes ACCEPTED into unstable

2011-09-24 Thread Sandro Tosi
I'm pleased to announce basemap has just been accepted into Debian, and soon will be available to unstable/testing users! Thanks for your help in this process! On Sat, Sep 24, 2011 at 11:17, Debian FTP Masters wrote: > > > > Accepted: > basemap_1.0.1-1.debian.tar.gz >  to main/b/basemap/basemap_1

Re: [matplotlib-devel] mpl release candidate branch

2011-09-24 Thread John Hunter
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

2011-09-24 Thread John Hunter
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

2011-09-24 Thread John Hunter
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