Issue 31462: Remove trailing whitespaces (original) (raw)

Issue31462

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/75643

classification

process

Created on 2017-09-14 05:50 by serhiy.storchaka, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (5)
msg302140 - (view)	Author: Serhiy Storchaka (serhiy.storchaka) *	Date: 2017-09-14 05:50
Proposed PR removes trailing whitespaces from CPython source files. Some of them were added since the last trailing whitespaces removing. Some text files were omitted in previous trailing whitespaces removings. Now I consider them safe to cleanup.
msg302144 - (view)	Author: Serhiy Storchaka (serhiy.storchaka) *	Date: 2017-09-14 06:38
New changeset 13ad3b7a82bf56d803fbe48ee5df6c4b08986c78 by Serhiy Storchaka in branch 'master': bpo-31462: Remove trailing whitespaces. (#3564) https://github.com/python/cpython/commit/13ad3b7a82bf56d803fbe48ee5df6c4b08986c78
msg302173 - (view)	Author: Terry J. Reedy (terry.reedy) *	Date: 2017-09-14 15:31
I plan to backport the idlelib changes. Do you prefer than I try to include other files (by using cherry-pick) or only do idlelib (probably much easier)?
msg302180 - (view)	Author: Serhiy Storchaka (serhiy.storchaka) *	Date: 2017-09-14 16:38
Usually we don't backport such kind of changes. And I afraid that cherry-picking would be with many conflicts, because many changes are in new code. The idlelib changes are more harmless, since they are in text files.
msg302229 - (view)	Author: Terry J. Reedy (terry.reedy) *	Date: 2017-09-15 02:52
New changeset 93d5f91fff5740b463980797a04f3d5f1d5f1a51 by Terry Jan Reedy in branch '3.6': [3.6] bpo-31462: IDLE - remove trailing whitespaces (GH-3564) (#3594) https://github.com/python/cpython/commit/93d5f91fff5740b463980797a04f3d5f1d5f1a51