[issue16960] Fix PEP8 errors everywhere

R. David Murray added the comment: It is valid, but it is not *useful* to have it in the bug tracker as an open bug. All developers are aware that when they touch code for some other reason, they can fix PEP8 errors at the same time. Having an open bug report for it would just clutter the ti

[issue16960] Fix PEP8 errors everywhere

Ramchandra Apte added the comment: It's a valid bug report however difficult or low priority it is. -- ___ Python tracker ___ ___ Pyth

[issue16960] Fix PEP8 errors everywhere

Raymond Hettinger added the comment: FWIW, I concur with Ezio's reasons for rejecting this. -- nosy: +rhettinger ___ Python tracker ___ __

[issue16960] Fix PEP8 errors everywhere

Ezio Melotti added the comment: Several reasons, e.g.: * there's the risk of introducing new bugs; * it makes merging more difficult; * it takes time to produce and review the patches; * it makes hg annotate harder to use; -- ___ Python tracker <

[issue16960] Fix PEP8 errors everywhere

Ramchandra Apte added the comment: Why? This may be low priority. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue16960] Fix PEP8 errors everywhere

Ezio Melotti added the comment: Sorry, but we don't fix style issue unless we are already working on that code for some other reasons. -- nosy: +ezio.melotti resolution: -> rejected stage: -> committed/rejected status: open -> closed type: -> enhancement

[issue16960] Fix PEP8 errors everywhere

Ramchandra Apte added the comment: s/stdlib/everywhere -- components: +None title: Fix PEP8 errors in stdlib. -> Fix PEP8 errors everywhere ___ Python tracker ___ ___