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
Fixes to inspection machinery for magics #1845
Conversation
Refactored some of the oinspect logic into standalone functions and added tests.
From the looks of this, you're taking a conservative approach - only referring to Whichever way we prefer, we should probably make it consistent. |
Good point, I'll change it to go with our previous reasoning, I agree with it. Thanks for the review, I'll update as soon as I have a minute. |
Once you make the changes, I think this can be merged. |
Will do, thanks for the review... |
OK, thanks for the review guys. I made the suggested changes, and added extra tests to validate that we really access |
Fixes to inspection machinery for magics Now that magics are generated via decorators, the inspection machinery wasn't finding data about them such as source code. Fixes that along with some refactoring, cleanup and test additions. Closes gh-1799.
The |
I just missed that fact, refactoring PR welcome! |
I tried: #1919 |
Great, merged. |
Fixes to inspection machinery for magics Now that magics are generated via decorators, the inspection machinery wasn't finding data about them such as source code. Fixes that along with some refactoring, cleanup and test additions. Closes ipythongh-1799.
Now that magics are generated via decorators, the inspection machinery wasn't finding data about them such as source code. Fixes that along with some refactoring, cleanup and test additions.
Closes gh-1799.