[issue13362] Many PEP 8 errors

Benjamin Peterson added the comment: 2011/11/7 skreft : > > skreft added the comment: > > Hi all again: > > in the original posting of this issue,  I asked what would be the best way to > address this issue. Additionally I proposed to use existing tools to check > the current code. These tool

[issue13362] Many PEP 8 errors

Martin v. Löwis added the comment: skreft: I can see nothing wrong by having a website that lists PEP 8 violations in the standard library - feel free to create one on wiki.python.org. Your preferred solution of having automated tests is not feasible. Taking punycode.py (sic) as an example (o

[issue13362] Many PEP 8 errors

Raymond Hettinger added the comment: I concur with Benjamin. This is a waste of time and a potential source of new errors. -- nosy: +rhettinger ___ Python tracker ___ _

[issue13362] Many PEP 8 errors

skreft added the comment: Hi all again: in the original posting of this issue, I asked what would be the best way to address this issue. Additionally I proposed to use existing tools to check the current code. These tools could be easily added to the tests in a non failing mode, so develope

[issue13362] Many PEP 8 errors

Benjamin Peterson added the comment: Generally, we don't do style cleanups for the sake of style cleanups. -- nosy: +benjamin.peterson resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue13362] Many PEP 8 errors

New submission from skreft : Hi all, I was reading Python's source code and was surprised to find many PEP 8 errors. The file that I found specially non PEP8 compliant is Lib/encodings/punnycode.py, but there are many others that are not compliant. I think that this issue should be addressed,