[BUG] VCS URLs are detected as path on linux systems
Nobody has claimed this yet.
- #33 by @Anurag-S1ngh — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
Research direction
Start by locating the _looks_like_path entry point and reproduce the Linux case with the VCS URL shown in the issue. Trace how that URL is classified, then verify that it is no longer treated as a filesystem path while ordinary paths remain recognized.
Written by the indexing model from the issue text.
Description
issue
'git+https://github.com/path/to/package-one@41b95ec#egg=package-one'
is detected as a path, but actually it is just a VCS url
expected:
'git+https://github.com/path/to/package-one@41b95ec#egg=package-one'
is NOT detected as a path
reason:
def _looks_like_path(name: str) -> bool:
"""Checks whether the string ``name`` "looks like" a path on the filesystem.
This does not check whether the target actually exists, only judge from the
appearance.
Returns true if any of the following conditions is true:
* a path separator is found (either os.path.sep or os.path.altsep);
* a dot is found (which represents the current directory).
"""
if not name:
return False
if os.path.sep in name:
return True
# exists here, on linux/unix, as there is a '/' in the name
# ...
- 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
-
Tests failures with packaging 26.0Possibly taken @s-t-e-v-e-n-k claimed this 290 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/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 ·
-
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