Ned Deily

> I seem to remember that the release process includes building the docs + PDF etc, or perhaps it used to. If this is still the case, can part of...

> See [python/cpython#124489](https://github.com/python/cpython/pull/124489) to alter the build process. Thanks, that looks good to me. The only potential issue I can think of is that there might be users/scripts out there...

I think this brings up another related issue inspired by the above discussion and a [comment in the PR](https://github.com/python/cpython/pull/124489#issue-2546985343): > By just using x.y we are honest that the download...

That's macOS 10.12, not macOS 12. We already depend on `certifi` for users of the python.org macOS installers. We think that the workaround of installing the older version of pip...

Talking with @sethmlarson, I think the best thing to do is to fix the issue in `truststore` and eventually release it in a version of pip. I've offered assistance in...

The only thing I did was to provide a quick workaround for the Python 3.12.5 python.org Python for macOS installer which still supports macOS 10.9 through 10.12. The workaround is...

When this issue was brought up before I recall that using a staging location would cause some problems for the Windows steps of the release process. @zooba, is that right?

@zooba, thoughts?

Thanks for the reminder. The page is now updated. This is an ongoing issue because the updating of the https://www.python.org/doc/versions page, while mentioned in [the release process PEP](https://peps.python.org/pep-0101/), is not...

Thanks for the report. Since it concerns mailing lists and the Usenet gateway, it would be more appropriate as a pythondotorg issue rather than a cpython one.