-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Keyword completion in options #2485
Comments
I'll assign this to 1.10 as it would be nice to have a replacement for |
An alternative to docstring hackery to make this work would be to replace |
Maybe I am misremembering but that approach is essentially piggy-backing off param to set the docstrings for you. |
Right, I think that's preferable over re-implementing custom docstring hackery for this particular case, but I'll leave that up to whoever implements this. |
I'm fine with this (and happy to implement it) though if I remember right, you were objecting to callable objects that look like methods at one point. :-) |
No I was objecting to using nested APIs like redim everywhere, |
Sure though simply by being parameterized means nested things like |
True, not ideal I guess, maybe a custom solution is preferable. |
Implemented in #3173 |
Given that we want to reduce the use of the
%%opts
magic, it would be good if the.options
method could tab-complete the available keywords.This is possible to do in IPython but it will involve some hackish dynamic updates of docstrings. I'm wondering if this could be done by a safe utility in the constructor, ideally in one place at the
Dimensioned
level...The text was updated successfully, but these errors were encountered: