gh-153309 Add HTTP QUERY method (RFC 10008) to http library

[mbeijen]

RFC 10008: The HTTP QUERY Method is now a finalized RFC on the Standards track, and the method name has been added to the IANA registry

Add it to http library HTTPMethod enum, too

• Issue: Add RFC 10008: The HTTP QUERY Method #153309

[read-the-docs-community]

Documentation build overview

📚 cpython-previews | 🛠️ Build #33720199 | 📁 Comparing a39fa7e against main (aa533dc)

  🔍 Preview build  

85 files changed · + 3 added · ± 82 modified

+ Added

• library/asyncio-tools.html
• library/tkinter.fontchooser.html
• library/tkinter.systray.html

± Modified

• py-modindex.html
• c-api/exceptions.html
• c-api/float.html
• c-api/frame.html
• c-api/type.html
• c-api/typeobj.html
• c-api/veryhigh.html
• deprecations/index.html
• deprecations/pending-removal-in-3.19.html
• faq/general.html
• and 72 more...

[picnixz]

Don't we need something like do_QUERY in HTTP client etcs? please also check if we need tests for that.

[mbeijen]

Don't we need something like do_QUERY in HTTP client etcs? please also check if we need tests for that.

We have these do_ methods in server, not in the client. And we do not need to add QUERY there, we have this code

cpython/Lib/http/server.py

Line 455 in 1051384

mname = 'do_' + self.command

that automatically parses the method names. We also do not have explicit methods there for do_DELETE and so on.

[sobolevn]

(not a full review)

[picnixz]

(I will do a review tomorrow while I am commuting)

[picnixz]

Overall good.

[mbeijen]

@picnixz you seem to be the most active reviewer on this PR, can you help me move this forward?

[edvilme]

Not a Core Dev but left my little review. Additionally I would look into adding more tests that make sure the actual HTTP request gets created properly

[edvilme]

Maybe change the wording so that it matches the previous statement?

Suggested change

	* RFC 10008: The HTTP QUERY Method
	* RFC 10008: QUERY Method for HTTP

[mbeijen]

well now it matches RFC

[edvilme]

Edit: Duplicate comment, but can't remove

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[mbeijen]

@StanFromIreland why did you close? I think I messed up because i wanted to merge origin/main into my tree and then I force pushed, is that a big nono? What should I do now, open a new PR and start again?

[StanFromIreland]

Open up a new PR, you've requested a review from many people who have now been automatically subscribed to this PR.

[mbeijen]

Open up a new PR, you've requested a review from many people who have now been automatically subscribed to this PR.

Yeah I'm sorry, I messed up by rebasing in the wrong direction and this triggered a massive set of reviewers that got added because of CODEOWNERS :sad: sorry for the mess

[terryjreedy]

merging main into PR branches is normal and should never cause an issue other than a merge conflict that really needs fixing. force-pushing on PR branches is seldom (never?) needed and not wanted and can cause the problem here.