python-trio / python-trio/flake8-async

Warn if `except*` exceptions are stringified

Open
#302 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

new rule
Dominant language
Python
Stars
26
Forks
10
PR merge metrics
No merged PRs in 30d

Description

except* FooError as e: produces an ExceptionGroup with an empty message, so str(e) == " (1 sub-exception)" (or whatever other number). It'd be nice to detect this (including in f-strings), and recommend using the repr instead.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test entry point is named; start by locating the existing checks for exception stringification in flake8-async. The work is done when stringification of an except* exception, including in f-strings, is detected and the diagnostic recommends using repr instead.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.