Re: [Matplotlib-users] [matplotlib-devel] v1.4.3rc1

2015-02-08 Thread Thomas Caswell
Sorry about the bad tarball, I forgot to clean my git directory before generating it. Another point in favor of using the gh tarball, I can't screw it up. This is the first I have seen that CVE. That PR is not included in 1.4.3 because it completely over-hauls how the Agg rendering works (and ge

Re: [Matplotlib-users] [matplotlib-devel] v1.4.3rc1

2015-02-08 Thread Benjamin Root
Please ignore my test failure report. I was accidentally running an older install of matplotlib from the same branch. Ben Root On Sat, Feb 7, 2015 at 9:08 PM, Benjamin Root wrote: > I am getting some test failures here and on master in the collections > module. > > =

Re: [Matplotlib-users] [matplotlib-devel] v1.4.3rc1

2015-02-08 Thread Sandro Tosi
Hi, On Sat, Feb 7, 2015 at 9:46 PM, Thomas Caswell wrote: > Sandro, > > Well, creating the tarball on GH is a lot easier for us as it happens > automatically! I don't want to unilaterally change policy so I will create > the files on SF. the release tarball contains __pycache__ directories and

Re: [Matplotlib-users] [matplotlib-devel] v1.4.3rc1

2015-02-08 Thread Sandro Tosi
On Sat, Feb 7, 2015 at 9:46 PM, Thomas Caswell wrote: > Well, creating the tarball on GH is a lot easier for us as it happens > automatically! I don't want to unilaterally change policy so I will create > the files on SF. > > If you want to tracking GH for debian instead of SF I don't think that