-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align API with HTTPX changes #79
Comments
Looking forward to this, as I currently have a conflict with a dependency that requires |
Current Did you mean something else, or have more detail on what Feedback welcome! |
@lundberg can you release an version on pypi with supports poetry lock
Updating dependencies
Resolving dependencies... (0.3s)
[SolverProblemError]
Because respx (0.12.1) depends on httpx (>=0.14,<0.15)
and no versions of respx match >0.12.1,<0.13.0, respx (>=0.12.1,<0.13.0) requires httpx (>=0.14,<0.15).
So, because ... depends on both httpx (^0.15.4) and respx (^0.12.1), version solving failed. |
Hi, we are using respx 0.12.1 and poetry shows this to me
Notice the upper limit <0.15. So having respx as dependency prevents us from upgrading to httpx 0.15.4. Looking forward for the latest changes. :) edit: jairhenrique and me got hit by the same problem at the same time it seems :D |
@lundberg I'm having the exact problem @jairhenrique is having:
|
Absolutely, released |
I removed the |
Thanks so much @lundberg, |
Super quick, thanks |
HTTPX public API has seen some changes lately that should be addressed and aligned with in RESPX.
When adding patterns/responses, RESPX should support:
params
(suggested in Support HTTPX params argument #63 and solved by Fixed #63: Support HTTPX params argument #81)Moved Enhance request pattern matching #87files
(investigate POST fields)Moved Enhance request pattern matching #87cookies
(investigate format)text
,html
andjson
(like existing content -> json, to mimic Response.PartlySolved by Refactor encode/decode raw response #82 and Expose text, html and json in high-level API #93)The text was updated successfully, but these errors were encountered: