electric-coder

> typing them as such makes PyCharm lose it's autocompletion This should be a non-concern over having mypy working. Stub those objects separately if you want to keep the autocompletion...

> Note that `TypeIs` allows for intersection type behaviour. That's a surprise, PEP 742 announced in mid-February *just-in-time* to make the final cut in May for Python 3.13... I spend...

Seems to be the exact same problem as explained [in this post](https://stackoverflow.com/q/64588821). In this case you have to think about both autodoc and napoleon working simultaneously and declaring the attributes...

> Doesn't this make the `Attributes:` tag redundant No! The `Attributes:` docstring section still retains its intended functionality. > if I have to put a comment description on the attribute...

> I agree that the enum module is too complicated and has too many features. I disagree, the enum module is excellent and comes with a minimal feature set corresponding...

> ```python > reveal_type(Sig.ABRT) # mypy: Literal[Sig.ABRT]; pyright: int > ``` pyright is wrong. It should obviously be: > ```python > reveal_type(Sig.ABRT) # mypy: Literal[Sig.ABRT] > reveal_type(Sig.ABRT.value) # mypy: int...

> Default configuration The deciding configuration here is autodoc's [`autodoc_preserve_defaults`][1] (notice the docs still say: *"Added in version 4.0: Added as an experimental feature."* although in my experience this functionality...

There's a similar problem reported with square brackets `[` `]` #9704, in general this kind of bug was fixed by #8771.

[As was said by tk0miya][2] (emphasis mine): > - It preserves the default argument values of function signatures in source code **and keep them not evaluated for readability**. and the...

@MKuranowski you didn't remove the greater `>` lesser `