Documenting about the applied patches

[rhvarrier]

I would like to use this fork in production but for that couldn't find any documentation about the patches made to the original source code in order to evaluate what changes were made.
More generally speaking is this fork production ready, i.e. reliable and fully tested against the original cpython repo.

[lazka]

That's a tricky question.

For the documentation you can see the commits on the default branch until you hit the upstream commits. Some older commits lack context though as we didn't start this in git.

As for testing, this gets some regular usage in MSYS2 for building various packages and running some applications. We also run the tests suite in CI, but we have skipped quite a few tests that always failed.

There are lots of things that could be improved, but we are lacking the manpower/time to do so. And keeping it up-to-date with upstream CPython is a task on its own..

If you still give it a try let us know if you find any issues.