Fix travis install failure on py31

[dmcdougall]

Trying to fix the Travis tests, since we seem to be getting lots of false negatives.

This is not ready to merge. I'm only pushing here to trigger a travis build.

[dmcdougall]

This is the queued py31 Travis job.

[pelson]

FYI, you don't need a PR to run a travis-ci job. You can always enable travis-ci on your repo and then it will run for each commit you push. I don't recommend doing this in general, but it is a nice way of testing travis-ci related issues.
Of course, there is no problem with making a PR here either, I just wanted to let you know about the other possible alternative approaches.

Cheers!

[dmcdougall]

@pelson I tried that. For some reason the payload wasn't being deployed. I enable the setting in both my fork and on my Travis profile page.

[dmcdougall]

One of the errors is: Executing your (rm -f ~/.ssh/source_rsa) took longer than 3 minutes and was terminated.

I don't think there's a whole lot we can do about that...

[dmcdougall]

And the other is: Executing your (git clone --depth=100 --quiet git://github.com/matplotlib/matplotlib.git matplotlib/matplotlib) took longer than 3 minutes and was terminated.

I think this venture is a lost cause. Closing.