-
Notifications
You must be signed in to change notification settings - Fork 437
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
RF: Use new name for this function. #2348
Conversation
Hello @arokem, Thank you for updating ! Cheers ! There are no PEP8 issues in this Pull Request. 🍻 Comment last updated at 2021-04-08 05:53:22 UTC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @arokem,
Thank you for this update!
it seems you are missing 2-3 real_sph_harm
in test_shm.py
. Also, you will have to update test_default_lambda_csdmodel
.
Thanks !
Thanks for taking a look! I also took the opportunity to replace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @arokem,
You forgot to address the problem with test_default_lambda_csdmodel
. You just need to update the number of warnings to be caught.
After that, it should be ready to be in.
Thanks!
On the way to deprecation by 2.0
12cd257
to
13965d2
Compare
OK - I think I got it all now. Thanks for the quick review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Green, CI's Happy, I will merge this if there is no additional comment by the end of the day.
Thank you for this @arokem!
@arokem By changing the method name in here: a duplication was introduced with an existing method name: Thus, only the second one is being tested: If the first one, which is calling the deprecated |
This shouid eliminate warnings that now routinely appear