Automated test build machinery on travis - move to numpy or scipy org?
19 Jun 2014 19 Jun '14
As some of you might have seen, I automated the build of numpy / scipy against ATLAS using recent gcc here:
with testing and uploading to Rackspace here:
(thanks to Matt Terry for the original code for travis-ci build / testing  and Olivier Grisel for setting me up for Rackspace upload).
Maybe it would be a good idea to move numpy-atlas-build to numpy or scipy organization and maintain it as part of the release process?
Age (days ago)
Last active (days ago)