-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
working with python 2 but not with python 3 #207
Comments
#207 and #208 have high chance to be the same issue. test cases with skyfield 1.8 and numpy 1.15.1 from skyfield.api import load
ts = load.timescale()
eph = load('de421.bsp')
earth = eph['earth']
t = ts.utc(2000, range(12)) python 3 lat, lon, distance = earth.at(t).ecliptic_latlon('date')
lat, lon, distance = earth.at(t).ecliptic_latlon(t) those two line of code work fine. but lat, lon, distance = earth.at(t).ecliptic_latlon() keep rising the same error message as before. python 2it is the revers: lat, lon, distance = earth.at(t).ecliptic_latlon() work. lat, lon, distance = earth.at(t).ecliptic_latlon(t)
lat, lon, distance = earth.at(t).ecliptic_latlon('date') rise this error Does anyone can reproduce my result ? |
Until this is fixed, the build should be broken.
My guess is that you might have a different version of Skyfield installed under each version of Python, since that method didn't used to take an optional second argument; that would explain why you're not seeing the same error (which is a real one that needs to be fixed!) under Python 2, which isn't even accepting the new 2nd argument. Could you try printing |
I've just released Skyfield 1.9 with this fix. Thanks for the report! |
yes indeed ... my mistake: 2 different version off skyfield on my system: thank for skyfield.VERSION, I'll use it in future bug report |
Hopefully you can now upgrade both Pythons and get working Skyfields :) |
skyfield 1.8
it work fine
but by changing the first line by this
#!/usr/bin/env python3
it throw this error
am I missing something ?
I believe this script was doing ok before...
The text was updated successfully, but these errors were encountered: