fix(spikes): make fixture captures reproducible, and stop leaking $HOME

The weekly fixture-drift job has never been able to pass, and could not have.
Every capture built its venv in a `mkdtemp` directory whose name carries a random
suffix, and `redact()` replaced only the temp *root*, so the suffix survived into
every committed sidecar. A 100% false-positive rate, independent of any engine
release.

Four more sources of churn were underneath it, found by running the captures twice
back to back rather than by reasoning about them:

  - pip's "[notice] To update, run: <venv>\Scripts\python.exe" embeds the venv
    path -- which also shipped the capturing user's home directory to a public repo
  - CPython object addresses in urllib3 retry warnings, moved by ASLR
    ("<HTTPConnection object at 0x000001A92FBCFBC0>")
  - pip's download progress bar, which carries a transfer rate and an ETA
  - uv's per-phase timings ("Resolved 3 packages in 775ms")

Plus two absolute interpreter paths that can never match a re-capture on CI, where
Python lives in hostedtoolcache rather than under the user profile, and pip's cache
state, which turns "Downloading numpy-1.19.5.zip (7.3 MB)" into "Using cached ..."
depending on what the machine happened to have. A runner is always cold; a dev
machine is usually warm.

So: redact all of it, capture cache-free so both sides take the download path, and
split the sidecar by what each half is for. meta.json is the contract the gate
watches; capture-provenance.json records engine and interpreter versions and argv,
churns on every release, and is excluded from the gate by pathspec -- still
committed, so `git diff` always tells you which engine produced the current bytes.

This is the one place fixtures are not literal engine bytes, against the letter of
TESTING section 1. It is safe because nothing reads a path or a duration out of
them: every CLASSIFIERS entry in errors/catalog.rs keys off message text, and the
uv adapter only tests contains("Resolved "). Line endings are untouched -- `-text`
is what protects those. Verified: 173 tests green, and two full capture passes over
both engines differ in 0 of 96 files.

Two smaller things in the same area, both of which hid the problem:

  - .gitattributes set `-diff` as well as `-text` on the fixture tree. `-text` is
    what preserves the CRLF bytes the comment argues for; `-diff` only suppresses
    the textual diff, so the drift job's own diagnostics could report nothing but
    "Binary files differ". Scope byte-exactness to the .txt captures and let the
    JSON sidecars be diffable.
  - the "weekly, daily would be rude" drift job matched the nightly cron, the only
    one in the file, so it ran nightly. Give it its own '17 4 * * 1', and drop the
    run_attempt guard -- re-running is how you reproduce a drift failure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 5 committed 2026-07-29 20:26:01 +07:00
1 parent 6a81b0cbfe
commit 4066aa63d4
67 files changed
+868 -677

No files matched your search

