Remove coverity from the DevGuide

conf.py

@@ -114,11 +114,9 @@
 rediraffe_redirects = {
     # Development Tools
     "clang.rst": "development-tools/clang.rst",
-    "coverity.rst": "development-tools/coverity.rst",
     "gdb.rst": "development-tools/gdb.rst",
     # Advanced Tools was renamed Development Tools in gh-1149
     "advanced-tools/clang.rst": "development-tools/clang.rst",
-    "advanced-tools/coverity.rst": "development-tools/coverity.rst",
     "advanced-tools/gdb.rst": "development-tools/gdb.rst",
     # Core Developers
     "coredev.rst": "core-developers/become-core-developer.rst",

core-developers/experts.rst

@@ -319,7 +319,6 @@ buildbots           zware, pablogsal
 bytecode            benjaminp, 1st1, markshannon, brandtbucher, carljm, iritkatriel
 context managers    ncoghlan
 core workflow       Mariatta, ezio-melotti, hugovk, AA-Turner
-coverity scan       tiran, Yhg1s
 cryptography        gpshead, dstufft
 data formats
 database            malemburg

development-tools/clang.rst

@@ -54,7 +54,7 @@ A complete list of sanitizers can be found at `Controlling Code Generation
 
 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`_,
 etc.
 
 Clang/LLVM setup
@@ -281,3 +281,5 @@ Unfortunately, you won't know what to ignorelist until you run the sanitizer.
 
 The documentation is available at `Sanitizer special case list
 <https://clang.llvm.org/docs/SanitizerSpecialCaseList.html>`_.
+
+.. _Valgrind: https://github.com/python/cpython/blob/main/Misc/README.valgrind

development-tools/index.rst

@@ -8,5 +8,4 @@ Development tools
    clinic
    gdb
    clang
-   coverity
    warnings