@JulienPalard: Backport status check is done, and it's a success ✅ .

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.

@ned-deily thanks for the feedback. I think it's ok for 3.6 (not as a language bug fix I agree, but as a usability fix): I encontered the issue multiple time by using "python3 -m http.server", typically to test the doc. I expect other people to find the bug too.

OK, I guess this is OK for 3.6. If you want to address some or all of the comments in a follow-on PR for master and 3.7, that's fine.

As discussed with @vstinner, I'll finally won't backport it to 3.6: introducing a new class (changing the API) is something we should not do. It's still fixable without changing the API by hiding the ThreadedHTTPServer class in the test function if someone want to do it.

@JulienPalard @miss-islington Thanks for this PR. However what do you think about changing the class name http.server.ThreadedHTTPServer to http.server.ThreadingHTTPServer, in order to be consistent with the already existing classes:

• socketserver.ForkingTCPServer;
• socketserver.ForkingUDPServer;
• socketserver.ThreadingTCPServer;
• socketserver.ThreadingUDPServer.