-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
DeprecationWarning #486
Comments
Well, how annoying. Using Booleans as indexes is so useful! I suppose that because of this unwelcome change in NumPy, that all the search routines will have to coerce their output values to something like int8 in the case that they detect their object function has been returning Boolean values. Thanks for letting me know. The lack of a changelog entry must be because I forgot to push the docs? It was a quick release to fix a bug, so I might have skipped a few steps. Later this week I'm planning a more casual release, and hopefully the docs will catch up at that point. |
Thank's a lot. |
I have committed a possible fix. To try it out, run:
— and then see if the deprecation warning goes away. |
I've been looking into alternatives to boolean indexing since it's used quite often in |
@JoshPaterson — You might be talking about a different technique: the use of an array of Booleans as long as the array being indexed? That will always be supported and is indeed a backbone of NumPy and libraries that rely on it, like Pandas. The deprecated use, by contrast, is the use of single ("scalar" in the deprecation warning) Booleans to select element 0 or element 1 out of an array. Try this:
When run with
|
Yes, that is the source of the confusion! Thanks for explaining that. |
Good morning Brandon,
I ran the meridian_transit() function today, and I got the following Warning due to Deprecation Warning. That shows you should update the codes.
On the other hand, the recent version of Skyfiled is 1.33, but I didn't see any changelog on the website regarding this version.
Best regards,
The text was updated successfully, but these errors were encountered: