Replace the usage of httpx

[johnzhou721]

httpx is maintained by the same person who is the original author of MkDocs, who recently announced plans to work on a MkDocs 2.0, with significant pushback. httpx also turned off issues and PRs on their repository, for personal reasons of the author. There's also plans for a breaking v1.

Reference: https://tildeweb.nl/~michiel/httpxyz.html

So should we recommend something else over httpx in the tutorials, and at least recommend tutorial users pin httpx < 1? Or is it fine because the tutorial is not a production project?

[freakboy3742]

I'm aware that httpx shares a maintainer with MkDocs, and that the project has had some recent changes in issue handling. I'll admit these changes don't make me especially comfortable, but I'm also not rushing to replace httpx as a dependency.

Pressing the fork button is easy. Maintaining a fork is difficult. httpxyz has a lot of work to do to before it can claim to be a maintained fork of httpx. If it's still being actively maintained in 12 months, and/or httpx has demonstrated that it's losing market share, then we might consider switching.

[johnzhou721]

I apologize for my lack of clarity here. I do not mean we should replace with httpxyz.

I meant that this should be a problem we're aware of, which, as this comment shows, you are, and that we should start looking for alternatives, and pin httpx < 1 as a fix.

Do you think it would be worthwhile to pin httpx < 1 on the tutorial on this line?

beeware-tutorial/docs/en/tutorial/tutorial-8.md

Line 22 in a48aa5a

"httpx",

If so, I can file an issue.

[freakboy3742]

It's a tutorial. The lifespan of this code is about 30 minutes. We don't need to overthink dependency pinning.

[johnzhou721]

Thanks. I think we can close the loop on this discussion now — I've clearly overlooked the transiency of the tutorial.