build(deps): update dependency yarl to v1.9.4 #42
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.9.3
->1.9.4
Release Notes
aio-libs/yarl (yarl)
v1.9.4
Compare Source
==================
Bug fixes
Started raising :py:exc:
TypeError
when a string value is passed into:py:meth:
~yarl.URL.build
as theport
argument -- by :user:commonism
.Previously the empty string as port would create malformed URLs when rendered as string representations. (:issue:
883
)Packaging updates and notes for downstreams
The leading
--
has been dropped from the :pep:517
in-tree buildbackend config setting names.
--pure-python
is now justpure-python
-- by :user:
webknjaz
.The usage now looks as follows:
.. code-block:: console
(:issue:
963
)Contributor-facing changes
A step-by-step :doc:
Release Guide <contributing/release_guide>
guide hasbeen added, describing how to release yarl -- by :user:
webknjaz
.This is primarily targeting maintainers. (:issue:
960
)Coverage collection has been implemented for the Cython modules
-- by :user:
webknjaz
.It will also be reported to Codecov from any non-release CI jobs.
To measure coverage in a development environment, yarl can be
installed in editable mode:
.. code-block:: console
Editable install produces C-files required for the Cython coverage
plugin to map the measurements back to the PYX-files.
:issue:
961
It is now possible to request line tracing in Cython builds using the
with-cython-tracing
:pep:517
config setting-- :user:
webknjaz
.This can be used in CI and development environment to measure coverage
on Cython modules, but is not normally useful to the end-users or
downstream packagers.
Here's a usage example:
.. code-block:: console
For editable installs, this setting is on by default. Otherwise, it's
off unless requested explicitly.
The following produces C-files required for the Cython coverage
plugin to map the measurements back to the PYX-files:
.. code-block:: console
Alternatively, the
YARL_CYTHON_TRACING=1
environment variablecan be set to do the same as the :pep:
517
config setting.:issue:
962
Configuration
📅 Schedule: Branch creation - "on the 1st day of the month" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.