Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork940
Add an output_nostrip kwarg to Git.execute#77
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Add an output_nostrip kwarg to Git.execute#77
Uh oh!
There was an error while loading.Please reload this page.
Conversation
The last line of the output normally is stripped if it is empty. Ifoutput_nostrip is True, this behavior is disabled. This can be importantwhen constructing patches e.g. using the diff command.
Thanks for the fix. |
I tried this but it does not feel right for me. IMHO I try to come up with some test cases. |
Thanks for the unit test, its much appreciated. Besides that, I don't think one can compare a CLI with an API. The In APIs I consider it bad practice to negate something in the first place, and then have double-negations in the code like |
Following up in#79 |
The last line of the output normally is stripped if it is empty. If
output_nostrip
isTrue
, this behavior is disabled. This can be important when constructing patches e.g. using thediff
command.