Peter Bierma

Yeah, you're right, it should be `class range(start, stop, step=1, /)` on the functions page. PR welcome, we're always looking for new contributors :)

> Shouldn't the `functions` and the `stdtypes` page be kept in sync, i.e. read exactly the same? I thought about that, but it doesn't seem like the functions page uses...

I think the most reasonable fix would be to change [this line](https://github.com/python/cpython/blob/6f26d496d3c894970ee18a125e9100791ebc2b36/Python/codecs.c#L1529) to something like: ```c return PyStatus_Error("Failed to import encodings module. Are you sure PYTHONHOME is correct?"); ``` PR...

You could, but what makes `PYTHONHOME` special is that it's "required" to do anything with the interpreter--explicitly messing with other variables is the user's fault IMO.

OK, I think I understand Steve's point of view now. There's precedent for this in the stdlib: we're using `sys.implementation` in `platform` here: https://github.com/python/cpython/blob/10c4c95395771fb37e93811aaace42f026c16de5/Lib/platform.py#L889 I'm only comfortable with `sys.implementation._architecture` if...

If we go for `sys.architecture`, then there's no need for an `_architecture` attribute at all.

Yeah, initially that wasn't a call to `PyUnicode_AsUTF8` and I just forgot to remove the `free` call when I changed it. Good catch!

Are you still working on this? I'm happy to take a stab at some of these.

> stdlib interpreter-core docs topic-repl 3.13 3.14 3.15 We try not to mix `stdlib`, `interpreter-core`, and `docs`. Let's pick one.

I think the best option is to wait for items in C using a `PyEvent` rather than polling. There shouldn't be any need for an extra lock.