Remaining bare `except:` / swallowed exceptions in tests/ and src/ (Codacy + hidden failures)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 45/100
- Issue-Typ
- Refactoring
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- python
- Bereich
- computer-vision, devtools, testing-qa
Rechercherichtung
Start with #114's PR description and the listed files: tests/test_camera.py, tests/base/test_base_color.py, tests/test_ros.py, tests/conftest.py, and the named src locations. Run each protected test snippet on OpenCV 4 and 5, then review the exception sites and mutation-check that tests fail when behavior is broken. Done means the findings are addressed in focused PRs, the color.py message has a test, and Ruff rules E722, BLE001, and S110 can be enabled.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Follow-up to #51 / #114, which fixed the bare except: pass pattern in tests/test_image_point_features.py. Inventory of what remains as of 2026-10-03 (main at 770a031a). These are likely contributing to the Codacy B grade (Pylint/Pyflakes bare-except and try/except/pass/W0702/W0703-type findings, see #41) and, in tests, hide real failures.
Why it matters
In tests, a bare except: also swallows the AssertionError from assert*, so the test can never fail. Fixing the same pattern in #114 showed that several of those tests had been calling APIs that don't exist (Image.SURF, corners, getpixel, concat), so expect similar findings here: fix by running each snippet unprotected on OpenCV 4 and 5, rewriting against the real API with direct assertions, and mutation-checking that the test now fails when the code is broken (see #114's PR description for the method).
tests/
| File | bare except: |
except Exception + pass/continue |
|---|---|---|
tests/test_camera.py |
11 | 8 |
tests/base/test_base_color.py |
3 | 1 |
tests/test_ros.py |
0 | 3 |
tests/conftest.py |
0 | 2 (probably legitimate GUI-suppression; review rather than blanket-remove) |
src/
| Location | Issue | Suggested fix |
|---|---|---|
base/color.py:966 and :976 (rgb2xyz-style white/primaries lookup) |
bare except: around a dict lookup, then raise ValueError("unknown white value, must be one of" ", ".join(...)). Real bug: the two adjacent string literals concatenate first, so ", ".join(...) uses the whole sentence as the separator; the error message is garbled. |
except KeyError: and build the message with an f-string: f"unknown white value, must be one of {', '.join(_whites)}", plus a test that checks the message |
base/findpeaks.py:119 |
bare except: around Polynomial.fit, then print + continue |
catch the specific exceptions Polynomial.fit raises for a neighbourhood falling off the data; use warnings.warn rather than print |
base/imageio.py:1033 (set_window_title) |
bare except: pass |
except (AttributeError, RuntimeError): (backends without a window manager) |
Camera.py, ImageProcessing.py, base/imageio.py |
one except Exception: pass/continue each |
review each: narrow the exception type or log |
Suggested approach
Separate small PRs: (1) color.py message bug + test (src, real fix), (2) other src sites, (3) tests/test_camera.py, (4) tests/base/test_base_color.py and the rest. Add E722 (bare except) and BLE001/S110 (try-except-pass) to the ruff rule set once clean so it can't regress (see the typing/lint cluster, #40/#41).
Related: #41, #51, #113
- Vorherrschende Sprache
- Python
- Sterne
- 224
- Forks
- 31
- Ø Merge
- 1 T. 22 Std.
- Gemergte PRs (30 T.)
- 29
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus petercorke/machinevision-toolbox-python
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 76/100
petercorke/machinevision-toolbox-python#160 ·
Maintainer antworten meist innerhalb von 1 Tag
-
tech-debt
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 39/100
petercorke/machinevision-toolbox-python#159 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Image.draw_* fail on images from Image.Read: pixel data is not C-contiguous (cv2 line/circle/putText layout error)Evtl. vergeben @petercorke hat das heute übernommen. Offenbug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 35/100
petercorke/machinevision-toolbox-python#158 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 42/100
petercorke/machinevision-toolbox-python#157 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
petercorke/machinevision-toolbox-python#152 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in petercorke/machinevision-toolbox-python
Ähnliche Issues
-
infrastructure
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
khuisman/mcp-gee-sweet#1152 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
backroom bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ditto-assistant/ditto-subnet#3069 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
open-webui/open-webui#32901 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
0.3.3 bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag