aboutcode-org / aboutcode-org/pip-requirements-parser

Potential improvement for editable installs

未关闭
#6 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
20
派生
13
PR 合并指标
30 天内没有已合并 PR

描述

I noticed another small difference between `pip-api` and `pip-requirements-parser` which I'd like to bring up.
At the moment, `pip-requirements-parser` relies on an egg fragment being at the end of an editable install in order to infer its name/specifier. Otherwise, the `EditableRequirement`'s `req` member is set to `None`.

`pip-api` has some special logic that checks whether the editable installation points to a directory. If so, it checks that directory for a `setup.py` and attempts to parse the package name and version out of the file. You can find the relevant logic [here](https://github.com/di/pip-api/blob/master/pip_api/_parse_requirements.py#L248).

How do you feel about having this logic in `pip-requirements-parser`? I appreciate that this logic perhaps goes a bit beyond "parsing" but it'd be useful since not all editable requirements have an egg fragment.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。