[Python-Dev] improving quality (original) (raw)

Michael Hudson mwh at python.net
Sat Apr 1 15:59:55 CEST 2006

"Chris AtLee" <chris at atlee.ca> writes:

On 3/28/06, Neal Norwitz <nnorwitz at gmail.com> wrote:

We've made a lot of improvement with testing over the years. Recently, we've gotten even more serious with the buildbot, Coverity, and coverage (http://coverage.livinglogic.de). However, in order to improve quality even further, we need to do a little more work. This is especially important with the upcoming 2.5. Python 2.5 is the most fundamental set of changes to Python since 2.2. If we're to make this release work, we need to be very careful about it. This reminds me of something I've been wanting to ask for a while: does anybody run python through valgrind on a regular basis? I've noticed that valgrind complains a lot about invalid reads in PyObjectFree. I know that valgrind can warn about things that turn out not to be problems, but would generating a suppresion file and running all or part of the test suite through valgrind on the buildbots be useful?

Have you read Misc/README.valgrind?

I don't know if anyone runs Python under valgrind regularly though.

Cheers, mwh

-- The ultimate laziness is not using Perl. That saves you so much work you wouldn't believe it if you had never tried it. -- Erik Naggum, comp.lang.lisp

More information about the Python-Dev mailing list