Benjamin Peterson <benja...@python.org> added the comment: 2011/11/7 skreft <rep...@bugs.python.org>: > > skreft <skr...@gmail.com> 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 developers who modify the code, could know that the source > code does not follow the coding style and probably she/he could improve the > code. This tool would also help newcomers to contribute better code. > > Unfortunately, by the decision of rejecting this issue without even answering > the full issue, I conclude that the Python team is not willing to improve its > own basecode. > > I repeat my posture, python source code should be a model of a python > project, hence if there are tools that can ensure or improve the quality of > the project, they should be incorporated to the development process.
It can be cleaned up and modernized as it is changed for some other purpose. Ultimately, it doesn't matter in the least bit how many lines are between inline comments and other code, which seems to be principally what pep8.py cares about in Lib/*. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13362> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
