-
Notifications
You must be signed in to change notification settings - Fork 430
Remove @util.positional from the authorize() wrapper. #196
Remove @util.positional from the authorize() wrapper. #196
Conversation
Your change LGTM. The coverage decrease is just an unavoidable math fact caused by removing 1 line:
Regarding your comment
I'm not sure how quickly a new version will be propagated to the SDK. |
@nathanielmanistaatgoogle You are a go to merge, note that the method being monkey patched (ewwww I wish PS I now have merge privileges but just wanted to make sure someone else saw. |
Thanks for the contribution! (1) Please rewrite your commit message to conform to chris.beams.io/posts/git-commit/#seven-rules. (2) You describe this change as a fix, so how about a regression test? (3) How much digging did you do on this? In what commit was the original error made? What line of thinking or false assumption is the root cause of the mistake? Is there some larger lesson we should learn or action we should take beyond just deleting a single method decoration? |
Since the original method does not have a constraint on positional parameters, its wrapper should not either. See http://stackoverflow.com/questions/18126157/appengine-warning-during-python-app-update/30469210 for a case where this is producing annoying warnings.
(1) Updated the commit message. (2) Added a regression test. (3) To be honest, I think the cause of the mistake is using the |
Remove @util.positional from the authorize() wrapper.
FYI that regression test has side-effects. |
That it does; I should have caught that. |
Yes sorry, I meant to add teardown logic. I'll send another PR with that. |
Remove unwanted side-effect in test_oauth2client introduced by #196.
Since the original method does not have a constraint on positional parameters,
its wrapper should not either. See
http://stackoverflow.com/questions/18126157/appengine-warning-during-python-app-update/30469210
for a case where this is producing annoying warnings.