Michael H

> Maybe that could be documented as restoring the original POSIX-like signature? I added the setter in case it was ever used after defining the command, as rarely as that...

As long as this only prevents shadowing commands (and not functions) this won't be a large issue. With the prevention of shadowing all functions in a class built into this,...

> I'm saying that negated types will not compose with existing typing features. The feature would require many caveats and special cases limiting where it can be used. > >...

To add another detraction to this, regex in annotations to be checked *statically* is probably not a great idea for similar reasons that type checkers don't evaluate expressions. Pathological patterns,...

When testing this rule to see if this rule should be enabled for my own projects, the current implementation of this rule needs more nuance that just classmethods. I understand...

I don't mind if we have a section of the docs which is strictly for internal Red use, but I think there's a larger issue doing this somewhat masks. We...

I can put a draft PR up later today for modification and use with 3.2 which may make it a bit more clear the level of changes I'd be arguing...

I think the parts of this we were most concerned about for 3.2 are handled at this point, but I don't think this is fully resolved yet.

Changing `list` to `Sequence` is often incorrect. `MutableSequence` is less likely to be a problem, but even that can cause issue if you are relying on the sequence being an...

I commented on this briefly where it came up for someone in the python discord's typing channel. I believe that this is neither the typeshed being wrong nor pyright being...