-
Notifications
You must be signed in to change notification settings - Fork 28
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
Better handling of callables #15
base: master
Are you sure you want to change the base?
Better handling of callables #15
Conversation
Hi @alexandre, this looks great. It's an oversight on my part that callables aren't supported. I definitely intended for this to work. I'll merge this into the next release. |
I'm glad you did like. I could improve this pull request with more some tasks:
What do you think? would be better I open an issue ? |
Those changes sound great! Please feel free to go ahead and implement them on this pull request. No need to file another issue. |
Ok! :] |
Hello,
Instead to use a function, I prefer to write a class aiming a better description of my analysis rules. So, I defined a callable:
Then, I use it in the
Analysis.then
method:The proof.Analisys._fingerprint is considering only functions and instead any callable like.
TL;DR I got this exception: https://github.com/python/cpython/blob/master/Lib/inspect.py#L624
I think this PR could be an initial step to a better way to handle callable in this method (_fingerprint).
P.S - I'm sorry if I broke some PR rule/template. I would be happy to discuss this point, improve this PR and write more tests if necessary.