Bartosz Sławecki

@Lucretiel

Example: Having ```py # foo.py from autocommand import autocommand @autocommand(__name__) def main(arg: int): pass ``` the `python -m foo m` command correctly reports an error: ``` usage: foo.py [-h] arg...

> [!Note] > It was a known issue: https://github.com/Lucretiel/autocommand/blob/acff23e565ae90c44cb2d10ecdd729d25949e2b7/src/autocommand/autoparse.py#L60-L61

Related to https://github.com/Lucretiel/autocommand/issues/30.

> PEP 563 appears to have been superseded, due to backwards compatibility issues, so I'm closing this for now. Feel free to re-open if PEP is restored. Strong -1 on...

I suggested myself as a maintainer of typeguard and reached out to Alex directly. Once I'm approved, I'll manage to solve the concerns presented in this issue.

I reproduced this with the following virtual environment: ```shell annotated-types==0.7.0 av==12.2.0 certifi==2024.7.4 charset-normalizer==3.3.2 click==8.1.7 click-default-group==1.2.4 cloup==3.0.5 decorator==5.1.1 glcontext==2.5.0 idna==3.7 isosurfaces==0.1.2 jinja2==3.1.4 lxml==5.2.2 manim==0.18.1 manim-slides==5.1.7 manimpango==0.5.0 mapbox-earcut==1.0.1 markdown-it-py==3.0.0 markupsafe==2.1.5 mdurl==0.1.2 moderngl==5.10.0...

Downgrading to `pyside6==6.5.2` fixed the issue. CC @pacaunt @jeertmans maybe make an extra with pyside6 pinned to 6.5.2?

I recorded "before and after" with asciinema for `poetry add pydantic` and `poetry remove pydantic` commands in the poetry repo. What concerns me is that the operation messages starting with...

I've taken on the challenge of fixing this. It's my first time working with mypy, so bear with me or let me know if someone else fixes it.