Fwd: [Python-Dev] [Announcement] New mailing list for code quality tools including Flake8, Pyflakes and Pep8
Hey all, Alfredo brought up an excellent question on python-dev following the announcement of our new list. I don't think there are any pyflakes/pylint/etc. checks run against CPython currently. Has anyone thought about doing this and seeing how many errors or warnings there are? I would hope there aren't that many, but with modules like unittest I could see pep8 giving a lot of warnings. ---------- Forwarded message ---------- From: Charles-François Natali <cf.natali@gmail.com> Date: Thu, Apr 4, 2013 at 12:57 AM Subject: Re: [Python-Dev] [Announcement] New mailing list for code quality tools including Flake8, Pyflakes and Pep8 To: Alfredo Solano Martínez <asolano@icai.es> Cc: Ian Cordasco <graffatcolmingov@gmail.com>, Python Dev <Python-Dev@python.org>
Are you planning to cover the code quality of the interpreter itself too? I've been recently reading through the cert.org secure coding practice recommendations and was wondering if there has is any ongoing effort to perform static analysis on the cpython codebase.
AFAICT CPython already benefits from Coverity scans (I guess the Python-security guys receive those notifications). Note that this only covers the C codebase. cf
On 4/4/13 4:39 PM, Ian Cordasco wrote:
Hey all,
Alfredo brought up an excellent question on python-dev following the announcement of our new list. I don't think there are any pyflakes/pylint/etc. checks run against CPython currently. Has anyone thought about doing this and seeing how many errors or warnings there are? I would hope there aren't that many, but with modules like unittest I could see pep8 giving a lot of warnings.
basically, most of the stdlib is non-pep8 ;)
---------- Forwarded message ---------- From: Charles-François Natali <cf.natali@gmail.com> Date: Thu, Apr 4, 2013 at 12:57 AM Subject: Re: [Python-Dev] [Announcement] New mailing list for code quality tools including Flake8, Pyflakes and Pep8 To: Alfredo Solano Martínez <asolano@icai.es> Cc: Ian Cordasco <graffatcolmingov@gmail.com>, Python Dev <Python-Dev@python.org>
Are you planning to cover the code quality of the interpreter itself too? I've been recently reading through the cert.org secure coding practice recommendations and was wondering if there has is any ongoing effort to perform static analysis on the cpython codebase. AFAICT CPython already benefits from Coverity scans (I guess the Python-security guys receive those notifications). Note that this only covers the C codebase.
cf _______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
-- Tarek Ziadé · http://ziade.org · @tarek_ziade
About PEP8, see also: http://bugs.python.org/issue16960 IIRC Georg Brandl ran Pyflakes on the stdlib few years ago, and he removed some unused imports and constructs. Some other developers have also fixed errors reported by Pyflakes. -- Florent 2013/4/4 Tarek Ziadé <tarek@ziade.org>
On 4/4/13 4:39 PM, Ian Cordasco wrote:
Hey all,
Alfredo brought up an excellent question on python-dev following the announcement of our new list. I don't think there are any pyflakes/pylint/etc. checks run against CPython currently. Has anyone thought about doing this and seeing how many errors or warnings there are? I would hope there aren't that many, but with modules like unittest I could see pep8 giving a lot of warnings.
basically, most of the stdlib is non-pep8 ;)
---------- Forwarded message ---------- From: Charles-François Natali <cf.natali@gmail.com> Date: Thu, Apr 4, 2013 at 12:57 AM Subject: Re: [Python-Dev] [Announcement] New mailing list for code quality tools including Flake8, Pyflakes and Pep8 To: Alfredo Solano Martínez <asolano@icai.es> Cc: Ian Cordasco <graffatcolmingov@gmail.com>, Python Dev <Python-Dev@python.org>
Are you planning to cover the code quality of the interpreter itself
too? I've been recently reading through the cert.org secure coding practice recommendations and was wondering if there has is any ongoing effort to perform static analysis on the cpython codebase.
AFAICT CPython already benefits from Coverity scans (I guess the Python-security guys receive those notifications). Note that this only covers the C codebase.
cf ______________________________**_________________ code-quality mailing list code-quality@python.org http://mail.python.org/**mailman/listinfo/code-quality<http://mail.python.org/mailman/listinfo/code-quality>
-- Tarek Ziadé · http://ziade.org · @tarek_ziade
______________________________**_________________ code-quality mailing list code-quality@python.org http://mail.python.org/**mailman/listinfo/code-quality<http://mail.python.org/mailman/listinfo/code-quality>
participants (3)
-
Florent -
Ian Cordasco -
Tarek Ziadé