Sebastian Rittau
Sebastian Rittau
This makes sense to me. It might even make sense to use two type variables for setting and getting. On the other hand, I don't know what the impact on...
It looks to me that `memoryview` should be generic over the format. That said, I'm uncomfortable making a change like this as long as we don't have type var defaults....
Reopening. We should at least document why we use `Any` in the PR, instead of `object`. That said, I'd prefer if mypy would fix their bug, or alternatively that mypy...
In this particular case, fastapi doesn't seem to use the type stubs for runtime type checking, instead using the runtime classes. I'm not sure that is even easily possible. That...
That should help and is the correct long-term solution anyway, as redis is moving towards including types themselves.
Would it make sense to add an option to disable these checks, so we could disable them in CI for now?
@ilevkivskyi @JukkaL Can one of you log in as user typeshed_bot on PyPI and yank all released versions of `types-typing-extensions` and also `types-pkg-resources` (while you're at it). I think there...
`_TemporaryFileWrapper` doesn't extend any, but has a `__getattr__()` returning `Any`. This matches the implementation, and would be hard, but not impossible to change: We could look into the actual file...
`Callable[[], object]` is the better option. It also potentially avoids an `Any` import.
I've come to see `_typeshed` as a staging ground for `typing_extensions`, now that we seem to have consensus that moving some stuff over seems desirable.