Stanislav Terliakov
Stanislav Terliakov
I pushed the isolated change; all other files are modified by autogen - please run it yourself in whichever way is convenient for you.
Hm, thanks, that might indeed be a `mypy` issue. I filed https://github.com/python/mypy/issues/18525 and convert this to draft for now.
Yes, the two linked PRs are very relevant: #17355 supports `partial` application to `ParamSpec` callables, and without it whole support for ParamSpec+partial is dead. I just resurrected that PR, but...
Wow, only one hit? That should be easy to resolve...
Let's remove that and try to merge this before we introduce another unreachable block:)
Agree with @A5rocks - there was a ticket for `--all-checks` or a similar flag that is a superset of `--strict` and enables all our optional codes, I don't think `all`...
That's an unprecedented behavior for error codes: any existing error code can be used in a suppression comment. I don't think introducing a "meta" error code that isn't usable in...
Also related (and closable by any implementation of this idea) #14143
Even worse, ```python from typing_extensions import Any, TypeIs, reveal_type class C[T]: v: T def is_int(v: object) -> TypeIs[C[int]]: ... def f(c: C[Any]) -> None: if is_int(c): reveal_type(c) # N: Revealed...
Could you elaborate more on your use case? I struggle to understand what `django.config.settings.SECRET_KEY` has to do with multitenancy: `SECRET_KEY` is usually configured per application... It's pretty difficult for some...