Sebastian Rittau

`typing.IO.write()` as well as basically all classes in the stdlib (especially the base classes in `io`) return an `int`.

I'm unwilling to change the protocol. As the primer hits show, there is no problem with returning `int`, unless you use `codecs` directly, which isn't recommended anyway. Returning the number...

And anyway, this discussion is off topic for this PR. `_typeshed.SupportsWrite` should go, no matter whether `io.Writer` is changed or not.

> I think we should aim to give users of type checkers the best experience possible, so I'm not sure why we should accept any mypy_primer fallout here unless there's...

I've answered these arguments in the CPython PR. As I said before, I believe (sync) `write()` methods are supposed to return the number of items written, a convention that goes...

Thanks! `stubs/gdb/METADATA.toml` needs to be updated to the correct version as well. Also, for review purposes, is there some way to view the changes to the Python API between the...

@oltolm Our CI still complains about a few symbols that are not available at runtime: https://github.com/python/typeshed/actions/runs/15323229467/job/43111418230?pr=13923 Are you sure these items exist in gdb 16.3? In that case, these items...

There are some problems I can see: * Stubs lag behind the implementation, sometimes considerable. In case of SemVer-like packages, where typeshed uses `a.b.*` versions, this means that packages that...

We can't update pyright due to a bug: microsoft/pyright#10487 microsoft/pyright#10484

It seems that `curframe_locals` actually does not exist in 3.13, at least according to stubtest. I'm not totally sure what's going on here.