Skip to content
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

Outputting function as root dd/dump object does not behave consistently #13

Closed
brodriguez8774 opened this issue Mar 30, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@brodriguez8774
Copy link
Collaborator

Seems to be related to call-stack examination.

Currently seems to (generally) output correctly for module-level functions, but breaks with class-level.

Before closing issue, should also examine functions in nested classes, as well as outputting a default value in event of future call-stack examination issues.

@brodriguez8774 brodriguez8774 added the bug Something isn't working label Mar 30, 2022
@DJBarnes
Copy link
Owner

DJBarnes commented Apr 6, 2022

Currently works when dumping a function and a function on an object. But fails to find the function name if the function is deeper within an object. EX: dump(obj_a.prop_b.do_work) will not be able to find the name of do_work. But, should we really be dumping things in this manner anyway? It seems more likely to just dump obj_a and then inspect.

@DJBarnes
Copy link
Owner

Was determined that they should be functionality that is included. Should be fully fixed as there is an entirely new way of getting the dumped variable's name that is way simpler and handles making nested calls inside the dump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants