Repository navigation
Conversation
|
|
|
I will update some test-cases to ensure |
This is caused by a known limitation in invoke: pyinvoke/invoke#555 See pyinvoke/invoke#666 for a possible future fix
d71a348 to
139f5e8
Compare
|
I've added unit test to cover cases of applying multi decorators (both function and class decorators). |
|
Sorry, Just accidentally clicked the button Request Review. I cancelled the request. Don't want to be rude to ask you review it now. Take your time. Thank you! |
|
Hello @bitprophet, did you see this PR ? I would be fantastic to have support for decorator 😍 |
|
Another voice for getting this in @bitprophet |
|
I'd also like to see this go in :-). FWIW if Python 2.7 compatibility is of prime concern here one could still fall back to use Some helpful discussion (imho) can be found here: https://stackoverflow.com/a/43506509/7379507 |
|
2.0.0 will be out soon & is now using |
I made these changes to implement for:
#246
#399
#555
It's more than 4 years from the date when people found it hard to apply to Invoke
@taskon other@decorator. The root cause of it isinspect.getargspecwhich couldn't handle decorated function. It's also recommended replacing byinspect.signaturefor a "more structured introspection API for callables" from python 3.4.I also keep the compatibility with Python 2.x by using the original function under the name
argspec_python2. Newargspecwill check if it is Python 2 and switch the flow toargspec_python2on runtime.