On Mon, Feb 9, 2015 at 1:00 AM, Thomas Caswell wrote:
> 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.
I switch to GH tarball, but I must say they are a lot different than
the SF ones
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
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.
>
> =
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
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
I am getting some test failures here and on master in the collections
module.
==
FAIL: __main__.test_regularpolycollection_rotate.test
--
Traceback (most recent c
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.
If you want to tracking GH for debian instead of SF I don't think that
would be a bad idea, but I don't know how much of a has
On Sat, Feb 7, 2015 at 9:05 PM, Thomas Caswell wrote:
> Sandro,
>
> Can you use the tarball from github
> (https://github.com/matplotlib/matplotlib/archive/v1.4.3rc1.tar.gz ?)
Sure I can, but since all the previous release (even RC) were done one
SF, we have our tools to monitor and download new
Sandro,
Can you use the tarball from github (
https://github.com/matplotlib/matplotlib/archive/v1.4.3rc1.tar.gz ?)
Tom
On Sat Feb 07 2015 at 4:01:01 PM Sandro Tosi wrote:
> Hi Thomas,
>
> On Mon, Feb 2, 2015 at 5:37 AM, Thomas Caswell wrote:
> > Evening all,
> >
> > I have tagged the first re
Hi Thomas,
On Mon, Feb 2, 2015 at 5:37 AM, Thomas Caswell wrote:
> Evening all,
>
> I have tagged the first release candidate for v1.4.3
> (https://github.com/matplotlib/matplotlib/releases/tag/v1.4.3rc1).
...
> Please kick the tires and give it a try! If there are no major issues, the
> plan is
Awesome work! Full credit to Tom who has driven this release.
The nbagg backend is looking great - some pretty swish new features thanks
to hard work from Steven Silvester and Thomas Caswell!
On 2 February 2015 at 10:58, Jens Nielsen wrote:
> Thanks Tom,
>
> I ran the test suite on OSX 10.10 wi
Hi,
On Mon, Feb 2, 2015 at 2:58 AM, Jens Nielsen wrote:
> Thanks Tom,
>
> I ran the test suite on OSX 10.10 with both python 2.7.8 and 3.4.2 including
> the tex and QT4 tests that are skipped on Travis.
> Everything passes as expected.
I built wheels for OSX testing, via the automated travis bui
12 matches
Mail list logo
