Normalise entry point and package name to make 'pip run' more permissive · pypa/pipx#618

(3 comments) (0 reactions) (0 assignees)Python (7,844 stars) (363 forks)batch import

enhancementhelp wanted

Description

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?

Contributor guide

Tech stack: python
Domain: clideveloper experience
Issue type: feature
Difficulty: 3
Estimated time: 1-2 days
Activity status: stale
Clarity: clear
Prerequisites: Pythonpipx basicsPEP 503 norms
Newbie friendliness: 60
Research direction: 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.