Add hishel - #3297
Merged
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
karpetrosyan
commented
Aug 23, 2026
ContributorAuthor
Thanks 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Project
hishel
Checklist
Add project-name- [pypi-name](https://github.com/owner/repo) - Description ending with period.Which Tier
Pick one:
Explain:
hishel is the RFC 9111 HTTP caching library for httpx and requests (sync and async). 5.6M downloads/month (pypistats), 1.x since Oct 2025, latest release Aug 2026
Displacement
Not needed — Caching had 4 entries, this makes 5.
Alternative placement: HTTP response caching is arguably its own use case, so an "HTTP Caching" subcategory under HTTP Clients (next to Clients and URL Manipulation) would be a more precise home. That is a structure change and maintainer-only, so this PR uses the existing Caching use case; happy to move it if you prefer the subcategory.