Tests failures with packaging 26.0

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

@s-t-e-v-e-n-k is already working on this.

Since Feb 2, 2026.

  • #28 by @s-t-e-v-e-n-k — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Run the nine failing tests listed in the report, then inspect tests/pip_requirements_parser_tests/unit/test_req.py, tests/pip_requirements_parser_tests/unit/test_req_file.py, and tests/test_pip_api_parse_requirements.py. Compare their expected requirement strings with packaging 26.0 behavior; done means the listed failures pass without introducing new failures in the suite.

Written by the indexing model from the issue text.

Description

In packaging release 26.0, they've changed the string representation of requirements with URL like:

-foo@ git+http://foo.com@ref#egg=foo
+foo @ git+http://foo.com@ref#egg=foo

See https://github.com/pypa/packaging/issues/935 and https://github.com/pypa/packaging/pull/953

Because of that change, some tests in this project fail:

=========================== short test summary info ============================
FAILED tests/pip_requirements_parser_tests/unit/test_req.py::TestInstallRequirement::test_pep440_url_link_requirement
FAILED tests/pip_requirements_parser_tests/unit/test_req.py::TestInstallRequirement::test_pep440_wheel_link_requirement
FAILED tests/pip_requirements_parser_tests/unit/test_req_file.py::TestProcessFile::test_parse_name_at_url_to_wheel_with_packaging
FAILED tests/pip_requirements_parser_tests/unit/test_req_file.py::TestProcessFile::test_parse_name_at_url__with_packaging
FAILED tests/pip_requirements_parser_tests/unit/test_req_file.py::TestProcessFile::test_parse_name_at_vcs_url_to_wheel_with_packaging
FAILED tests/pip_requirements_parser_tests/unit/test_req_file.py::TestProcessFile::test_can_dumps_name_at_url_to_wheel
FAILED tests/pip_requirements_parser_tests/unit/test_req_file.py::TestProcessFile::test_can_dumps_name_at_url_to_wheel_with_space
FAILED tests/test_pip_api_parse_requirements.py::test_parse_requirements_PEP508[test_5080]
FAILED tests/test_pip_api_parse_requirements.py::test_parse_requirements_PEP508[test_5081]
XFAIL tests/test_packaging_legacy_version.py::TestLegacyVersion::test_legacy_version_is_deprecated - We vendored packaging to reinstate LegacyVersion
===== 9 failed, 8105 passed, 5 skipped, 156 deselected, 1 xfailed in 4.80s =====
Dominant language
Python
Stars
20
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/pip-requirements-parser

All issues in aboutcode-org/pip-requirements-parser

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.