-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Remove to original callable #29012
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
Remove to original callable #29012
Conversation
Update Local Version
Updating to most recent version
Replaced the function to_original_callable with the function inspect.unwrap
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.
Thanks @Nabel0721. Before we merge this we need to make sure we understand what it affects.
We should generate the list of error before and after this change, and see which errors this fixes, and which this introduces, and see if it's what we want. You have a --format=json
that can be useful.
Attached are the two json files with the errors. It looks like it's introducing more errors, but I think that it's just uncovering some errors that were previously covered. We can hold off on this PR though, if you think it's introducing too much. Some of the new errors should be sorted out as I go through the codebase for decorators without the change_formatted.txt Let me know what you think when you can. There's a lot of data in there. |
This import is now unnecessary for this script.
Thanks for that @Nabel0721. It's not a problem at all to have more errors, if they are genuine. What I don't is to add incorrect errors, because we're validating the wrong docstring. Do you have the list of new errors? Would be great to have a look at some of them and try to understand why they're appearing after this change. |
I’ll look over them more this week. I don’t have as much time as I used to,
so it’ll take a bit. But I should be able to figure out if they’re
legitimate errors or not.
On Tue, Oct 15, 2019 at 10:41 PM Marc Garcia ***@***.***> wrote:
Thanks for that @Nabel0721 <https://github.com/Nabel0721>. It's not a
problem at all to have more errors, if they are genuine. What I don't is to
add incorrect errors, because we're validating the wrong docstring.
Do you have the list of new errors? Would be great to have a look at some
of them and try to understand why they're appearing after this change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29012?email_source=notifications&email_token=ACT76URGIAO6CXLL55PMAQDQOZ5MLA5CNFSM4JBC2M52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBK2TAI#issuecomment-542484865>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACT76URD7SQBFOLUNB2BJF3QOZ5MLANCNFSM4JBC2M5Q>
.
--
Sincerely,
*Nathan Abel*
Kettering University - Computer Science
989-780-3050
|
I think this is already done now that the script lives in numpydoc |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff
@datapythonista This is the pull request for replacing to_original_callable