-
Notifications
You must be signed in to change notification settings - Fork 14
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
supporting callables? #7
Comments
I suspect the problem is knowing whether a callable supports keyword arguments. The One possibility is to take the Erlang approach and just "let it crash" if it turns out a callable doesn't support keywords. Trouble is the signal in question might be a very rare one and it'll only be some time later that you find there's a problem. I made a fork of |
Could you curry your callable maybe ?
|
Okay, I'm a little lost, what is meant by "curry your callable"? |
I was thinking of this curry command
https://github.com/django/django/blob/master/django/utils/functional.py#L10
Just suggesting as a temporary workaround.
|
nifty little module!
Would it be possible to support callables instead of just functions - I ran into this use case:
Basically I wanted to specialize a signal handler from a generic function with a partial application in between. Error is:
The text was updated successfully, but these errors were encountered: