Conversation
|
Actually, I am not sure if this is worth it, unless we had some kind of git pre-commit warn/error hook in place to make sure we are clean from trailing whitespaces. This is quite pedantic in practice, and we might just want to close without merging. |
|
Yeah, a lot of changes. It all depends on you, maintainers, whether you want this or not. My IDE is hardly configured to remove any trailing spaces automatically and add a new line at the end of the file if there is none. So it makes it a bit difficult to me to restore whitespaces before commit, but I'll align with whatever decision you make. I'm pretty sure you can add something like Travis CI and make a check on each incoming PR whether it conforms to the rules you'd like it to conform. This way even if not everyone have pre-commit hook added, you can still avoid merging something that introduces new redundant whitespaces. |
|
Closing this, not useful. |
Remove trailing whitespaces on a number of .py, .js and .rst files in the repository.
This was motivated by #5464 (comment)
Done by running
sed -i '' -e's/[[:space:]]*$//' "$1"on the input files.