fa1f6f2b19
For Travis CI: a more recent numpy for Python 3.7
2019-12-16 12:16:57 -05:00
3f3a762baf
Lock down NumPy version on Travis CI, to fix #35
...
This should stop jplephem from accidentally using features too modern
for users on several-year-old systems.
2019-12-16 09:17:01 -05:00
f4fbaa962f
Fix Travis CI by only doing one cd
2019-09-19 16:21:40 -04:00
aae60da592
Check in ephemerides necessary for CI testing
...
This prevents Travis CI from having to hammer the JPL servers when
testing jplephem against several versions of Python at once. It
will also stop CI from routinely erroring out one or more versions
of Python when the JPL’s servers happen to drop a request.
2019-09-19 16:05:24 -04:00
ba560cb086
Travis CI: abandon Python 3.3 but try 3.7
2019-08-22 16:07:43 -04:00
b7a4d0c45c
To fix the build,bid a fond farewell to Python 2.6
2018-02-09 07:32:50 -05:00
c66d674a35
Stop fetching deprecated ephemeris package
...
There is really no point in having Travis burn bandwidth for this on
every commit any more.
2016-04-02 20:22:31 -04:00
7891d59ac3
Add Python 3.5 to Travis configuration
2016-04-02 20:22:01 -04:00
93f7e54e80
Add de405 to kernels downloaded for Travis CI test
2015-08-04 09:07:24 -04:00
5a4e7abfb4
Have Travis CI do a real install from .tar.gz
2015-02-08 15:20:04 -05:00
2491588038
Switch JPL tests to our SPK code with DE430
2015-02-08 03:31:53 -05:00
79b53434a9
Remember to tell Travis where package lives now
2015-02-08 01:31:39 -05:00
c9a51f1a7b
Fix Travis tests by downloading necessary file
2015-02-07 21:30:24 -05:00
27a77343d9
Add Travis CI integration
2015-02-07 19:16:48 -05:00
Brandon Rhodes