-
Notifications
You must be signed in to change notification settings - Fork 12
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
Nicer formatting for missing arguments #13
Comments
It also seems that each function has it's warning printed twice, and for several they have I hope this is helpful, happy to try to debug a bit |
Thanks for the kind words ! And, sorry, most of thos print statements are for debug, i'm using But yes, I should that that behind a "verbose" fag at least :-) |
it somewhat difficult to know which function the warning refers to: only the module and function name are given, but it would be really useful to also include the line number. Also, in the case of a module with multiple classes and a shared method name (e.g. |
looking into it, the duplicated messages happens because Lines 802 to 824 in 1be3565
Also, if instead of passing |
This is an awesome project :)
I just started applying it (mpl-extensions/mpl-interactions#168) after I saw your PR to napari. An overall the experience has been great. One potential improvement would be to make the formatting of the warning for missing parameters nicer:
currently it looks like this:
And the majority of space is devoted to
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:513 in |
which isn't super important information for fixing my missing arguments (of which there are shockingly many 😢 edit: turns out in part because I document several kwargs that are passed through to matplotlib. Though that's probably not very numpydocy... ) It would be awesome if this instead had a hierarchical organization. Something like:The text was updated successfully, but these errors were encountered: