Remove coverity from the DevGuide#1411
Conversation
development-tools/clang.rst
Outdated
| Clang and its sanitizers have strengths (and weaknesses). Its just one tool in | ||
| the war chest to uncovering bugs and improving code quality. Clang should be | ||
| used to complement other methods, including Code Reviews, Valgrind, Coverity, | ||
| used to complement other methods, including Code Reviews, Valgrind, |
There was a problem hiding this comment.
Question, do we have more info about "Valgrind"? It was mentioned only once on the entire devguide.
There was a problem hiding this comment.
How to use valgrind? What is it for?
There was a problem hiding this comment.
Valgrind is a tool for finding C-level memory issues, like memory leaks or writes to uninitialized memory.
There was a problem hiding this comment.
It's documented here: https://github.com/python/cpython/blob/main/Misc/README.valgrind
There was a problem hiding this comment.
Interesting, we also have a https://github.com/python/cpython/blob/main/Misc/README.coverity that perhaps should be cleaned up from the repo.
There was a problem hiding this comment.
Yeah I found references to coverity on the CPython repo. In addition to README.coverity,
also Misc\coverity_model.c
There was a problem hiding this comment.
It's documented here: https://github.com/python/cpython/blob/main/Misc/README.valgrind
I updated to link to that doc. Thanks.
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
|
Related CPython PR: python/cpython#124460 |
|
Thanks! |
3 participants
The CPython Coverity Scan hasn't been updated since 2020.
People listed as admins and experts of coverity scan are no longer administering/maintaining it.
On Discord, it was decided to drop this from CPython core workflow.
Closes #1410
📚 Documentation preview 📚: https://cpython-devguide--1411.org.readthedocs.build/