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.

Author skreft
Recipients benjamin.peterson, skreft
Date 2011-11-07.05:22:33
SpamBayes Score 2.8961702e-08
Marked as misclassified No
Message-id <1320643354.54.0.319680461208.issue13362@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-11-07 05:22:34skreftsetrecipients: + skreft, benjamin.peterson
2011-11-07 05:22:34skreftsetmessageid: <1320643354.54.0.319680461208.issue13362@psf.upfronthosting.co.za>
2011-11-07 05:22:33skreftlinkissue13362 messages
2011-11-07 05:22:33skreftcreate