pypa/pipx

Support module only packages

Closed

#177 opened on Jul 9, 2019

View on GitHub
 (26 comments) (3 reactions) (0 assignees)Python (363 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (7,844 stars)
PR merge metrics
 (Avg merge 4d 12h) (22 merged PRs in 30d)

Description

Some packages don't offer console script for various reasons. We should be able to install these, perhaps by generating simpler wrappers that forward the invocation to the module. This could also version qualify installed scripts to ensure the user can explicitly differentiate between multiple version:

Think of:

  • tox3.4
  • tox3.6
  • tox3.7
  • tox (links to first target - 37?)

Reference: https://github.com/pypa/pep517/issues/54

Contributor guide

Research direction
Examine how pipx currently generates console scripts for packages that provide entry points. Review the referenced pep517 issue to understand module only packaging. Design a wrapper that invokes Python modules directly, and consider version qualification. Then implement a prototype.
Tech stack
python
Domain
clitoolingdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Pythonpipx
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50