Closed gmbrandt closed 3 years ago
Hi @gmbrandt , thank you for pointing this out, the traceback and the MWE. I'll try to reproduce it, and get back to you!
Hi @gmbrandt,
I'm unable to replicate the error using your MWE with my current environment, here are my versions - python == 3.8.1 numpy == 1.19.4 barycorrpy == 0.3.4 astropy == 4.1
I'll update them and check.
I do reproduce the error using numpy==1.20.0 and astropy==4.2. Closing it with #37
Thanks!
using get_BC_vel in python 3.8 with up to date packages (e.g. astropy etc.) raises a int object is not callable error. The stack trace follows
Minimal working example to reproduce the above issue (package versions follow at the end of this issue)
Calling the above in e.g. Ipython will cause the aforementioned error. This seems like an issue with np.size() crashing on a length 1 astropy.time.Time object.One gets the same error with
JDUTC=mid_obstime,
i.e. using the actual Time value results in the same error.This was not an issue in python 3.5
My environment to reproduce the error: python == 3.8.5 astropy==4.2 numpy==1.20.0 (also fails with numpy==1.19.5)