Petr Viktorin

With my distro maintainer hat on: If the docs use `python` everywhere, I think it would be a disservice to users if `python` was not the latest available stable version....

@tiran, http://scan5.coverity.com:8080/ still works if you are logged in, right?

I don't think following `302 Found` redirects is the way to go – some of these are short URLs, and the target URL looks more like an implementation detail. For...

I guess `libpython3d.so` would make sense for consistency, but as Victor says it's not useful in practice. Applications that need to link to an alternate library for debugging can link...

PEP 384 is a historical document, but we could update the implementation. But, as far as I know, what PEP 384 says makes sense for Windows.

(For clarity: support for platforms CPython core devs can't handle can still be maintained externally. The current out-of-date table is probably not useful at all, but as long as non-core...

You are correct. Functions that return borrowed references are tricky to use correctly: you need to ensure that whatever you're borrowing from stays valid, and that its reference stays valid...

The safe thing is to create a new reference after calling `PyList_GetItem` (a function that is problematic because it returns a borrowed reference), or to instead call `PySequence_GetItem` (which returns...

The borrowed reference that's passed as an argument *must not go away* until the called function returns, regardless of other threads. Since the caller must hold a reference, other threads...

The caller doesn't need to know anything about `callee`. It does need to ensure that the reference that it passes to `callee` remains valid until `callee` returns. Maybe misunderstanding about...