False alarm. The Travis logs includes (but hides) the install output, and
test_mlab was running for me, but I was looking at the wrong line
numbers. Still though, I would be curious as to any differences, but I
can't seem to download the log file.
Ben
On Thu, Jun 26, 2014 at 6:57 PM, Benjamin
Just noticed an oddity with the tests on Travis versus the tests on my
machine. The test log on Travis for a single run has over 10,000 lines.
But, for me, it is over ~4800 lines. At a glance, I can see that test_mlab
is not executed for me, but they are for Travis. I am very suspicious of
the test
This is very interesting. I have also noticed that ticking has been a
bottleneck in rendering, but always suspected the computation of the ticks
rather than the actual rendering of the marks. Perhaps this might spur some
renewed interest in identifying the specific reason for the bottleneck and
sol
About a week ago I sent a message to the users mailing list with tick mark
performance problems. I now have a proof of concept patch which (mis-)uses the
projection keyword in add_subplot to use a custom Axes class. Import one
python file, use "projection='fastticks'" -> boring scatter plots rend
