Tests failures with packaging 26.0
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/pip-requirements-parser
-
Quadratic comment split on a requirements file line (pip_requirements_parser.py:1058)May be free again @Anurag-S1ngh claimed this 25 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aboutcode-org/pip-requirements-parser#30 · 1 comment ·
-
Support PEP 561 Distributing and Packaging Type Information (py.typed marker)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 60/100
-
Doesn't support local paths to wheelsMay be free again @Anurag-S1ngh claimed this 18 days ago, and no pull request is open. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
aboutcode-org/pip-requirements-parser#26 · 3 comments ·
-
[BUG] VCS URLs are detected as path on linux systemsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in aboutcode-org/pip-requirements-parser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day