pypa/pipx

Normalise entry point and package name to make 'pip run' more permissive

Open

#618 创建于 2021年2月1日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)Python (7,844 star) (363 fork)batch import
enhancementhelp wanted

描述

Continuing the discussion in https://github.com/pipxproject/pipx/pull/615#issuecomment-770336369

I'm assuming the following will not work:

pipx run bUiLd --help

It will download and install build properly from PyPI (I believe) but it won't match the likely pipx.run endpoint name of "build".

console scripts in conjunction with pipx run would face the same issue.

How can we improve this? I guess it’s not too controversial that the names should be case-insensitive. How about dashes, underscores, and dots? Do we use the same normalisation logic as PEP 503?

This change would also make the check here more difficult:

https://github.com/pipxproject/pipx/blob/25a227b2092f672c88622209d99953a758502f18/src/pipx/commands/run.py#L59-L69

Since now we will need to walk through PATH and make sure none of the variants exist on it?

贡献者指南

技术栈
python
领域
clideveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Pythonpipx basicsPEP 503 norms
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Study the normalization logic described in PEP 503 and look at the current implementation in src/pipx/commands/run.py, especially lines 59-69. Consider how to make name matching case insensitive and handle dashes/underscores/dots. Review the linked PR #615 and comments to understand the context. Determine how to walk PATH to check for conflicting executables.