sebclem/pixivcord
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

⬆️ Update dependency yarl to v1.9.4 #8

Merged
sebclem merged 1 commits from renovate/yarl-1.x into main 2024-01-25 11:33:37 +01:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2024-01-25 11:27:09 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
yarl patch ==1.9.2 -> ==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 the port 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 build
    backend config setting names. --pure-python is now just pure-python
    -- by :user:webknjaz.

    The usage now looks as follows:

    .. code-block:: console

    $ python -m build \
    --config-setting=pure-python=true \
    --config-setting=with-cython-tracing=true

    (:issue:963)

Contributor-facing changes

  • A step-by-step :doc:Release Guide <contributing/release_guide> guide has
    been 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

    $ python -Im pip install -e .

    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

    $ python -Im pip install . --config-settings=with-cython-tracing=true

    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

    $ python -Im pip install -e .

    Alternatively, the YARL_CYTHON_TRACING=1 environment variable
    can be set to do the same as the :pep:517 config setting.

    :issue:962

v1.9.3

Compare Source

==================

Bug fixes

  • Stopped dropping trailing slashes in :py:meth:~yarl.URL.joinpath -- by :user:gmacon. (:issue:862, :issue:866)
  • Started accepting string subclasses in __truediv__() operations (URL / segment) -- by :user:mjpieters. (:issue:871, :issue:884)
  • Fixed the human representation of URLs with square brackets in usernames and passwords -- by :user:mjpieters. (:issue:876, :issue:882)
  • Updated type hints to include URL.missing_port(), URL.__bytes__()
    and the encoding argument to :py:meth:~yarl.URL.joinpath
    -- by :user:mjpieters. (:issue:891)

Packaging updates and notes for downstreams

  • Integrated Cython 3 to enable building yarl under Python 3.12 -- by :user:mjpieters. (:issue:829, :issue:881)

  • Declared modern setuptools.build_meta as the :pep:517 build
    backend in :file:pyproject.toml explicitly -- by :user:webknjaz. (:issue:886)

  • Converted most of the packaging setup into a declarative :file:setup.cfg
    config -- by :user:webknjaz. (:issue:890)

  • The packaging is replaced from an old-fashioned :file:setup.py to an
    in-tree :pep:517 build backend -- by :user:webknjaz.

    Whenever the end-users or downstream packagers need to build yarl from
    source (a Git checkout or an sdist), they may pass a config_settings
    flag --pure-python. If this flag is not set, a C-extension will be built
    and included into the distribution.

    Here is how this can be done with pip:

    .. code-block:: console

    $ python -m pip install . --config-settings=--pure-python=false

    This will also work with -e | --editable.

    The same can be achieved via pypa/build:

    .. code-block:: console

    $ python -m build --config-setting=--pure-python=false

    Adding -w | --wheel can force pypa/build produce a wheel from source
    directly, as opposed to building an sdist and then building from it. (:issue:893)

    .. attention::

    v1.9.3 was the only version using the --pure-python setting name.
    Later versions dropped the -- prefix, making it just pure-python.

  • Declared Python 3.12 supported officially in the distribution package metadata
    -- by :user:edgarrmondragon. (:issue:942)

Contributor-facing changes

  • A regression test for no-host URLs was added per :issue:821
    and :rfc:3986 -- by :user:kenballus. (:issue:821, :issue:822)

  • Started testing yarl against Python 3.12 in CI -- by :user:mjpieters. (:issue:881)

  • All Python 3.12 jobs are now marked as required to pass in CI
    -- by :user:edgarrmondragon. (:issue:942)

  • MyST is now integrated in Sphinx -- by :user:webknjaz.

    This allows the contributors to author new documents in Markdown
    when they have difficulties with going straight RST. (:issue:953)

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [yarl](https://github.com/aio-libs/yarl) | patch | `==1.9.2` -> `==1.9.4` | --- ### Release Notes <details> <summary>aio-libs/yarl (yarl)</summary> ### [`v1.9.4`](https://github.com/aio-libs/yarl/blob/HEAD/CHANGES.rst#194-2023-12-06) [Compare Source](https://github.com/aio-libs/yarl/compare/v1.9.3...v1.9.4) \================== ## Bug fixes - Started raising :py:exc:`TypeError` when a string value is passed into :py:meth:`~yarl.URL.build` as the `port` 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 build backend config setting names. `--pure-python` is now just `pure-python` \-- by :user:`webknjaz`. The usage now looks as follows: .. code-block:: console $ python -m build \ --config-setting=pure-python=true \ --config-setting=with-cython-tracing=true (:issue:`963`) ## Contributor-facing changes - A step-by-step :doc:`Release Guide <contributing/release_guide>` guide has been 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 $ python -Im pip install -e . 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 $ python -Im pip install . --config-settings=with-cython-tracing=true 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 $ python -Im pip install -e . Alternatively, the `YARL_CYTHON_TRACING=1` environment variable can be set to do the same as the :pep:`517` config setting. :issue:`962` ### [`v1.9.3`](https://github.com/aio-libs/yarl/blob/HEAD/CHANGES.rst#193-2023-11-20) [Compare Source](https://github.com/aio-libs/yarl/compare/v1.9.2...v1.9.3) \================== ## Bug fixes - Stopped dropping trailing slashes in :py:meth:`~yarl.URL.joinpath` -- by :user:`gmacon`. (:issue:`862`, :issue:`866`) - Started accepting string subclasses in `__truediv__()` operations (`URL / segment`) -- by :user:`mjpieters`. (:issue:`871`, :issue:`884`) - Fixed the human representation of URLs with square brackets in usernames and passwords -- by :user:`mjpieters`. (:issue:`876`, :issue:`882`) - Updated type hints to include `URL.missing_port()`, `URL.__bytes__()` and the `encoding` argument to :py:meth:`~yarl.URL.joinpath` \-- by :user:`mjpieters`. (:issue:`891`) ## Packaging updates and notes for downstreams - Integrated Cython 3 to enable building *yarl* under Python 3.12 -- by :user:`mjpieters`. (:issue:`829`, :issue:`881`) - Declared modern `setuptools.build_meta` as the :pep:`517` build backend in :file:`pyproject.toml` explicitly -- by :user:`webknjaz`. (:issue:`886`) - Converted most of the packaging setup into a declarative :file:`setup.cfg` config -- by :user:`webknjaz`. (:issue:`890`) - The packaging is replaced from an old-fashioned :file:`setup.py` to an in-tree :pep:`517` build backend -- by :user:`webknjaz`. Whenever the end-users or downstream packagers need to build `yarl` from source (a Git checkout or an sdist), they may pass a `config_settings` flag `--pure-python`. If this flag is not set, a C-extension will be built and included into the distribution. Here is how this can be done with `pip`: .. code-block:: console $ python -m pip install . --config-settings=--pure-python=false This will also work with `-e | --editable`. The same can be achieved via `pypa/build`: .. code-block:: console $ python -m build --config-setting=--pure-python=false Adding `-w | --wheel` can force `pypa/build` produce a wheel from source directly, as opposed to building an `sdist` and then building from it. (:issue:`893`) .. attention:: v1.9.3 was the only version using the `--pure-python` setting name. Later versions dropped the `--` prefix, making it just `pure-python`. - Declared Python 3.12 supported officially in the distribution package metadata \-- by :user:`edgarrmondragon`. (:issue:`942`) ## Contributor-facing changes - A regression test for no-host URLs was added per :issue:`821` and :rfc:`3986` -- by :user:`kenballus`. (:issue:`821`, :issue:`822`) - Started testing *yarl* against Python 3.12 in CI -- by :user:`mjpieters`. (:issue:`881`) - All Python 3.12 jobs are now marked as required to pass in CI \-- by :user:`edgarrmondragon`. (:issue:`942`) - MyST is now integrated in Sphinx -- by :user:`webknjaz`. This allows the contributors to author new documents in Markdown when they have difficulties with going straight RST. (:issue:`953`) </details> --- ### 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 becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNTIuMCIsInVwZGF0ZWRJblZlciI6IjM3LjE1Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
renovate-bot added 1 commit 2024-01-25 11:27:11 +01:00
⬆️ Update dependency yarl to v1.9.4
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Details
ci/woodpecker/pr/woodpecker Pipeline was successful
Details
f14b925ef1
renovate-bot force-pushed renovate/yarl-1.x from f14b925ef1 to 98ca76d285 2024-01-25 11:33:21 +01:00 Compare
sebclem merged commit d9a5e50685 into main 2024-01-25 11:33:37 +01:00
sebclem deleted branch renovate/yarl-1.x 2024-01-25 11:33:38 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sebclem/pixivcord#8
No description provided.
Delete Branch "renovate/yarl-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?