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.

classification
Title: make standard library PEP8 compliant
Type: enhancement Stage: resolved
Components: Library (Lib) Versions:
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: Friedrich.Spee.von.Langenfeld, r.david.murray
Priority: normal Keywords:

Created on 2013-06-18 09:53 by Friedrich.Spee.von.Langenfeld, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
autopepframework.py Friedrich.Spee.von.Langenfeld, 2013-06-18 09:53
Messages (2)
msg191392 - (view) Author: Friedrich Spee von Langenfeld (Friedrich.Spee.von.Langenfeld) Date: 2013-06-18 09:53
The modules in the standard library aren´t PEP( compliant. I´ve written a script to change this. It uses autopep8.py (must be in the path) and is written for Windows users.
msg191402 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2013-06-18 12:26
Sorry, but this is not the kind of change that we make to the codebase.  It has too many unintended consequences.  (Large portions of the stdlib pre-date PEP8, and thus are not PEP8 compliant.)  We fix some thing when we modify the code involved, but other things (such as API names) will at this point never get fixed, sad to say.
History
Date User Action Args
2022-04-11 14:57:47adminsetgithub: 62453
2013-06-18 12:26:00r.david.murraysetstatus: open -> closed

nosy: + r.david.murray
messages: + msg191402

resolution: rejected
stage: resolved
2013-06-18 09:53:11Friedrich.Spee.von.Langenfeldcreate