Releases: jawah/niquests
Releases · jawah/niquests
Version 3.4.7
3.4.7 (2024-02-21)
Fixed
- Unintentional performance regression with multiple concurrent multiplexed connection within a single Session.
Version 3.4.6
3.4.6 (2024-02-21)
Fixed
- Unmatched filter for deprecation warning yielded by Cryptography due to some legacy CA available in Windows having a negative serial number.
- Setting
boundary
inContent-Type
header with no value associated (no equal sign) can cause a rare error (multipart). - Rare racing condition while emitting too many request across a multiplexed connections.
- Spawning too many threads while using
AsyncSession
in specific contexts.
Version 3.4.5
3.4.5 (2024-02-02)
Fixed
- Thread-safety issue when leveraging a single multiplexed connection across multiple threads.
- Apparently consumed content when allow_redirect is set to True when accessing a lazy response that follow redirects.
Changed
- urllib3.future lower bound constraint has been raised to version 2.5.900 in order to leverage the advanced multiplexing scheduler.
This upgrade come with a noticeable performance bump with complex multiplexed requests.
Added
Session
constructor now accepts bothpool_connections
andpool_maxsize
parameters to scale your pools of connections at will.
Version 3.4.4
3.4.4 (2024-01-19)
Fixed
- Issuing a request with
Session(multiplexed=True)
that weren't eligible (e.g. HTTP/1.1) but was redirected to an
eligible server (HTTP/2+) caused a rare error. - An anonymous netrc entry (e.g. username only) could be wrongfully used when it should be discarded. (PR #61)
Added
- Awaitable close method within
AsyncSession
.
Version 3.4.3
3.4.3 (2024-01-16)
Fixed
- Accessing a lazy response (multiplexed enabled) that have multiple redirects did not work appropriately.
Changed
- Response
iter_content
anditer_line
read chunks as they arrive by default. The default chunk size is now-1
.
-1
mean to instruct that the chunks can be of variable sizes, depending on how packets arrives. It improves
overall performances in content streaming. - urllib3.future lower bound constraint has been raised to version 2.4.904 in order to accept
-1
as a chunk size.
Version 3.4.2
3.4.2 (2024-01-11)
Fixed
- Connection information kept targeting its original copy, thus always keeping the latest timings inside while expecting the historical ones.
Added
AsyncSession
now returns aAsyncResponse
whenstream
is set to True in order to handle properly streams in an async context.
Version 3.4.1
3.4.1 (2024-01-07)
Fixed
CaseInsensibleDict
did not properly convertHTTPHeaderDict
from urllib3 thus only letting the last entry in.- Redirect chain lead to a non waited coroutine in
AsyncSession
.
Version 3.4.0
3.4.0 (2024-01-01)
Added
- Support for specifying a custom DNS resolver in
Session
. - Support for passing the source address in
Session
. - Support for disabling either IPv4 or IPv6 within a
Session
.
Changed
- PySocks is no longer used for SOCKS proxies. Replaced by python-socks instead.
- urllib3.future minimal version raised to 2.4+ to leverage newly added features.
- Improve compatibility when end-user inadvertently pass a
Timeout
orRetry
instance from the legacyurllib3
instead ofurllib3_future
.
Fixed
- Blocking the event loop when closing the
AsyncSession
usingwith
. - Rare exception on older PyPy interpreters due to Generic having unsupported type variable in
extensions._sync_to_async
module.
Misc
- Project extras aligned with urllib3.future.
- Using nox instead of tox.
- Switch to ruff instead of black and isort.
Version 3.3.4
3.3.4 (2023-12-03)
Fixed
- Overall, the static typing experience has been improved.
- Code HTTP 425 is now registered as
too_early
in addition to the legacyunordered_collection
.
Removed
- Private module
niquests._internal_utils
has been removed as it no longer serves its purposes.
Version 3.3.3
3.3.3 (2023-11-26)
Added
- Hook
on_upload
that allows you to monitor/track the upload progress. - Model
TransferProgress
that is used inPreparedRequest
as public propertyupload_progress
.