+11 -2
View File
@@ -16,5 +16,14 @@
# pip and uv emit CRLF on Windows. Normalising those to LF in the blob would test the adapter
# parsers against line endings that never occur in production — a parser mishandling a trailing
# \r would pass CI and fail on every real Windows machine. docs/TESTING.md §1 makes adapter
# parsing the thing that must never regress, so: no normalisation, no diffing.
crates/pipdock-core/tests/fixtures/** -text -diff
# parsing the thing that must never regress, so: no normalisation.
#
# `-text` is what buys that. `-diff` does NOT: it only suppresses the textual diff, and it used
# to be set here too, which meant the weekly drift job — whose entire job is to show you which
# engine bytes moved — could report nothing but "Binary files differ". Byte-exactness and a
# readable diff are not in tension, so keep the first and drop the second.
crates/pipdock-core/tests/fixtures/**/*.txt -text
# The JSON sidecars are ours, not the engines'. They are ordinary text and must stay diffable:
# meta.json is the contract the drift job gates on, so its diff has to be legible.
crates/pipdock-core/tests/fixtures/**/*.json text eol=crlf
+21 -5
View File
@@ -22,8 +22,12 @@ on:
- 'spikes/capture.py'
- '.github/workflows/ci-integration.yml'
schedule:
# Nightly, and the fixture-drift check weekly on Mondays (see the job condition below).
# Nightly: the disposable-venv end-to-end pass.
- cron: '17 3 * * *'
# Mondays: the fixture-drift re-capture. It needs its own cron rather than a day-of-week
# condition on the nightly one — `github.event.schedule` is the only thing a job can match
# on, so two behaviours need two entries or the "weekly" job silently runs every night.
- cron: '17 4 * * 1'
workflow_dispatch:
permissions:
@@ -181,7 +185,9 @@ jobs:
name: Re-capture against the latest engines
# Weekly rather than nightly: it hits PyPI hard enough that daily would be rude, and engine
# releases are not a daily event.
if: github.event_name == 'schedule' && github.event.schedule == '17 3 * * *' && github.run_attempt == 1
# Not gated on run_attempt: re-running the workflow is how you reproduce a drift failure,
# so skipping this job on a retry would defeat the point.
if: (github.event_name == 'schedule' && github.event.schedule == '17 4 * * 1') || github.event_name == 'workflow_dispatch'
runs-on: windows-latest
timeout-minutes: 30
steps:
@@ -207,12 +213,22 @@ jobs:
# A diff means an engine changed its output. That is exactly the PD-ENG-003 situation the
# adapters degrade into, and catching it here is what stops a user meeting it first.
#
# capture-provenance.json is excluded: it records the engine and interpreter versions and
# the argv used, all of which move on every engine release and every setup-python bump.
# Gating on it would fire this job constantly for reasons that have nothing to do with
# output shape. It is still rewritten and still committable, so `git diff` after a run
# always tells you which engine produced the current bytes.
- name: Fail if the captured shapes moved
shell: pwsh
run: |
git diff --stat -- crates/pipdock-core/tests/fixtures
if (git status --porcelain -- crates/pipdock-core/tests/fixtures) {
git diff -- crates/pipdock-core/tests/fixtures
$paths = @(
'crates/pipdock-core/tests/fixtures',
':!crates/pipdock-core/tests/fixtures/**/capture-provenance.json'
)
git diff --stat -- $paths
if (git status --porcelain -- $paths) {
git diff --text -- $paths
throw "engine output changed — review the diff, update the adapters, commit the new fixtures"
}
@@ -0,0 +1,16 @@
{
"scenario": "build-backend-failure",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"numpy==1.19.5"
],
"stdout_bytes": 360,
"stderr_bytes": 7255
}
@@ -1,25 +1,13 @@
{
"scenario": "build-backend-failure",
"question": "sdist build backend failure (PEP 517 backend unavailable).",
"expects_code": "PD-BLD-002",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-build-backend-failure-tykm5pzw\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-build-backend-failure-tykm5pzw\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"numpy==1.19.5"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 2,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 282,
"stderr_bytes": 7255
}
{
"scenario": "build-backend-failure",
"question": "sdist build backend failure (PEP 517 backend unavailable).",
"expects_code": "PD-BLD-002",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 2,
"seed": [],
"seed_exit_code": null
}
@@ -1,82 +1,82 @@
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
ERROR: Exception:
Traceback (most recent call last):
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 106, in _run_wrapper
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 106, in _run_wrapper
status = _inner_run()
^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 97, in _inner_run
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 97, in _inner_run
return self.run(options, args)
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\cli\req_command.py", line 67, in wrapper
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\req_command.py", line 67, in wrapper
return func(self, options, args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\commands\install.py", line 386, in run
File "<WORK>\venv\Lib\site-packages\pip\_internal\commands\install.py", line 386, in run
requirement_set = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\resolver.py", line 95, in resolve
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\resolver.py", line 95, in resolve
result = self._result = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 546, in resolve
File "<WORK>\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 546, in resolve
state = resolution.resolve(requirements, max_rounds=max_rounds)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 397, in resolve
File "<WORK>\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 397, in resolve
self._add_to_criteria(self.state.criteria, r, parent=None)
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 173, in _add_to_criteria
File "<WORK>\venv\Lib\site-packages\pip\_vendor\resolvelib\resolvers.py", line 173, in _add_to_criteria
if not criterion.candidates:
^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\resolvelib\structs.py", line 156, in __bool__
File "<WORK>\venv\Lib\site-packages\pip\_vendor\resolvelib\structs.py", line 156, in __bool__
return bool(self._sequence)
^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 174, in __bool__
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 174, in __bool__
return any(self)
^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 162, in <genexpr>
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 162, in <genexpr>
return (c for c in iterator if id(c) not in self._incompatible_ids)
^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 53, in _iter_built
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\found_candidates.py", line 53, in _iter_built
candidate = func()
^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\factory.py", line 187, in _make_candidate_from_link
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\factory.py", line 187, in _make_candidate_from_link
base: Optional[BaseCandidate] = self._make_base_candidate_from_link(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\factory.py", line 233, in _make_base_candidate_from_link
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\factory.py", line 233, in _make_base_candidate_from_link
self._link_candidate_cache[link] = LinkCandidate(
^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 304, in __init__
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 304, in __init__
super().__init__(
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 159, in __init__
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 159, in __init__
self.dist = self._prepare()
^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 236, in _prepare
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 236, in _prepare
dist = self._prepare_distribution()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 315, in _prepare_distribution
File "<WORK>\venv\Lib\site-packages\pip\_internal\resolution\resolvelib\candidates.py", line 315, in _prepare_distribution
return preparer.prepare_linked_requirement(self._ireq, parallel_builds=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 527, in prepare_linked_requirement
File "<WORK>\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 527, in prepare_linked_requirement
return self._prepare_linked_requirement(req, parallel_builds)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 642, in _prepare_linked_requirement
File "<WORK>\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 642, in _prepare_linked_requirement
dist = _get_prepared_distribution(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 72, in _get_prepared_distribution
File "<WORK>\venv\Lib\site-packages\pip\_internal\operations\prepare.py", line 72, in _get_prepared_distribution
abstract_dist.prepare_distribution_metadata(
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 56, in prepare_distribution_metadata
File "<WORK>\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 56, in prepare_distribution_metadata
self._install_build_reqs(finder)
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 126, in _install_build_reqs
File "<WORK>\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 126, in _install_build_reqs
build_reqs = self._get_build_requires_wheel()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 103, in _get_build_requires_wheel
File "<WORK>\venv\Lib\site-packages\pip\_internal\distributions\sdist.py", line 103, in _get_build_requires_wheel
return backend.get_requires_for_build_wheel()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_internal\utils\misc.py", line 702, in get_requires_for_build_wheel
File "<WORK>\venv\Lib\site-packages\pip\_internal\utils\misc.py", line 702, in get_requires_for_build_wheel
return super().get_requires_for_build_wheel(config_settings=cs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_impl.py", line 196, in get_requires_for_build_wheel
File "<WORK>\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_impl.py", line 196, in get_requires_for_build_wheel
return self._call_hook(
^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-build-backend-failure-tykm5pzw\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_impl.py", line 402, in _call_hook
File "<WORK>\venv\Lib\site-packages\pip\_vendor\pyproject_hooks\_impl.py", line 402, in _call_hook
raise BackendUnavailable(
pip._vendor.pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'
@@ -1,5 +1,6 @@
Collecting numpy==1.19.5
Using cached numpy-1.19.5.zip (7.3 MB)
Downloading numpy-1.19.5.zip (7.3 MB)
<PROGRESS>
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
@@ -0,0 +1,20 @@
{
"scenario": "clean-upgrade",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"idna"
],
"stdout_bytes": 7526,
"stderr_bytes": 203
}
@@ -1,31 +1,15 @@
{
"scenario": "clean-upgrade",
"question": "Baseline: what does an unconstrained upgrade plan look like?",
"expects_code": null,
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-clean-upgrade-enhq45pn\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-clean-upgrade-enhq45pn\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"idna"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0,
"stdout_bytes": 7526,
"stderr_bytes": 203
}
{
"scenario": "clean-upgrade",
"question": "Baseline: what does an unconstrained upgrade plan look like?",
"expects_code": null,
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0
}
@@ -1,3 +1,3 @@
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-clean-upgrade-enhq45pn\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
@@ -20,7 +20,7 @@
"name": "idna",
"version": "3.18",
"summary": "Internationalized Domain Names in Applications (IDNA)",
"description": "# Internationalized Domain Names in Applications (IDNA)\n\nSupport for [Internationalized Domain Names in Applications\n(IDNA)](https://tools.ietf.org/html/rfc5891) and [Unicode IDNA\nCompatibility Processing](https://unicode.org/reports/tr46/). It\nsupersedes the standard library's `encodings.idna`, which only\nimplements the 2003 specification, offering broader script coverage and\nlimiting domains with known security vulnerabilities.\n\n## Usage\n\nPackage may be installed from [PyPI](https://pypi.org/project/idna/) via\nthe typical methods (e.g. `python3 -m pip install idna`)\n\nFor typical usage, the `encode` and `decode` functions will take a\ndomain name argument and perform a conversion to ASCII-compatible encoding\n(known as A-labels), or to Unicode strings (known as U-labels)\nrespectively.\n\n```pycon\n>>> import idna\n>>> idna.encode('ドメイン.テスト')\nb'xn--eckwd4c7c.xn--zckzah'\n>>> print(idna.decode('xn--eckwd4c7c.xn--zckzah'))\nドメイン.テスト\n```\n\nConversions can be applied at a per-label basis using the `ulabel` or\n`alabel` functions for specialized use cases.\n\n\n### Compatibility Mapping (UTS #46)\n\nThis library provides support for [Unicode IDNA Compatibility\nProcessing](https://unicode.org/reports/tr46/) which normalizes input from\ndifferent potential ways a user may input a domain prior to performing the IDNA\nconversion operations. This functionality, known as a\n[mapping](https://tools.ietf.org/html/rfc5895), is considered by the\nspecification to be a local user-interface issue distinct from IDNA\nconversion functionality.\n\nFor example, \"Königsgäßchen\" is not a permissible label as capital letters\nare not allowed. UTS 46 will convert this into lower case prior to applying\nthe IDNA conversion.\n\n```pycon\n>>> import idna\n>>> idna.encode('Königsgäßchen')\n...\nidna.core.InvalidCodepoint: Codepoint U+004B at position 1 of 'Königsgäßchen' not allowed\n>>> idna.encode('Königsgäßchen', uts46=True)\nb'xn--knigsgchen-b4a3dun'\n>>> idna.decode('xn--knigsgchen-b4a3dun')\n'königsgäßchen'\n```\n\nWhen performing a decode operation for display purposes, `decode()`\naccepts a `display=True` argument that leaves any `xn--` label that\nfails to decode unchanged. This is useful for user interface display\nwhere a domain is in use, the A-label form can be presented when it\nis not a valid IDN.\n\n\n## Exceptions\n\nAll errors raised during conversion derive from the `idna.IDNAError`\nbase class. The more specific exceptions are:\n\n* `idna.IDNABidiError` — raised when a label contains an illegal\n combination of left-to-right and right-to-left characters.\n* `idna.InvalidCodepoint` — raised when a label contains a codepoint\n that is INVALID for IDNA.\n* `idna.InvalidCodepointContext` — raised when a CONTEXTO or CONTEXTJ\n codepoint appears in a position whose contextual requirements are\n not satisfied.\n\n\n## Command-line tool\n\nThe package supports command-line usage to convert domain names\nbetween their Unicode and ASCII-compatible forms. It can be run either\nas a module (`python3 -m idna`) or, once installed (such as with `uv\ntool` or `pipx`), via the `idna` script:\n\n```bash\n$ uv tool install idna\n$ idna xn--e1afmkfd.xn--p1ai\nпример.рф\n$ idna пример.рф\nxn--e1afmkfd.xn--p1ai\n```\n\nMode can be specified with `-e`/`--encode` or `-d`/`--decode`, otherwise\nit will be chosen automatically based on the first input. Multiple\ndomains can be supplied either as arguments or through standard input.\nUTS #46 mapping is applied by default, which lets the tool accept\ninputs that aren't strictly valid IDNA 2008 by normalising them first,\npass `--strict` to disable UTS #46.\n\nConversion failures are reported on stderr together with the\noffending input; processing continues with the remaining domains and\nthe tool exits with a non-zero status if any conversion failed.\n\n\n## Additional Notes\n\n* **Version support**. This library supports Python 3.9 and higher.\n As this library serves as a low-level toolkit for a variety of\n applications, we strive to support all versions of Python that are\n not beyond end-of-life.\n\n* **Emoji**. It is an occasional request to support emoji domains in\n this library. Encoding of symbols like emoji is expressly prohibited by\n the IDNA technical standard, and emoji domains are broadly phased\n out across the domain industry due to associated security risks.\n\n* **Regenerating lookup tables**. The IDNA and UTS 46 functionality\n relies upon pre-calculated lookup tables, generated using the\n `idna-data` script in [`tools/`](tools/README.md).\n\n",
"description": "# Internationalized Domain Names in Applications (IDNA)\n\nSupport for [Internationalized Domain Names in Applications\n(IDNA)](https://tools.ietf.org/html/rfc5891) and [Unicode IDNA\nCompatibility Processing](https://unicode.org/reports/tr46/). It\nsupersedes the standard library's `encodings.idna`, which only\nimplements the 2003 specification, offering broader script coverage and\nlimiting domains with known security vulnerabilities.\n\n## Usage\n\nPackage may be installed from [PyPI](https://pypi.org/project/idna/) via\nthe typical methods (e.g. `python3 -m pip install idna`)\n\nFor typical usage, the `encode` and `decode` functions will take a\ndomain name argument and perform a conversion to ASCII-compatible encoding\n(known as A-labels), or to Unicode strings (known as U-labels)\nrespectively.\n\n```pycon\n>>> import idna\n>>> idna.encode('ドメイン.テスト')\nb'xn--eckwd4c7c.xn--zckzah'\n>>> print(idna.decode('xn--eckwd4c7c.xn--zckzah'))\nドメイン.テスト\n```\n\nConversions can be applied at a per-label basis using the `ulabel` or\n`alabel` functions for specialized use cases.\n\n\n### Compatibility Mapping (UTS #46)\n\nThis library provides support for [Unicode IDNA Compatibility\nProcessing](https://unicode.org/reports/tr46/) which normalizes input from\ndifferent potential ways a user may input a domain prior to performing the IDNA\nconversion operations. This functionality, known as a\n[mapping](https://tools.ietf.org/html/rfc5895), is considered by the\nspecification to be a local user-interface issue distinct from IDNA\nconversion functionality.\n\nFor example, \"Königsgäßchen\" is not a permissible label as capital letters\nare not allowed. UTS 46 will convert this into lower case prior to applying\nthe IDNA conversion.\n\n```pycon\n>>> import idna\n>>> idna.encode('Königsgäßchen')\n...\nidna.core.InvalidCodepoint: Codepoint U+004B at position 1 of 'Königsgäßchen' not allowed\n>>> idna.encode('Königsgäßchen', uts46=True)\nb'xn--knigsgchen-b4a3dun'\n>>> idna.decode('xn--knigsgchen-b4a3dun')\n'königsgäßchen'\n```\n\nWhen performing a decode operation for display purposes, `decode()`\naccepts a `display=True` argument that leaves any `xn--` label that\nfails to decode unchanged. This is useful for user interface display\nwhere a domain is in use, the A-label form can be presented when it\nis not a valid IDN.\n\n\n## Exceptions\n\nAll errors raised during conversion derive from the `idna.IDNAError`\nbase class. The more specific exceptions ar<PATH>\n* `idna.IDNABidiError` — raised when a label contains an illegal\n combination of left-to-right and right-to-left characters.\n* `idna.InvalidCodepoint` — raised when a label contains a codepoint\n that is INVALID for IDNA.\n* `idna.InvalidCodepointContext` — raised when a CONTEXTO or CONTEXTJ\n codepoint appears in a position whose contextual requirements are\n not satisfied.\n\n\n## Command-line tool\n\nThe package supports command-line usage to convert domain names\nbetween their Unicode and ASCII-compatible forms. It can be run either\nas a module (`python3 -m idna`) or, once installed (such as with `uv\ntool` or `pipx`), via the `idna` scrip<PATH>\nMode can be specified with `-e`/`--encode` or `-d`/`--decode`, otherwise\nit will be chosen automatically based on the first input. Multiple\ndomains can be supplied either as arguments or through standard input.\nUTS #46 mapping is applied by default, which lets the tool accept\ninputs that aren't strictly valid IDNA 2008 by normalising them first,\npass `--strict` to disable UTS #46.\n\nConversion failures are reported on stderr together with the\noffending input; processing continues with the remaining domains and\nthe tool exits with a non-zero status if any conversion failed.\n\n\n## Additional Notes\n\n* **Version support**. This library supports Python 3.9 and higher.\n As this library serves as a low-level toolkit for a variety of\n applications, we strive to support all versions of Python that are\n not beyond end-of-life.\n\n* **Emoji**. It is an occasional request to support emoji domains in\n this library. Encoding of symbols like emoji is expressly prohibited by\n the IDNA technical standard, and emoji domains are broadly phased\n out across the domain industry due to associated security risks.\n\n* **Regenerating lookup tables**. The IDNA and UTS 46 functionality\n relies upon pre-calculated lookup tables, generated using the\n `idna-data` script in [`tools/`](tools/README.md).\n\n",
"description_content_type": "text/markdown",
"author_email": "Kim Davies <kim+pypi@gumleaf.org>",
"license_expression": "BSD-3-Clause",
@@ -0,0 +1,21 @@
{
"scenario": "held-back-constrained",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore",
"httpx==0.23.0"
],
"stdout_bytes": 469,
"stderr_bytes": 211
}
@@ -1,32 +1,15 @@
{
"scenario": "held-back-constrained",
"question": "SP-1 follow-up: does restating the installed set as explicit requirements make the resolver hold httpcore back to 0.15.x instead of breaking httpx? This decides whether PipDock must pass the full installed set on every plan.",
"expects_code": null,
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-held-back-constrained-c9qurkon\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-held-back-constrained-c9qurkon\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore",
"httpx==0.23.0"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 469,
"stderr_bytes": 211
}
{
"scenario": "held-back-constrained",
"question": "SP-1 follow-up: does restating the installed set as explicit requirements make the resolver hold httpcore back to 0.15.x instead of breaking httpx? This decides whether PipDock must pass the full installed set on every plan.",
"expects_code": null,
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
@@ -1,3 +1,3 @@
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-held-back-constrained-c9qurkon\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
@@ -0,0 +1,20 @@
{
"scenario": "held-back",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore"
],
"stdout_bytes": 32856,
"stderr_bytes": 199
}
+15 -31
View File
@@ -1,31 +1,15 @@
{
"scenario": "held-back",
"question": "SP-1 core question: httpx 0.23.0 requires httpcore<0.16, so httpcore cannot reach its 1.x latest. Does the engine name httpx as the blocker, or only report the resolved version? ANSWER: neither \u2014 both engines ignore the installed httpx entirely and plan httpcore 1.0.9, silently breaking it. Exit 0.",
"expects_code": null,
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-held-back-mm7fn80i\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-held-back-mm7fn80i\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 32856,
"stderr_bytes": 199
}
{
"scenario": "held-back",
"question": "SP-1 core question: httpx 0.23.0 requires httpcore<0.16, so httpcore cannot reach its 1.x latest. Does the engine name httpx as the blocker, or only report the resolved version? ANSWER: neither \u2014 both engines ignore the installed httpx entirely and plan httpcore 1.0.9, silently breaking it. Exit 0.",
"expects_code": null,
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
@@ -1,3 +1,3 @@
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-held-back-mm7fn80i\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
@@ -20,7 +20,7 @@
"name": "httpcore",
"version": "1.0.9",
"summary": "A minimal low-level HTTP client.",
"description": "# HTTP Core\n\n[![Test Suite](https://github.com/encode/httpcore/workflows/Test%20Suite/badge.svg)](https://github.com/encode/httpcore/actions)\n[![Package version](https://badge.fury.io/py/httpcore.svg)](https://pypi.org/project/httpcore/)\n\n> *Do one thing, and do it well.*\n\nThe HTTP Core package provides a minimal low-level HTTP client, which does\none thing only. Sending HTTP requests.\n\nIt does not provide any high level model abstractions over the API,\ndoes not handle redirects, multipart uploads, building authentication headers,\ntransparent HTTP caching, URL parsing, session cookie handling,\ncontent or charset decoding, handling JSON, environment based configuration\ndefaults, or any of that Jazz.\n\nSome things HTTP Core does do:\n\n* Sending HTTP requests.\n* Thread-safe / task-safe connection pooling.\n* HTTP(S) proxy & SOCKS proxy support.\n* Supports HTTP/1.1 and HTTP/2.\n* Provides both sync and async interfaces.\n* Async backend support for `asyncio` and `trio`.\n\n## Requirements\n\nPython 3.8+\n\n## Installation\n\nFor HTTP/1.1 only support, install with:\n\n```shell\n$ pip install httpcore\n```\n\nThere are also a number of optional extras available...\n\n```shell\n$ pip install httpcore['asyncio,trio,http2,socks']\n```\n\n## Sending requests\n\nSend an HTTP request:\n\n```python\nimport httpcore\n\nresponse = httpcore.request(\"GET\", \"https://www.example.com/\")\n\nprint(response)\n# <Response [200]>\nprint(response.status)\n# 200\nprint(response.headers)\n# [(b'Accept-Ranges', b'bytes'), (b'Age', b'557328'), (b'Cache-Control', b'max-age=604800'), ...]\nprint(response.content)\n# b'<!doctype html>\\n<html>\\n<head>\\n<title>Example Domain</title>\\n\\n<meta charset=\"utf-8\"/>\\n ...'\n```\n\nThe top-level `httpcore.request()` function is provided for convenience. In practice whenever you're working with `httpcore` you'll want to use the connection pooling functionality that it provides.\n\n```python\nimport httpcore\n\nhttp = httpcore.ConnectionPool()\nresponse = http.request(\"GET\", \"https://www.example.com/\")\n```\n\nOnce you're ready to get going, [head over to the documentation](https://www.encode.io/httpcore/).\n\n## Motivation\n\nYou *probably* don't want to be using HTTP Core directly. It might make sense if\nyou're writing something like a proxy service in Python, and you just want\nsomething at the lowest possible level, but more typically you'll want to use\na higher level client library, such as `httpx`.\n\nThe motivation for `httpcore` is:\n\n* To provide a reusable low-level client library, that other packages can then build on top of.\n* To provide a *really clear interface split* between the networking code and client logic,\n so that each is easier to understand and reason about in isolation.\n\n## Dependencies\n\nThe `httpcore` package has the following dependencies...\n\n* `h11`\n* `certifi`\n\nAnd the following optional extras...\n\n* `anyio` - Required by `pip install httpcore['asyncio']`.\n* `trio` - Required by `pip install httpcore['trio']`.\n* `h2` - Required by `pip install httpcore['http2']`.\n* `socksio` - Required by `pip install httpcore['socks']`.\n\n## Versioning\n\nWe use [SEMVER for our versioning policy](https://semver.org/).\n\nFor changes between package versions please see our [project changelog](CHANGELOG.md).\n\nWe recommend pinning your requirements either the most current major version, or a more specific version range:\n\n```python\npip install 'httpcore==1.*'\n```\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).\n\n## Version 1.0.9 (April 24th, 2025)\n\n- Resolve https://github.com/advisories/GHSA-vqfr-h8mv-ghfj with h11 dependency update. (#1008)\n\n## Version 1.0.8 (April 11th, 2025)\n\n- Fix `AttributeError` when importing on Python 3.14. (#1005)\n\n## Version 1.0.7 (November 15th, 2024)\n\n- Support `proxy=…` configuration on `ConnectionPool()`. (#974)\n\n## Version 1.0.6 (October 1st, 2024)\n\n- Relax `trio` dependency pinning. (#956)\n- Handle `trio` raising `NotImplementedError` on unsupported platforms. (#955)\n- Handle mapping `ssl.SSLError` to `httpcore.ConnectError`. (#918)\n\n## 1.0.5 (March 27th, 2024)\n\n- Handle `EndOfStream` exception for anyio backend. (#899)\n- Allow trio `0.25.*` series in package dependancies. (#903)\n\n## 1.0.4 (February 21st, 2024)\n\n- Add `target` request extension. (#888)\n- Fix support for connection `Upgrade` and `CONNECT` when some data in the stream has been read. (#882)\n\n## 1.0.3 (February 13th, 2024)\n\n- Fix support for async cancellations. (#880)\n- Fix trace extension when used with socks proxy. (#849)\n- Fix SSL context for connections using the \"wss\" scheme (#869)\n\n## 1.0.2 (November 10th, 2023)\n\n- Fix `float(\"inf\")` timeouts in `Event.wait` function. (#846)\n\n## 1.0.1 (November 3rd, 2023)\n\n- Fix pool timeout to account for Line truncated
"description": "# HTTP Core\n\n[![Test Suite](https://github.com/encode/httpcore/workflows/Test%20Suite/badge.svg)](https://github.com/encode/httpcore/actions)\n[![Package version](https://badge.fury.io/py/httpcore.svg)](https://pypi.org/project/httpcore/)\n\n> *Do one thing, and do it well.*\n\nThe HTTP Core package provides a minimal low-level HTTP client, which does\none thing only. Sending HTTP requests.\n\nIt does not provide any high level model abstractions over the API,\ndoes not handle redirects, multipart uploads, building authentication headers,\ntransparent HTTP caching, URL parsing, session cookie handling,\ncontent or charset decoding, handling JSON, environment based configuration\ndefaults, or any of that Jazz.\n\nSome things HTTP Core does d<PATH>\n* Sending HTTP requests.\n* Thread-safe / task-safe connection pooling.\n* HTTP(S) proxy & SOCKS proxy support.\n* Supports HTTP/1.1 and HTTP/2.\n* Provides both sync and async interfaces.\n* Async backend support for `asyncio` and `trio`.\n\n## Requirements\n\nPython 3.8+\n\n## Installation\n\nFor HTTP/1.1 only support, install wit<PATH>\nSend an HTTP request:\n\n```python\nimport httpcore\n\nresponse = httpcore.request(\"GET\", \"https://www.example.com/\")\n\nprint(response)\n# <Response [200]>\nprint(response.status)\n# 200\nprint(response.headers)\n# [(b'Accept-Ranges', b'bytes'), (b'Age', b'557328'), (b'Cache-Control', b'max-age=604800'), ...]\nprint(response.content)\n# b'<!doctype html>\\n<html>\\n<head>\\n<title>Example Domain</title>\\n\\n<meta charset=\"utf-8\"/>\\n ...'\n```\n\nThe top-level `httpcore.request()` function is provided for convenience. In practice whenever you're working with `httpcore` you'll want to use the connection pooling functionality that it provides.\n\n```python\nimport httpcore\n\nhttp = httpcore.ConnectionPool()\nresponse = http.request(\"GET\", \"https://www.example.com/\")\n```\n\nOnce you're ready to get going, [head over to the documentation](https://www.encode.io/httpcore/).\n\n## Motivation\n\nYou *probably* don't want to be using HTTP Core directly. It might make sense if\nyou're writing something like a proxy service in Python, and you just want\nsomething at the lowest possible level, but more typically you'll want to use\na higher level client library, such as `httpx`.\n\nThe motivation for `httpcore` i<PATH>\n* To provide a reusable low-level client library, that other packages can then build on top of.\n* To provide a *really clear interface split* between the networking code and client logic,\n so that each is easier to understand and reason about in isolation.\n\n## Dependencies\n\nThe `httpcore` package has the following dependencies...\n\n* `h11`\n* `certifi`\n\nAnd the following optional extras...\n\n* `anyio` - Required by `pip install httpcore['asyncio']`.\n* `trio` - Required by `pip install httpcore['trio']`.\n* `h2` - Required by `pip install httpcore['http2']`.\n* `socksio` - Required by `pip install httpcore['socks']`.\n\n## Versioning\n\nWe use [SEMVER for our versioning policy](https://semver.org/).\n\nFor changes between package versions please see our [project changelog](CHANGELOG.md).\n\nWe recommend pinning your requirements either the most current major version, or a more specific version rang<PATH>\npip install 'httpcore==1.*'\n```\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).\n\n## Version 1.0.9 (April 24th, 2025)\n\n- Resolve https://github.com/advisories/GHSA-vqfr-h8mv-ghfj with h11 dependency update. (#1008)\n\n## Version 1.0.8 (April 11th, 2025)\n\n- Fix `AttributeError` when importing on Python 3.14. (#1005)\n\n## Version 1.0.7 (November 15th, 2024)\n\n- Support `proxy=…` configuration on `ConnectionPool()`. (#974)\n\n## Version 1.0.6 (October 1st, 2024)\n\n- Relax `trio` dependency pinning. (#956)\n- Handle `trio` raising `NotImplementedError` on unsupported platforms. (#955)\n- Handle mapping `ssl.SSLError` to `httpcore.ConnectError`. (#918)\n\n## 1.0.5 (March 27th, 2024)\n\n- Handle `EndOfStream` exception for anyio backend. (#899)\n- Allow trio `0.25.*` series in package dependancies. (#903)\n\n## 1.0.4 (February 21st, 2024)\n\n- Add `target` request extension. (#888)\n- Fix support for connection `Upgrade` and `CONNECT` when some data in the stream has been read. (#882)\n\n## 1.0.3 (February 13th, 2024)\n\n- Fix support for async cancellations. (#880)\n- Fix trace extension when used with socks proxy. (#849)\n- Fix SSL context for connections using the \"wss\" scheme (#869)\n\n## 1.0.2 (November 10th, 2023)\n\n- Fix `float(\"inf\")` timeouts in `Event.wait` function. (#846)\n\n## 1.0.1 (November 3rd, 2023)\n\n- Fix pool timeout to account for the total time spent retrying. (#823)\n- Raise a neater RuntimeError when the correct async deps are not installed. (#826)\n- Add support for synchronous TLS-in-TLS streams. (#840)\n\n## 1.0.0 (OLine truncated
"description_content_type": "text/markdown",
"author_email": "Tom Christie <tom@tomchristie.com>",
"license_expression": "BSD-3-Clause",
@@ -95,7 +95,7 @@
"summary"
],
"summary": "A pure-Python, bring-your-own-I/O implementation of HTTP/1.1",
"description": "h11\n===\n\n.. image:: https://travis-ci.org/python-hyper/h11.svg?branch=master\n :target: https://travis-ci.org/python-hyper/h11\n :alt: Automated test status\n\n.. image:: https://codecov.io/gh/python-hyper/h11/branch/master/graph/badge.svg\n :target: https://codecov.io/gh/python-hyper/h11\n :alt: Test coverage\n\n.. image:: https://readthedocs.org/projects/h11/badge/?version=latest\n :target: http://h11.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status\n\nThis is a little HTTP/1.1 library written from scratch in Python,\nheavily inspired by `hyper-h2 <https://hyper-h2.readthedocs.io/>`_.\n\nIt's a \"bring-your-own-I/O\" library; h11 contains no IO code\nwhatsoever. This means you can hook h11 up to your favorite network\nAPI, and that could be anything you want: synchronous, threaded,\nasynchronous, or your own implementation of `RFC 6214\n<https://tools.ietf.org/html/rfc6214>`_ -- h11 won't judge you.\n(Compare this to the current state of the art, where every time a `new\nnetwork API <https://trio.readthedocs.io/>`_ comes along then someone\ngets to start over reimplementing the entire HTTP protocol from\nscratch.) Cory Benfield made an `excellent blog post describing the\nbenefits of this approach\n<https://lukasa.co.uk/2015/10/The_New_Hyper/>`_, or if you like video\nthen here's his `PyCon 2016 talk on the same theme\n<https://www.youtube.com/watch?v=7cC3_jGwl_U>`_.\n\nThis also means that h11 is not immediately useful out of the box:\nit's a toolkit for building programs that speak HTTP, not something\nthat could directly replace ``requests`` or ``twisted.web`` or\nwhatever. But h11 makes it much easier to implement something like\n``requests`` or ``twisted.web``.\n\nAt a high level, working with h11 goes like this:\n\n1) First, create an ``h11.Connection`` object to track the state of a\n single HTTP/1.1 connection.\n\n2) When you read data off the network, pass it to\n ``conn.receive_data(...)``; you'll get back a list of objects\n representing high-level HTTP \"events\".\n\n3) When you want to send a high-level HTTP event, create the\n corresponding \"event\" object and pass it to ``conn.send(...)``;\n this will give you back some bytes that you can then push out\n through the network.\n\nFor example, a client might instantiate and then send a\n``h11.Request`` object, then zero or more ``h11.Data`` objects for the\nrequest body (e.g., if this is a POST), and then a\n``h11.EndOfMessage`` to indicate the end of the message. Then the\nserver would then send back a ``h11.Response``, some ``h11.Data``, and\nits own ``h11.EndOfMessage``. If either side violates the protocol,\nyou'll get a ``h11.ProtocolError`` exception.\n\nh11 is suitable for implementing both servers and clients, and has a\npleasantly symmetric API: the events you send as a client are exactly\nthe ones that you receive as a server and vice-versa.\n\n`Here's an example of a tiny HTTP client\n<https://github.com/python-hyper/h11/blob/master/examples/basic-client.py>`_\n\nIt also has `a fine manual <https://h11.readthedocs.io/>`_.\n\nFAQ\n---\n\n*Whyyyyy?*\n\nI wanted to play with HTTP in `Curio\n<https://curio.readthedocs.io/en/latest/tutorial.html>`__ and `Trio\n<https://trio.readthedocs.io>`__, which at the time didn't have any\nHTTP libraries. So I thought, no big deal, Python has, like, a dozen\ndifferent implementations of HTTP, surely I can find one that's\nreusable. I didn't find one, but I did find Cory's call-to-arms\nblog-post. So I figured, well, fine, if I have to implement HTTP from\nscratch, at least I can make sure no-one *else* has to ever again.\n\n*Should I use it?*\n\nMaybe. You should be aware that it's a very young project. But, it's\nfeature complete and has an exhaustive test-suite and complete docs,\nso the next step is for people to try using it and see how it goes\n:-). If you do then please let us know -- if nothing else we'll want\nto talk to you before making any incompatible changes!\n\n*What are the features/limitations?*\n\nRoughly speaking, it's trying to be a robust, complete, and non-hacky\nimplementation of the first \"chapter\" of the HTTP/1.1 spec: `RFC 7230:\nHTTP/1.1 Message Syntax and Routing\n<https://tools.ietf.org/html/rfc7230>`_. That is, it mostly focuses on\nimplementing HTTP at the level of taking bytes on and off the wire,\nand the headers related to that, and tries to be anal about spec\nconformance. It doesn't know about higher-level concerns like URL\nrouting, conditional GETs, cross-origin cookie policies, or content\nnegotiation. But it does know how to take care of framing,\ncross-version differences in keep-alive handling, and the \"obsolete\nline folding\" rule, so you can focus your energies on the hard /\ninteresting parts for your application, and it tries to support the\nfull specification in the sense that any useful HTTP/1.1 conformant\napplication should be able to use h11.\n\nIt's pure Python, and has no dLine truncated
"description": "h11\n===\n\n.. image:: https://travis-ci.org/python-hyper/h11.svg?branch=master\n :target: https://travis-ci.org/python-hyper/h11\n :alt: Automated test status\n\n.. image:: https://codecov.io/gh/python-hyper/h11/branch/master/graph/badge.svg\n :target: https://codecov.io/gh/python-hyper/h11\n :alt: Test coverage\n\n.. image:: https://readthedocs.org/projects/h11/badge/?version=latest\n :target: http://h11.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status\n\nThis is a little HTTP/1.1 library written from scratch in Python,\nheavily inspired by `hyper-h2 <https://hyper-h2.readthedocs.io/>`_.\n\nIt's a \"bring-your-own-I/O\" library; h11 contains no IO code\nwhatsoever. This means you can hook h11 up to your favorite network\nAPI, and that could be anything you want: synchronous, threaded,\nasynchronous, or your own implementation of `RFC 6214\n<https://tools.ietf.org/html/rfc6214>`_ -- h11 won't judge you.\n(Compare this to the current state of the art, where every time a `new\nnetwork API <https://trio.readthedocs.io/>`_ comes along then someone\ngets to start over reimplementing the entire HTTP protocol from\nscratch.) Cory Benfield made an `excellent blog post describing the\nbenefits of this approach\n<https://lukasa.co.uk/2015/10/The_New_Hyper/>`_, or if you like video\nthen here's his `PyCon 2016 talk on the same theme\n<https://www.youtube.com/watch?v=7cC3_jGwl_U>`_.\n\nThis also means that h11 is not immediately useful out of the bo<PATH>\nAt a high level, working with h11 goes like this:\n\n1) First, create an ``h11.Connection`` object to track the state of a\n single HTTP/1.1 connection.\n\n2) When you read data off the network, pass it to\n ``conn.receive_data(...)``; you'll get back a list of objects\n representing high-level HTTP \"events\".\n\n3) When you want to send a high-level HTTP event, create the\n corresponding \"event\" object and pass it to ``conn.send(...)``;\n this will give you back some bytes that you can then push out\n through the network.\n\nFor example, a client might instantiate and then send a\n``h11.Request`` object, then zero or more ``h11.Data`` objects for the\nrequest body (e.g., if this is a POST), and then a\n``h11.EndOfMessage`` to indicate the end of the message. Then the\nserver would then send back a ``h11.Response``, some ``h11.Data``, and\nits own ``h11.EndOfMessage``. If either side violates the protocol,\nyou'll get a ``h11.ProtocolError`` exception.\n\nh11 is suitable for implementing both servers and clients, and has a\npleasantly symmetric API: the events you send as a client are exactly\nthe ones that you receive as a server and vice-versa.\n\n`Here's an example of a tiny HTTP client\n<https://github.com/python-hyper/h11/blob/master/examples/basic-client.py>`_\n\nIt also has `a fine manual <https://h11.readthedocs.io/>`_.\n\nFAQ\n---\n\n*Whyyyyy?*\n\nI wanted to play with HTTP in `Curio\n<https://curio.readthedocs.io/en/latest/tutorial.html>`__ and `Trio\n<https://trio.readthedocs.io>`__, which at the time didn't have any\nHTTP libraries. So I thought, no big deal, Python has, like, a dozen\ndifferent implementations of HTTP, surely I can find one that's\nreusable. I didn't find one, but I did find Cory's call-to-arms\nblog-post. So I figured, well, fine, if I have to implement HTTP from\nscratch, at least I can make sure no-one *else* has to ever again.\n\n*Should I use it?*\n\nMaybe. You should be aware that it's a very young project. But, it's\nfeature complete and has an exhaustive test-suite and complete docs,\nso the next step is for people to try using it and see how it goes\n:-). If you do then please let us know -- if nothing else we'll want\nto talk to you before making any incompatible changes!\n\n*What are the features/limitations?*\n\nRoughly speaking, it's trying to be a robust, complete, and non-hacky\nimplementation of the first \"chapter\" of the HTTP/1.1 spec: `RFC 7230:\nHTTP/1.1 Message Syntax and Routing\n<https://tools.ietf.org/html/rfc7230>`_. That is, it mostly focuses on\nimplementing HTTP at the level of taking bytes on and off the wire,\nand the headers related to that, and tries to be anal about spec\nconformance. It doesn't know about higher-level concerns like URL\nrouting, conditional GETs, cross-origin cookie policies, or content\nnegotiation. But it does know how to take care of framing,\ncross-version differences in keep-alive handling, and the \"obsolete\nline folding\" rule, so you can focus your energies on the hard /\ninteresting parts for your application, and it tries to support the\nfull specification in the sense that any useful HTTP/1.1 conformant\napplication should be able to use h11.\n\nIt's pure Python, and has no dependencies outside of the standard\nlibrary.\n\nIt has a test suite with 100.0% coverage for both statements and\nbranches.\n\nCurrently it supports Python 3 (testing on 3.8-3.12) and PyPy 3.\nThe last Python 2-compatible version waLine truncated
"home_page": "https://github.com/python-hyper/h11",
"author": "Nathaniel J. Smith",
"author_email": "njs@pobox.com",
@@ -0,0 +1,21 @@
{
"scenario": "impossible",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore>=1.0",
"httpx==0.23.0"
],
"stdout_bytes": 0,
"stderr_bytes": 454
}
+15 -32
View File
@@ -1,32 +1,15 @@
{
"scenario": "impossible",
"question": "Unsatisfiable set: how is ResolutionImpossible reported and is it attributable?",
"expects_code": "PD-RES-001",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-impossible-6ja7hyci\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-impossible-6ja7hyci\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"httpcore>=1.0",
"httpx==0.23.0"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 454
}
{
"scenario": "impossible",
"question": "Unsatisfiable set: how is ResolutionImpossible reported and is it attributable?",
"expects_code": "PD-RES-001",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
@@ -1,5 +1,5 @@
ERROR: Cannot install httpcore>=1.0 and httpx==0.23.0 because these package versions have conflicting dependencies.
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-impossible-6ja7hyci\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
@@ -0,0 +1,22 @@
{
"scenario": "network-unreachable",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"--index-url",
"http://127.0.0.1:1/simple",
"idna"
],
"stdout_bytes": 0,
"stderr_bytes": 1947
}
@@ -1,31 +1,13 @@
{
"scenario": "network-unreachable",
"question": "Index unreachable \u2014 connection refused rather than DNS or TLS failure.",
"expects_code": "PD-NET-001",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-network-unreachable-brhd_kqy\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-network-unreachable-brhd_kqy\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"--index-url",
"http://127.0.0.1:1/simple",
"idna"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 1947
}
{
"scenario": "network-unreachable",
"question": "Index unreachable \u2014 connection refused rather than DNS or TLS failure.",
"expects_code": "PD-NET-001",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null
}
@@ -1,7 +1,7 @@
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0x000001A92FBCFBC0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0x000001A9308A93A0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0x000001A9309E0DD0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0x000001A9309E1040>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0x000001A9309E12B0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0xADDR>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0xADDR>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0xADDR>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0xADDR>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPConnection object at 0xADDR>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it')': /simple/idna/
ERROR: Could not find a version that satisfies the requirement idna (from versions: none)
ERROR: No matching distribution found for idna
@@ -0,0 +1,20 @@
{
"scenario": "not-found",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"pipdock-no-such-package-9f3a2b"
],
"stdout_bytes": 0,
"stderr_bytes": 388
}
+13 -29
View File
@@ -1,29 +1,13 @@
{
"scenario": "not-found",
"question": "Unknown distribution name.",
"expects_code": "PD-PKG-002",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-not-found-kac3nuir\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-not-found-kac3nuir\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"pipdock-no-such-package-9f3a2b"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 388
}
{
"scenario": "not-found",
"question": "Unknown distribution name.",
"expects_code": "PD-PKG-002",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null
}
@@ -1,5 +1,5 @@
ERROR: Could not find a version that satisfies the requirement pipdock-no-such-package-9f3a2b (from versions: none)
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-not-found-kac3nuir\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
ERROR: No matching distribution found for pipdock-no-such-package-9f3a2b
@@ -0,0 +1,20 @@
{
"scenario": "report-encoding-crash",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"idna"
],
"stdout_bytes": 788,
"stderr_bytes": 3419
}
@@ -1,28 +1,12 @@
{
"scenario": "report-encoding-crash",
"question": "Evidence for the pip --report UnicodeEncodeError on Windows/cp1252. Kept as a fixture so a regression in the UTF-8 mitigation is recognisable.",
"expects_code": null,
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-report-encoding-crash-h4_safl0\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-report-encoding-crash-h4_safl0\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"idna"
],
"extra_env": null,
"exit_code": 2,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0,
"stdout_bytes": 788,
"stderr_bytes": 3419
}
{
"scenario": "report-encoding-crash",
"question": "Evidence for the pip --report UnicodeEncodeError on Windows/cp1252. Kept as a fixture so a regression in the UTF-8 mitigation is recognisable.",
"expects_code": null,
"engine": "pip",
"extra_env": null,
"exit_code": 2,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0
}
@@ -1,41 +1,41 @@
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
ERROR: Exception:
Traceback (most recent call last):
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 106, in _run_wrapper
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 106, in _run_wrapper
status = _inner_run()
^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 97, in _inner_run
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\base_command.py", line 97, in _inner_run
return self.run(options, args)
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_internal\cli\req_command.py", line 67, in wrapper
File "<WORK>\venv\Lib\site-packages\pip\_internal\cli\req_command.py", line 67, in wrapper
return func(self, options, args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_internal\commands\install.py", line 393, in run
File "<WORK>\venv\Lib\site-packages\pip\_internal\commands\install.py", line 393, in run
print_json(data=report.to_dict())
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\__init__.py", line 106, in print_json
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\__init__.py", line 106, in print_json
get_console().print_json(
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 1787, in print_json
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 1787, in print_json
self.print(json_renderable, soft_wrap=True)
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 1678, in print
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 1678, in print
with self:
^^^^
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 864, in __exit__
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 864, in __exit__
self._exit_buffer()
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 822, in _exit_buffer
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 822, in _exit_buffer
self._check_buffer()
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 2019, in _check_buffer
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 2019, in _check_buffer
self._write_buffer()
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 2055, in _write_buffer
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\console.py", line 2055, in _write_buffer
legacy_windows_render(buffer, LegacyWindowsTerm(self.file))
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\_windows_renderer.py", line 17, in legacy_windows_render
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\_windows_renderer.py", line 17, in legacy_windows_render
term.write_styled(text, style)
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\_win32_console.py", line 441, in write_styled
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\_win32_console.py", line 441, in write_styled
self.write_text(text)
File "C:\Users\Anon\AppData\Local\Temp\pd-pip-report-encoding-crash-h4_safl0\venv\Lib\site-packages\pip\_vendor\rich\_win32_console.py", line 402, in write_text
File "<WORK>\venv\Lib\site-packages\pip\_vendor\rich\_win32_console.py", line 402, in write_text
self.write(text)
File "C:\Users\Anon\AppData\Local\Programs\Python\Python312\Lib\encodings\cp1252.py", line 19, in encode
File "<PATH>\cp1252.py", line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_table)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'charmap' codec can't encode characters in position 860-863: character maps to <undefined>
@@ -0,0 +1,20 @@
{
"scenario": "requires-python",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"scipy==1.7.3"
],
"stdout_bytes": 0,
"stderr_bytes": 1066
}
@@ -1,29 +1,13 @@
{
"scenario": "requires-python",
"question": "Requires-Python mismatch against the running interpreter. ANSWER: pip refuses with the same 'No matching distribution found' text it uses for an unknown name, so the two are indistinguishable from stderr; uv ignores the constraint and plans the install. Hence PD-PKG-001 is raised by pipdock-core's compat module before either engine runs, and these fixtures record what the engines do instead.",
"expects_code": "PD-PKG-002",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-requires-python-ez076pnc\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-requires-python-ez076pnc\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"scipy==1.7.3"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 1066
}
{
"scenario": "requires-python",
"question": "Requires-Python mismatch against the running interpreter. ANSWER: pip refuses with the same 'No matching distribution found' text it uses for an unknown name, so the two are indistinguishable from stderr; uv ignores the constraint and plans the install. Hence PD-PKG-001 is raised by pipdock-core's compat module before either engine runs, and these fixtures record what the engines do instead.",
"expects_code": "PD-PKG-002",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null
}
@@ -2,5 +2,5 @@ ERROR: Ignored the following yanked versions: 1.11.0, 1.14.0rc1
ERROR: Could not find a version that satisfies the requirement scipy==1.7.3 (from versions: 0.8.0, 0.9.0, 0.10.0, 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.14.0, 0.14.1, 0.15.0, 0.15.1, 0.16.0, 0.16.1, 0.17.0, 0.17.1, 0.18.0, 0.18.1, 0.19.0, 0.19.1, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.6.0, 1.6.1, 1.9.2, 1.9.3, 1.11.0rc1, 1.11.0rc2, 1.11.1, 1.11.2, 1.11.3, 1.11.4, 1.12.0rc1, 1.12.0rc2, 1.12.0, 1.13.0rc1, 1.13.0, 1.13.1, 1.14.0rc2, 1.14.0, 1.14.1, 1.15.0rc1, 1.15.0rc2, 1.15.0, 1.15.1, 1.15.2, 1.15.3, 1.16.0rc1, 1.16.0rc2, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.17.0rc1, 1.17.0rc2, 1.17.0, 1.17.1, 1.18.0rc1, 1.18.0rc2, 1.18.0)
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-requires-python-ez076pnc\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
ERROR: No matching distribution found for scipy==1.7.3
@@ -0,0 +1,20 @@
{
"scenario": "yanked",
"engine_version": "pip 25.0.1 (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<WORK>\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--no-cache-dir",
"--dry-run",
"--quiet",
"--report",
"-",
"urllib3==2.0.0"
],
"stdout_bytes": 8246,
"stderr_bytes": 685
}
+13 -29
View File
@@ -1,29 +1,13 @@
{
"scenario": "yanked",
"question": "Yanked release explicitly requested. Does the engine flag the yank, and where \u2014 structured field or stderr text?",
"expects_code": "PD-PKG-003",
"engine": "pip",
"engine_version": "pip 25.0.1 from C:\\Users\\Anon\\AppData\\Local\\Temp\\pd-pip-yanked-id7w4uu1\\venv\\Lib\\site-packages\\pip (python 3.12)",
"python": "Python 3.12.10",
"argv": [
"<TMP>\\pd-pip-yanked-id7w4uu1\\venv\\Scripts\\python.exe",
"-m",
"pip",
"install",
"-U",
"--dry-run",
"--quiet",
"--report",
"-",
"urllib3==2.0.0"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 8246,
"stderr_bytes": 685
}
{
"scenario": "yanked",
"question": "Yanked release explicitly requested. Does the engine flag the yank, and where \u2014 structured field or stderr text?",
"expects_code": "PD-PKG-003",
"engine": "pip",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null
}
+1 -1
View File
@@ -2,4 +2,4 @@ WARNING: The candidate selected for download or install is a yanked version: 'ur
Reason for being yanked: Truncated response bodies when streaming a large compressed body. Upgrade to at least 2.0.2 (See: https://github.com/urllib3/urllib3/issues/3009)
[notice] A new release of pip is available: 25.0.1 -> 26.1.2
[notice] To update, run: C:\Users\Anon\AppData\Local\Temp\pd-pip-yanked-id7w4uu1\venv\Scripts\python.exe -m pip install --upgrade pip
[notice] To update, run: <WORK>\venv\Scripts\python.exe -m pip install --upgrade pip
+1 -1
View File
@@ -20,7 +20,7 @@
"name": "urllib3",
"version": "2.0.0",
"summary": "HTTP library with thread-safe connection pooling, file post, and more.",
"description": "<h1 align=\"center\">\n\n![urllib3](https://github.com/urllib3/urllib3/raw/main/docs/_static/banner_github.svg)\n\n</h1>\n\n<p align=\"center\">\n <a href=\"https://pypi.org/project/urllib3\"><img alt=\"PyPI Version\" src=\"https://img.shields.io/pypi/v/urllib3.svg?maxAge=86400\" /></a>\n <a href=\"https://pypi.org/project/urllib3\"><img alt=\"Python Versions\" src=\"https://img.shields.io/pypi/pyversions/urllib3.svg?maxAge=86400\" /></a>\n <a href=\"https://discord.gg/urllib3\"><img alt=\"Join our Discord\" src=\"https://img.shields.io/discord/756342717725933608?color=%237289da&label=discord\" /></a>\n <a href=\"https://github.com/urllib3/urllib3/actions?query=workflow%3ACI\"><img alt=\"Coverage Status\" src=\"https://img.shields.io/badge/coverage-100%25-success\" /></a>\n <a href=\"https://github.com/urllib3/urllib3/actions?query=workflow%3ACI\"><img alt=\"Build Status on GitHub\" src=\"https://github.com/urllib3/urllib3/workflows/CI/badge.svg\" /></a>\n <a href=\"https://urllib3.readthedocs.io\"><img alt=\"Documentation Status\" src=\"https://readthedocs.org/projects/urllib3/badge/?version=latest\" /></a><br>\n <a href=\"https://deps.dev/pypi/urllib3\"><img alt=\"OpenSSF Scorecard\" src=\"https://api.securityscorecards.dev/projects/github.com/urllib3/urllib3/badge\" /></a>\n <a href=\"https://slsa.dev\"><img alt=\"SLSA 3\" src=\"https://slsa.dev/images/gh-badge-level3.svg\" /></a>\n <a href=\"https://bestpractices.coreinfrastructure.org/projects/6227\"><img alt=\"CII Best Practices\" src=\"https://bestpractices.coreinfrastructure.org/projects/6227/badge\" /></a>\n</p>\n\nurllib3 is a powerful, *user-friendly* HTTP client for Python. Much of the\nPython ecosystem already uses urllib3 and you should too.\nurllib3 brings many critical features that are missing from the Python\nstandard libraries:\n\n- Thread safety.\n- Connection pooling.\n- Client-side SSL/TLS verification.\n- File uploads with multipart encoding.\n- Helpers for retrying requests and dealing with HTTP redirects.\n- Support for gzip, deflate, brotli, and zstd encoding.\n- Proxy support for HTTP and SOCKS.\n- 100% test coverage.\n\nurllib3 is powerful and easy to use:\n\n```python3\n>>> import urllib3\n>>> http = urllib3.PoolManager()\n>>> resp = http.request(\"GET\", \"http://httpbin.org/robots.txt\")\n>>> resp.status\n200\n>>> resp.data\nb\"User-agent: *\\nDisallow: /deny\\n\"\n```\n\n## Installing\n\nurllib3 can be installed with [pip](https://pip.pypa.io):\n\n```bash\n$ python -m pip install urllib3\n```\n\nAlternatively, you can grab the latest source code from [GitHub](https://github.com/urllib3/urllib3):\n\n```bash\n$ git clone https://github.com/urllib3/urllib3.git\n$ cd urllib3\n$ pip install .\n```\n\n\n## Documentation\n\nurllib3 has usage and reference documentation at [urllib3.readthedocs.io](https://urllib3.readthedocs.io).\n\n\n## Community\n\nurllib3 has a [community Discord channel](https://discord.gg/urllib3) for asking questions and\ncollaborating with other contributors. Drop by and say hello 👋\n\n\n## Contributing\n\nurllib3 happily accepts contributions. Please see our\n[contributing documentation](https://urllib3.readthedocs.io/en/latest/contributing.html)\nfor some tips on getting started.\n\n\n## Security Disclosures\n\nTo report a security vulnerability, please use the\n[Tidelift security contact](https://tidelift.com/security).\nTidelift will coordinate the fix and disclosure with maintainers.\n\n\n## Maintainers\n\n- [@sethmlarson](https://github.com/sethmlarson) (Seth M. Larson)\n- [@pquentin](https://github.com/pquentin) (Quentin Pradet)\n- [@theacodes](https://github.com/theacodes) (Thea Flowers)\n- [@haikuginger](https://github.com/haikuginger) (Jess Shapiro)\n- [@lukasa](https://github.com/lukasa) (Cory Benfield)\n- [@sigmavirus24](https://github.com/sigmavirus24) (Ian Stapleton Cordasco)\n- [@shazow](https://github.com/shazow) (Andrey Petrov)\n\n👋\n\n\n## Sponsorship\n\nIf your company benefits from this library, please consider [sponsoring its\ndevelopment](https://urllib3.readthedocs.io/en/latest/sponsors.html).\n\n\n## For Enterprise\n\nProfessional support for urllib3 is available as part of the [Tidelift\nSubscription][1]. Tidelift gives software development teams a single source for\npurchasing and maintaining their software, with professional grade assurances\nfrom the experts who know it best, while seamlessly integrating with existing\ntools.\n\n[1]: https://tidelift.com/subscription/pkg/pypi-urllib3?utm_source=pypi-urllib3&utm_medium=referral&utm_campaign=readme\n",
"description": "<h1 align=\"center\">\n\n![urllib3](https://github.com/urllib3/urllib3/raw/main/docs/_static/banner_github.svg)\n\n</h1>\n\n<p align=\"center\">\n <a href=\"https://pypi.org/project/urllib3\"><img alt=\"PyPI Version\" src=\"https://img.shields.io/pypi/v/urllib3.svg?maxAge=86400\" /></a>\n <a href=\"https://pypi.org/project/urllib3\"><img alt=\"Python Versions\" src=\"https://img.shields.io/pypi/pyversions/urllib3.svg?maxAge=86400\" /></a>\n <a href=\"https://discord.gg/urllib3\"><img alt=\"Join our Discord\" src=\"https://img.shields.io/discord/756342717725933608?color=%237289da&label=discord\" /></a>\n <a href=\"https://github.com/urllib3/urllib3/actions?query=workflow%3ACI\"><img alt=\"Coverage Status\" src=\"https://img.shields.io/badge/coverage-100%25-success\" /></a>\n <a href=\"https://github.com/urllib3/urllib3/actions?query=workflow%3ACI\"><img alt=\"Build Status on GitHub\" src=\"https://github.com/urllib3/urllib3/workflows/CI/badge.svg\" /></a>\n <a href=\"https://urllib3.readthedocs.io\"><img alt=\"Documentation Status\" src=\"https://readthedocs.org/projects/urllib3/badge/?version=latest\" /></a><br>\n <a href=\"https://deps.dev/pypi/urllib3\"><img alt=\"OpenSSF Scorecard\" src=\"https://api.securityscorecards.dev/projects/github.com/urllib3/urllib3/badge\" /></a>\n <a href=\"https://slsa.dev\"><img alt=\"SLSA 3\" src=\"https://slsa.dev/images/gh-badge-level3.svg\" /></a>\n <a href=\"https://bestpractices.coreinfrastructure.org/projects/6227\"><img alt=\"CII Best Practices\" src=\"https://bestpractices.coreinfrastructure.org/projects/6227/badge\" /></a>\n</p>\n\nurllib3 is a powerful, *user-friendly* HTTP client for Python. Much of the\nPython ecosystem already uses urllib3 and you should too.\nurllib3 brings many critical features that are missing from the Python\nstandard librarie<PATH>\n- Client-side SSL/TLS verification.\n- File uploads with multipart encoding.\n- Helpers for retrying requests and dealing with HTTP redirects.\n- Support for gzip, deflate, brotli, and zstd encoding.\n- Proxy support for HTTP and SOCKS.\n- 100% test coverage.\n\nurllib3 is powerful and easy to us<PATH>\n>>> import urllib3\n>>> http = urllib3.PoolManager()\n>>> resp = http.request(\"GET\", \"http://httpbin.org/robots.txt\")\n>>> resp.status\n200\n>>> resp.data\nb\"User-agent: *\\nDisallow: /deny\\n\"\n```\n\n## Installing\n\nurllib3 can be installed with [pip](https://pip.pypa.io):\n\n```bash\n$ python -m pip install urllib3\n```\n\nAlternatively, you can grab the latest source code from [GitHub](https://github.com/urllib3/urllib3):\n\n```bash\n$ git clone https://github.com/urllib3/urllib3.git\n$ cd urllib3\n$ pip install .\n```\n\n\n## Documentation\n\nurllib3 has usage and reference documentation at [urllib3.readthedocs.io](https://urllib3.readthedocs.io).\n\n\n## Community\n\nurllib3 has a [community Discord channel](https://discord.gg/urllib3) for asking questions and\ncollaborating with other contributors. Drop by and say hello 👋\n\n\n## Contributing\n\nurllib3 happily accepts contributions. Please see our\n[contributing documentation](https://urllib3.readthedocs.io/en/latest/contributing.html)\nfor some tips on getting started.\n\n\n## Security Disclosures\n\nTo report a security vulnerability, please use the\n[Tidelift security contact](https://tidelift.com/security).\nTidelift will coordinate the fix and disclosure with maintainers.\n\n\n## Maintainers\n\n- [@sethmlarson](https://github.com/sethmlarson) (Seth M. Larson)\n- [@pquentin](https://github.com/pquentin) (Quentin Pradet)\n- [@theacodes](https://github.com/theacodes) (Thea Flowers)\n- [@haikuginger](https://github.com/haikuginger) (Jess Shapiro)\n- [@lukasa](https://github.com/lukasa) (Cory Benfield)\n- [@sigmavirus24](https://github.com/sigmavirus24) (Ian Stapleton Cordasco)\n- [@shazow](https://github.com/shazow) (Andrey Petrov)\n\n👋\n\n\n## Sponsorship\n\nIf your company benefits from this library, please consider [sponsoring its\ndevelopment](https://urllib3.readthedocs.io/en/latest/sponsors.html).\n\n\n## For Enterprise\n\nProfessional support for urllib3 is available as part of the [Tidelift\nSubscription][1]. Tidelift gives software development teams a single source for\npurchasing and maintaining their software, with professional grade assurances\nfrom the experts who know it best, while seamlessly integrating with existing\ntools.\n\n[1]: https://tidelift.com/subscription/pkg/pypi-urllib3?utm_source=pypi-urllib3&utm_medium=referral&utm_campaign=readme\n",
"description_content_type": "text/markdown",
"keywords": [
"filepost",
@@ -0,0 +1,17 @@
{
"scenario": "build-backend-failure",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"numpy==1.19.5",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 868
}
@@ -1,26 +1,13 @@
{
"scenario": "build-backend-failure",
"question": "sdist build backend failure (PEP 517 backend unavailable).",
"expects_code": "PD-BLD-002",
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"numpy==1.19.5",
"--python",
"<TMP>\\pd-uv-build-backend-failure-x06525p0\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 861
}
{
"scenario": "build-backend-failure",
"question": "sdist build backend failure (PEP 517 backend unavailable).",
"expects_code": "PD-BLD-002",
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null
}
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-build-backend-failure-x06525p0\venv
Resolved 1 package in 325ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 1 package in <DURATION>
Building numpy==1.19.5
× Failed to build `numpy==1.19.5`
├─▶ The build backend returned an error
@@ -10,7 +10,7 @@ Resolved 1 package in 325ms
Traceback (most recent call last):
File "<string>", line 8, in <module>
File
"C:\Users\Anon\AppData\Local\uv\cache\builds-v0\.tmpM6qzfj\Lib\site-packages\setuptools\__init__.py",
"<PATH>\__init__.py",
line 9, in <module>
import distutils.core
ModuleNotFoundError: No module named 'distutils'
@@ -0,0 +1,18 @@
{
"scenario": "clean-upgrade",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"idna",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 234
}
+15 -29
View File
@@ -1,29 +1,15 @@
{
"scenario": "clean-upgrade",
"question": "Baseline: what does an unconstrained upgrade plan look like?",
"expects_code": null,
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"idna",
"--python",
"<TMP>\\pd-uv-clean-upgrade-py2bn54p\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 234
}
{
"scenario": "clean-upgrade",
"question": "Baseline: what does an unconstrained upgrade plan look like?",
"expects_code": null,
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0
}
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-clean-upgrade-py2bn54p\venv
Resolved 1 package in 293ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 1 package in <DURATION>
Would download 1 package
Would uninstall 1 package
Would install 1 package
@@ -0,0 +1,19 @@
{
"scenario": "held-back-constrained",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"httpcore",
"httpx==0.23.0",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 189
}
@@ -1,30 +1,15 @@
{
"scenario": "held-back-constrained",
"question": "SP-1 follow-up: does restating the installed set as explicit requirements make the resolver hold httpcore back to 0.15.x instead of breaking httpx? This decides whether PipDock must pass the full installed set on every plan.",
"expects_code": null,
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"httpcore",
"httpx==0.23.0",
"--python",
"<TMP>\\pd-uv-held-back-constrained-66ncg_2i\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 189
}
{
"scenario": "held-back-constrained",
"question": "SP-1 follow-up: does restating the installed set as explicit requirements make the resolver hold httpcore back to 0.15.x instead of breaking httpx? This decides whether PipDock must pass the full installed set on every plan.",
"expects_code": null,
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
@@ -1,4 +1,4 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-held-back-constrained-66ncg_2i\venv
Resolved 8 packages in 406ms
Checked 8 packages in 1ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 8 packages in <DURATION>
Checked 8 packages in <DURATION>
Would make no changes
@@ -0,0 +1,18 @@
{
"scenario": "held-back",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"httpcore",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 276
}
+15 -29
View File
@@ -1,29 +1,15 @@
{
"scenario": "held-back",
"question": "SP-1 core question: httpx 0.23.0 requires httpcore<0.16, so httpcore cannot reach its 1.x latest. Does the engine name httpx as the blocker, or only report the resolved version? ANSWER: neither \u2014 both engines ignore the installed httpx entirely and plan httpcore 1.0.9, silently breaking it. Exit 0.",
"expects_code": null,
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"httpcore",
"--python",
"<TMP>\\pd-uv-held-back-6hmjod7b\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 276
}
{
"scenario": "held-back",
"question": "SP-1 core question: httpx 0.23.0 requires httpcore<0.16, so httpcore cannot reach its 1.x latest. Does the engine name httpx as the blocker, or only report the resolved version? ANSWER: neither \u2014 both engines ignore the installed httpx entirely and plan httpcore 1.0.9, silently breaking it. Exit 0.",
"expects_code": null,
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
+2 -2
View File
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-held-back-6hmjod7b\venv
Resolved 3 packages in 491ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 3 packages in <DURATION>
Would download 2 packages
Would uninstall 2 packages
Would install 2 packages
@@ -0,0 +1,19 @@
{
"scenario": "impossible",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"httpcore>=1.0",
"httpx==0.23.0",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 443
}
+15 -30
View File
@@ -1,30 +1,15 @@
{
"scenario": "impossible",
"question": "Unsatisfiable set: how is ResolutionImpossible reported and is it attributable?",
"expects_code": "PD-RES-001",
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"httpcore>=1.0",
"httpx==0.23.0",
"--python",
"<TMP>\\pd-uv-impossible-9aivzjzy\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 443
}
{
"scenario": "impossible",
"question": "Unsatisfiable set: how is ResolutionImpossible reported and is it attributable?",
"expects_code": "PD-RES-001",
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [
"httpx==0.23.0"
],
"seed_exit_code": 0
}
@@ -1,4 +1,4 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-impossible-9aivzjzy\venv
Using Python 3.12.10 environment at: <WORK>\venv
× No solution found when resolving dependencies:
╰─▶ Because httpx==0.23.0 depends on httpcore>=0.15.0,<0.16.0 and you
require httpcore>=1.0, we can conclude that your requirements and
@@ -0,0 +1,20 @@
{
"scenario": "network-unreachable",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"--index-url",
"http://127.0.0.1:1/simple",
"idna",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 471
}
@@ -1,29 +1,13 @@
{
"scenario": "network-unreachable",
"question": "Index unreachable \u2014 connection refused rather than DNS or TLS failure.",
"expects_code": "PD-NET-001",
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"--index-url",
"http://127.0.0.1:1/simple",
"idna",
"--python",
"<TMP>\\pd-uv-network-unreachable-ba6imiic\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 2,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 471
}
{
"scenario": "network-unreachable",
"question": "Index unreachable \u2014 connection refused rather than DNS or TLS failure.",
"expects_code": "PD-NET-001",
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 2,
"seed": [],
"seed_exit_code": null
}
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-network-unreachable-ba6imiic\venv
error: Request failed after 3 retries in 16.2s
Using Python 3.12.10 environment at: <WORK>\venv
error: Request failed after 3 retries in <DURATION>
Caused by: Failed to fetch: `http://127.0.0.1:1/simple/idna/`
Caused by: error sending request for url (http://127.0.0.1:1/simple/idna/)
Caused by: client error (Connect)
@@ -0,0 +1,18 @@
{
"scenario": "not-found",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"pipdock-no-such-package-9f3a2b",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 352
}
+13 -27
View File
@@ -1,27 +1,13 @@
{
"scenario": "not-found",
"question": "Unknown distribution name.",
"expects_code": "PD-PKG-002",
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"pipdock-no-such-package-9f3a2b",
"--python",
"<TMP>\\pd-uv-not-found-_xu4q_pz\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 352
}
{
"scenario": "not-found",
"question": "Unknown distribution name.",
"expects_code": "PD-PKG-002",
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 1,
"seed": [],
"seed_exit_code": null
}
+1 -1
View File
@@ -1,4 +1,4 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-not-found-_xu4q_pz\venv
Using Python 3.12.10 environment at: <WORK>\venv
× No solution found when resolving dependencies:
╰─▶ Because pipdock-no-such-package-9f3a2b was not found in the package
registry and you require pipdock-no-such-package-9f3a2b, we can conclude
@@ -0,0 +1,18 @@
{
"scenario": "report-encoding-crash",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"idna",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 242
}
@@ -1,26 +1,12 @@
{
"scenario": "report-encoding-crash",
"question": "Evidence for the pip --report UnicodeEncodeError on Windows/cp1252. Kept as a fixture so a regression in the UTF-8 mitigation is recognisable.",
"expects_code": null,
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"idna",
"--python",
"<TMP>\\pd-uv-report-encoding-crash-sjbyqk1o\\venv\\Scripts\\python.exe"
],
"extra_env": null,
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0,
"stdout_bytes": 0,
"stderr_bytes": 242
}
{
"scenario": "report-encoding-crash",
"question": "Evidence for the pip --report UnicodeEncodeError on Windows/cp1252. Kept as a fixture so a regression in the UTF-8 mitigation is recognisable.",
"expects_code": null,
"engine": "uv",
"extra_env": null,
"exit_code": 0,
"seed": [
"idna==3.4"
],
"seed_exit_code": 0
}
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-report-encoding-crash-sjbyqk1o\venv
Resolved 1 package in 343ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 1 package in <DURATION>
Would download 1 package
Would uninstall 1 package
Would install 1 package
@@ -0,0 +1,18 @@
{
"scenario": "requires-python",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"scipy==1.7.3",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 219
}
@@ -1,27 +1,13 @@
{
"scenario": "requires-python",
"question": "Requires-Python mismatch against the running interpreter. ANSWER: pip refuses with the same 'No matching distribution found' text it uses for an unknown name, so the two are indistinguishable from stderr; uv ignores the constraint and plans the install. Hence PD-PKG-001 is raised by pipdock-core's compat module before either engine runs, and these fixtures record what the engines do instead.",
"expects_code": null,
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"scipy==1.7.3",
"--python",
"<TMP>\\pd-uv-requires-python-tqk5qbo0\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 219
}
{
"scenario": "requires-python",
"question": "Requires-Python mismatch against the running interpreter. ANSWER: pip refuses with the same 'No matching distribution found' text it uses for an unknown name, so the two are indistinguishable from stderr; uv ignores the constraint and plans the install. Hence PD-PKG-001 is raised by pipdock-core's compat module before either engine runs, and these fixtures record what the engines do instead.",
"expects_code": null,
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null
}
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-requires-python-tqk5qbo0\venv
Resolved 2 packages in 400ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 2 packages in <DURATION>
Would download 2 packages
Would install 2 packages
+ numpy==1.22.4
@@ -0,0 +1,18 @@
{
"scenario": "yanked",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"<PATH>\\uv.exe",
"pip",
"install",
"-U",
"--no-cache",
"--dry-run",
"urllib3==2.0.0",
"--python",
"<WORK>\\venv\\Scripts\\python.exe"
],
"stdout_bytes": 0,
"stderr_bytes": 386
}
+13 -27
View File
@@ -1,27 +1,13 @@
{
"scenario": "yanked",
"question": "Yanked release explicitly requested. Does the engine flag the yank, and where \u2014 structured field or stderr text?",
"expects_code": "PD-PKG-003",
"engine": "uv",
"engine_version": "uv 0.11.32 (3010295ae 2026-07-23 x86_64-pc-windows-msvc)",
"python": "Python 3.12.10",
"argv": [
"spikes\\.venv-uv-latest\\Scripts\\uv.exe",
"pip",
"install",
"-U",
"--dry-run",
"urllib3==2.0.0",
"--python",
"<TMP>\\pd-uv-yanked-q_o2x7qx\\venv\\Scripts\\python.exe"
],
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null,
"stdout_bytes": 0,
"stderr_bytes": 386
}
{
"scenario": "yanked",
"question": "Yanked release explicitly requested. Does the engine flag the yank, and where \u2014 structured field or stderr text?",
"expects_code": "PD-PKG-003",
"engine": "uv",
"extra_env": {
"PYTHONIOENCODING": "utf-8",
"PYTHONUTF8": "1"
},
"exit_code": 0,
"seed": [],
"seed_exit_code": null
}
+2 -2
View File
@@ -1,5 +1,5 @@
Using Python 3.12.10 environment at: C:\Users\Anon\AppData\Local\Temp\pd-uv-yanked-q_o2x7qx\venv
Resolved 1 package in 740ms
Using Python 3.12.10 environment at: <WORK>\venv
Resolved 1 package in <DURATION>
Would download 1 package
Would install 1 package
+ urllib3==2.0.0
+97 -12
View File
@@ -19,6 +19,7 @@ from __future__ import annotations
import argparse
import json
import os
import re
import shutil
import subprocess
import sys
@@ -233,15 +234,20 @@ def capture(engine: str, scenario: Scenario, uv_exe: Path | None, out_root: Path
if seed_result.returncode != 0:
print(f" ! seed failed ({seed_result.returncode}); capturing anyway")
# Cache-free on purpose. A warm cache turns "Downloading numpy-1.19.5.zip (7.3 MB)" into
# "Using cached numpy-1.19.5.zip", so the same scenario captures differently depending on
# what the machine happened to have — and a CI runner is always cold while a dev machine
# is usually warm. The download path is the one both agree on. It costs bandwidth on a
# weekly job and buys a fixture that can actually be compared.
if engine == "pip":
args = ["install", "-U"]
args = ["install", "-U", "--no-cache-dir"]
if scenario.dry_run:
# DATA-FLOW §7: this is the exact planning command, JSON report to stdout.
args += ["--dry-run", "--quiet", "--report", "-"]
args += scenario.extra_args + scenario.target
argv = pip_argv(python, args)
else:
args = ["install", "-U"]
args = ["install", "-U", "--no-cache"]
if scenario.dry_run:
args += ["--dry-run"]
args += scenario.extra_args + scenario.target
@@ -251,39 +257,118 @@ def capture(engine: str, scenario: Scenario, uv_exe: Path | None, out_root: Path
out_dir = out_root / engine / scenario.name
out_dir.mkdir(parents=True, exist_ok=True)
(out_dir / "stdout.txt").write_text(result.stdout, encoding="utf-8")
(out_dir / "stderr.txt").write_text(result.stderr, encoding="utf-8")
# The captured streams are redacted for the same reason argv is, and it matters more
# here: pip's "[notice] To update, run: <venv>\Scripts\python.exe -m pip install
# --upgrade pip" embeds the disposable venv's path, which carries mkdtemp's random
# suffix. Left in, every pip stderr.txt differs on every capture — so the drift job can
# never go green — and the capturing user's home directory ships in a public repo.
#
# This is the one place the fixtures are not literal engine bytes, and it is safe
# because no classifier in errors/catalog.rs matches on a filesystem path; they all key
# off message text. Line endings are untouched: `text=True` gave us LF in memory and
# write_text puts CRLF back, exactly as before.
(out_dir / "stdout.txt").write_text(redact(result.stdout, work), encoding="utf-8")
(out_dir / "stderr.txt").write_text(redact(result.stderr, work), encoding="utf-8")
# The sidecar is split by what each half is FOR, because the weekly drift job diffs the
# fixture tree and fails on any change (ci-integration.yml, "Fail if the captured shapes
# moved"). Anything that churns for reasons unrelated to engine output would make that
# job fire on every run and mean nothing — which is exactly what it used to do.
#
# meta.json the contract. A diff here is a real change in engine
# behaviour, and the drift job is right to fail on it.
# capture-provenance.json how these bytes were obtained. Rewritten every capture and
# excluded from the drift gate, but still committed so you can
# always tell which engine produced the current fixtures.
meta = {
"scenario": scenario.name,
"question": scenario.question,
"expects_code": scenario.code_for(engine),
"engine": engine,
"engine_version": engine_version(engine, python, uv_exe),
"python": python_version(python),
"argv": [redact(a) for a in argv],
"extra_env": env,
"exit_code": result.returncode,
"seed": scenario.seed,
"seed_exit_code": None if seed_result is None else seed_result.returncode,
}
provenance = {
"scenario": scenario.name,
"engine_version": engine_version(engine, python, uv_exe),
"python": python_version(python),
"argv": [redact(a, work) for a in argv],
"stdout_bytes": len(result.stdout),
"stderr_bytes": len(result.stderr),
}
(out_dir / "meta.json").write_text(json.dumps(meta, indent=2) + "\n", encoding="utf-8")
return meta
(out_dir / "capture-provenance.json").write_text(
json.dumps(provenance, indent=2) + "\n", encoding="utf-8"
)
return {**meta, **provenance}
finally:
shutil.rmtree(work, ignore_errors=True)
def redact(arg: str) -> str:
"""Replace the temp-dir path so fixtures are stable across machines and runs."""
return arg.replace(str(Path(tempfile.gettempdir())), "<TMP>")
# Any drive-absolute Windows path, in both the raw form engines print to a console and the
# backslash-escaped form they emit inside JSON. Stops at quotes and whitespace so a path
# embedded in a JSON string cannot swallow the closing quote.
_ABS_PATH = re.compile(r'[A-Za-z]:(?:\\\\[^\\/:*?"<>|\r\n]+)+|[A-Za-z]:(?:\\[^\\/:*?"<>|\r\n]+)+')
def redact(text: str, work: Path) -> str:
"""Strip machine- and run-specific paths so a capture is comparable across machines.
Three distinct sources of churn, all of which used to land in committed fixtures:
* `work` is a fresh `mkdtemp`, so its name carries a random suffix. pip's "[notice] To
update, run: <venv>\\Scripts\\python.exe" embeds it, so every pip stderr.txt differed on
every capture.
* uv's build cache uses its own random `.tmpXXXXXX` directories, which appear in build
backend tracebacks.
* Absolute interpreter paths differ by machine — `C:\\Users\\<name>\\AppData\\Local\\Programs`
locally versus `C:\\hostedtoolcache\\...` on a CI runner — so a fixture captured on one
could never match a re-capture on the other.
Together those meant the drift job could not go green, and they shipped a real person's home
directory to a public repo. The final path component is kept because it is the part that
carries diagnostic meaning (`cp1252.py`); the directory prefix is not.
This is the one place fixtures are not literal engine bytes. It is safe because nothing reads
a path out of them: every entry in `CLASSIFIERS` (errors/catalog.rs) keys off message text,
and the plan parsers read pip's JSON report, whose URLs are https rather than filesystem.
"""
text = text.replace(str(work), "<WORK>")
text = text.replace(str(work).replace("\\", "\\\\"), "<WORK>")
text = re.sub(r"\.tmp[A-Za-z0-9_]{6,}", ".tmpXXXXXX", text)
def keep_basename(m: re.Match[str]) -> str:
sep = "\\\\" if "\\\\" in m.group(0) else "\\"
return "<PATH>" + sep + m.group(0).split(sep)[-1]
text = _ABS_PATH.sub(keep_basename, text)
text = text.replace(str(Path(tempfile.gettempdir())), "<TMP>")
# CPython object addresses. pip's retry warnings embed the urllib3 connection object's repr
# ("<...HTTPConnection object at 0x000001A92FBCFBC0>"), and ASLR moves it every process.
text = re.sub(r"0x[0-9A-Fa-f]{6,}", "0xADDR", text)
# pip's download progress bar carries a transfer rate and an ETA, so it is different on
# every run and wildly different between a dev machine and a CI runner.
text = re.sub(r"(?m)^\s*-+\s+[^\r\n]*?eta [0-9:]+[ \t]*$", " <PROGRESS>", text)
# uv times every phase — "Resolved 3 packages in 775ms", "Checked 8 packages in 1ms". The
# counts are signal and stay; the durations are never the same twice. Safe to drop: the uv
# adapter only tests `text.contains("Resolved ")` and reads the +/- lines (engine/parse.rs).
return re.sub(r"\bin \d+(?:\.\d+)?(?:ms|µs|us|s)\b", "in <DURATION>", text)
def engine_version(engine: str, python: Path, uv_exe: Path | None) -> str:
argv = (
pip_argv(python, ["--version"]) if engine == "pip" else [str(uv_exe), "--version"]
)
return run(argv).stdout.strip()
raw = run(argv).stdout.strip()
# `pip --version` reports its own install path: "pip 25.0.1 from C:\Users\<name>\... (python
# 3.12)". That is the capturing user's home directory, and these fixtures are committed to a
# public repo. Drop the clause; the version and the interpreter are the parts that matter.
return re.sub(r"^(pip \S+) from .*? (\(python .*\))$", r"\1 \2", raw)
def python_version(python: Path) -> str: