aio-libs/yarl - CodSpeed

yarl

Performance History

Latest Results

Keep RFC mode host checks off the WHATWG build path Guard the calls with the mode at the call sites, so URL.build() and with_host() in the default mode do not pay for an extra function call.

asvetlov:conformance-mode-aware

9 hours ago

Reject RFC-invalid userinfo and IDNA2008 hosts in RFC mode Measuring RFC mode in the conformance report showed two cases both standards reject that RFC mode accepted: an authority with more than one '@', and a non-ASCII host only the IDNA2003 fallback can encode.

asvetlov:conformance-mode-aware

9 hours ago

Measure both modes in the conformance report Each WPT case now runs through yarl in WHATWG mode and in RFC 3986 mode. A new section lists the cases where each mode follows its own standard, and the remaining ones are split by which mode misses its standard.

asvetlov:conformance-mode-aware

10 hours ago

Read the authority of http:host without "//" in WHATWG mode The WHATWG URL Standard skips the slashes after the scheme of a special URL other than file, so "http:example.com/" and "http:/example.com/" are "http://example.com/". Against a base with the same scheme the same input is a relative reference; the parsed URL keeps its original path so that URL.join() still resolves it that way. RFC 3986 mode is unchanged.

asvetlov:special-authority-no-slashes

10 hours ago

Strip trailing C0 control or space from parsed URLs (#1936)  ## What do these changes do? `split_url()` stripped only leading C0 control characters and spaces, following a comment copied from `urllib.parse.urlsplit`, and percent-encoded the trailing ones: `URL("http://h/p ")` printed as `http://h/p%20`. It now strips both ends in both modes. For WHATWG mode this is the basic URL parser. For RFC 3986 mode the strict grammar rejects such input, but RFC 3986 appendix C asks software that accepts user-typed URIs to strip surrounding whitespace, and RFC mode already stripped the leading side and dropped tabs and newlines. In `tools/conformance/REPORT.md`, four rows move from "All three differ" to "RFC 3986 differs, yarl follows WHATWG" (`' foo.com '`, `'\t :foo.com \n'`, `non-special:opaque `, and one with leading and trailing control characters). Two rows of that category stay because of unrelated differences (query spaces encoded as `+`, and `c|` drive letters). The "yarl differs, RFC 3986 and WHATWG agree" section is unchanged. ## Are there changes in behavior for the user? Yes. Trailing C0 control characters and spaces in a parsed URL string are dropped instead of being percent-encoded, in both `encoded=False` and `encoded=True` parsing and in both modes. ## Is it a substantial burden for the maintainers to support this? No, it replaces `lstrip` with `strip`. ## Related issue number Follow-up to #1923. ## Checklist - [x] I think the code is well written - [x] Unit tests for the changes exist - [x] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` - [x] Add a new news fragment into the `CHANGES/` folder Drafted with Claude Code (Claude Opus 5.5); reviewed by @asvetlov. <details> <summary>Agent run details (optional, for reviewers)</summary> Tests: `pytest ./tests ./yarl -n auto` with the C extension: 2503 passed, 131 skipped, 57 xfailed; with `YARL_NO_EXTENSIONS=1`: 2120 passed, 138 skipped, 55 xfailed. Conformance: `python tools/conformance/compare.py --check` passes after `make conformance`. Docs: sphinx doctest 192 tests, 0 failures; the spelling build shows only local false positives in `index.rst` contractions, which are unrelated. Lint: `pre-commit run` on the changed files passes, including mypy. </details>

master

10 hours ago

Re-enable the conformance report CI job (#1935)  ## What do these changes do? Uncomments the `Conformance report is current` job in `ci-cd.yml` and adds it back to the `test-summary` needs. The job runs `tools/conformance/compare.py --check` against the built wheel, so a PR that changes URL behaviour without regenerating `tools/conformance/REPORT.md` fails. AGENTS.md already describes the job as active. ## Are there changes in behavior for the user? No, CI only. ## Is it a substantial burden for the maintainers to support this? No. The check runs in a few seconds on the prebuilt wheel, and the report is already current on master. ## Related issue number Follow-up to #1923. ## Checklist - [x] I think the code is well written - [ ] Unit tests for the changes exist: N/A, CI only - [x] Documentation reflects the changes (AGENTS.md already describes the job) - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` - [x] Add a new news fragment into the `CHANGES/` folder Drafted with Claude Code (Claude Opus 5.5); reviewed by @asvetlov. <details> <summary>Agent run details (optional, for reviewers)</summary> `python tools/conformance/compare.py --check` passes on 66cb4c0. `pre-commit run` on the changed files passes (actionlint, check-jsonschema, yamllint, timeout-minutes check). </details>

master

10 hours ago

Strip trailing C0 control or space from parsed URLs The WHATWG basic URL parser strips leading and trailing C0 control or space; RFC 3986 appendix C asks software that accepts user-typed URIs to strip surrounding whitespace too. yarl only stripped the leading side, a rule copied from urllib.parse.urlsplit, and percent-encoded the trailing characters. Strip both ends in both modes.

asvetlov:strip-trailing-space

10 hours ago

Re-enable the conformance report CI job The job checks that tools/conformance/REPORT.md matches the code built into the wheel; it was commented out before #1923 landed.

asvetlov:conformance-ci-job

10 hours ago

Latest Branches

Measure both modes in the conformance report#1938

9 hours ago

71ec093

asvetlov:conformance-mode-aware

Read the authority of http:host without "//" in WHATWG mode#1937

10 hours ago

fc5e0d5

asvetlov:special-authority-no-slashes

Strip trailing C0 control or space from parsed URLs#1936

10 hours ago

b2a2421

asvetlov:strip-trailing-space

Home Terms Privacy Docs