-
Notifications
You must be signed in to change notification settings - Fork 579
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
YapfBear adds redundant newline to empty files #739
Comments
Thanks for reporting this issue! A coalaian will look at it soon. |
there's no workaround for this |
AbdealiLoKo
added a commit
that referenced
this issue
Aug 31, 2016
Yapf cannot handle zero-byte files correctly, because it adds a newline into the file when correcting. Hence we ignore zero byte files completely as they anyway do not have code to format. Fixes #739
AbdealiLoKo
added a commit
that referenced
this issue
Sep 1, 2016
Yapf cannot handle zero-byte files correctly, because it adds a newline into the file when correcting. Hence we ignore zero byte files completely as they anyway do not have code to format. Fixes #739
AbdealiLoKo
added a commit
that referenced
this issue
Sep 2, 2016
Yapf cannot handle zero-byte files correctly, because it adds a newline into the file when correcting. Hence we ignore zero byte files completely as they anyway do not have code to format. Fixes #739
CC @netman92 because we'll need it just so you know a fix is on the way, I'll release it todayish |
sils
pushed a commit
that referenced
this issue
Sep 2, 2016
Yapf cannot handle zero-byte files correctly, because it adds a newline into the file when correcting. Hence we ignore zero byte files completely as they anyway do not have code to format. Fixes #739
gosom
pushed a commit
to gosom/coala-bears
that referenced
this issue
Jul 15, 2017
Yapf cannot handle zero-byte files correctly, because it adds a newline into the file when correcting. Hence we ignore zero byte files completely as they anyway do not have code to format. Fixes coala#739
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
type/bug
The text was updated successfully, but these errors were encountered: