All commit authors signed the Contributor License Agreement.

Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply theskip news label instead.

Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply theskip news label instead.

I have created a NEWS entry for this fix, but actually this change has indeed a little impact on Python users, so maybeskip news tag is more appropriate here.

Many tests are failing with a warning - as now theDeprecationWarning is no longer hidden (and as I unedrstand it, the tests run with the equivalent of-Werror).

Many of the failing tests do not fail where one would expect to have more than one thread running. For example, intest_uuid.testIssue8621.

When printing there the number of threads usingthreading.active_count() we get1. However, when investigating further, the number of threads are actually2 - just that one of the threads is not a python thread, and therefore not counted bythreading.active_count().

Therefore, we should find a way to suppress the warning of running a fork within a thread in all the tests that fail. Petr suggests to consider using thesys.unraisablehook (seehttps://vstinner.github.io/sys-unraisablehook-python38.html) in all the places where the tests fail.

If anyone knows where this extra thread comes from, it will be appreciated if this is explained :-)