Brian Schubert
Brian Schubert
Related: #17008
Hmm, the build failure due to warnings from _other_ PEPs is puzzling. I see that the last build [used Sphinx v8.2.3](https://app.readthedocs.org/projects/pep-previews/builds/29481110/#285352085--45) whereas a previous successful build from 30 minutes ago...
>but I don't think it's possible. I think it might be? I saw something similar in the SQLAlchemy tests: https://github.com/sqlalchemy/sqlalchemy/blob/main/.github/workflows/run-test.yaml#L121
> Can/should we add a warning in a failing case? I think we get this for free - it seems an error annotation still gets emitted for the failing step...
I recently discovered that there's some kind of Codecov.io integration set up for the python GitHub organization: https://app.codecov.io/gh/python. Maybe we could use this for the typing_extensions coverage workflow? Some nice...
Just confirming (a little late), the starlette hit looks correct to me too. I think it boils down to something like this: ```python from collections.abc import Callable from typing import...
Looks reasonable, feel free to send a PR! This will involve typing `process_util` as an instance of a private callable type that also defines `cache_clear`.
No public API changes
I looked through the PEP and found a few other editorial issues (e.g. a mispellled word ("deaply"->"deeply"), a repeated article ("in a a similar"), more typos in examples). Would a...