-
Notifications
You must be signed in to change notification settings - Fork 20
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
chore(deps): update dependency pook to v2 #406
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/pook-2.x-lockfile
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
July 8, 2024 01:38
11ac9fa
to
e54d68d
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
3 times, most recently
from
July 15, 2024 01:02
ba165f2
to
a22d000
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
3 times, most recently
from
July 25, 2024 17:35
d557a85
to
e57eab4
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
4 times, most recently
from
August 5, 2024 02:00
086b281
to
abf1ea6
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
8 times, most recently
from
August 12, 2024 01:18
23bf582
to
171bfb8
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
August 19, 2024 01:39
f7faac7
to
e5c3f8f
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
3 times, most recently
from
September 2, 2024 00:42
80ff237
to
2cccac5
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
from
October 8, 2024 04:43
2cccac5
to
012a62f
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
3 times, most recently
from
October 24, 2024 09:38
1583d23
to
a1d0364
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
7 times, most recently
from
October 29, 2024 22:14
ca01de3
to
fe1b8ae
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
3 times, most recently
from
November 11, 2024 01:17
851225f
to
d5830a9
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
November 25, 2024 00:50
9f10950
to
5875efb
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
4 times, most recently
from
December 6, 2024 23:26
8326dfc
to
5a0fe7d
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
December 16, 2024 00:18
7ed5408
to
a5f6489
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
December 23, 2024 01:54
fd5ceab
to
baf81c8
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
2 times, most recently
from
January 1, 2025 01:54
bd9d039
to
d72660b
Compare
renovate
bot
force-pushed
the
renovate/pook-2.x-lockfile
branch
from
January 6, 2025 00:50
d72660b
to
0cb3d7d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.
This PR contains the following updates:
1.4.3
->2.1.3
Release Notes
h2non/pook (pook)
v2.1.3
Compare Source
v2.1.2
Compare Source
headers
object for standard library urllib by @sarayourfriend in https://github.com/h2non/pook/pull/154.Sequence[tuple[str, str]]
header input with aiohttp by @sarayourfriend in https://github.com/h2non/pook/pull/154.v2.1.1
Compare Source
Flush mocks when
pook.activate
used as a wrapper by @shift0965 in https://github.com/h2non/pook/pull/145.v2.1.0
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
See https://github.com/h2non/pook/issues/128 for a summary of the breaking changes and how to update your code if you are affected.
Breaking change: Remove
Response::body
'sbinary
parameter and enforce a keyword argument forchunked
.binary
parameter is no longer needed since responses are now always byte-encoded in all cases (see below).chunked
to ensure unnamed arguments meant for the removedbinary
parameter cannot be confused aschunked
arguments.Only return byte-encoded response bodies, matching the bahviour of all supported client libraries.
client library over the wire, which will, in all cases, be bytes. Client libraries that support reading
response content as a string or other formats will continue to work as expected, because they'll always
be handling bytes from pook.
urllib
,for which this also fixed a bug where non-bytes bodies were returned by pook in certain cases. This is impossible
in real application code. If you rely on pook to mock
urllib
responses and have code that handles non-bytes responsebodies, that code can be safely deleted (provided the only reason it was there was pook in the first place).
Breaking change: Remove
Mock::body
'sbinary
parameter.BodyMatcher
),so this will not cause any changes to tests that relied on it: it didn't do anything to begin with.
of any interecepted request will always be stored as bytes, and only decoded when necessary for individual downstream
matchers (JSON, XML).
Correct documentation strings for
XMLMatcher
andJSONMatcher
to no longer suggest they can handle regex matchers.Add a pytest fixture to the package.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.