@sobolevn Test with buildbots. Thanks

🤖 New build scheduled with the buildbot fleet by @sobolevn for commit 10db2f2 🤖

If you want to schedule another build, you need to add the "🔨 test-with-buildbots" label again.

Thanks for picking this work up!

cc @asvetlov The build-bots passed and are all green, ready for merge!

🤖 New build scheduled with the buildbot fleet by @asvetlov for commit 10db2f2 🤖

If you want to schedule another build, you need to add the "🔨 test-with-buildbots" label again.

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@asvetlov I am busy currently so I suggest to land this and I'll prepare a PR for docs shortly.

This failure looks related: https://buildbot.python.org/all/#/builders/178/builds/435

@sobolevn why do you think so?
I read the following summary as everything is almost fine, test_concurrent_futures alters the environment.
The concurrent futures are not affected by this PR, I read this error as unrelated.

1 test altered the execution environment:
    test_concurrent_futures
14 tests skipped:
    test_devpoll test_ioctl test_kqueue test_msilib test_nis
    test_readline test_startfile test_tix test_tk test_ttk_guionly
    test_winconsoleio test_winreg test_winsound test_zipfile64
1 re-run test:
    test_unittest
    ```

It is clearly unrelated.

@asvetlov: Please replace # with GH- in the commit message next time. Thanks!