python-poetry / python-poetry/poetry

Allow a folder with a list of wheels to be a repository, mimic pip --find-links

Open
#5,983 26 comments 36 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature status/triage
Dominant language
Python
Stars
34.3k
Forks
2.5k
Avg merge
2d 19h
Merged PRs (30d)
30

Description

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Feature Request

The git --find-links features allows one to add a folder with a set of wheels as a repository. One can also configure git to include a folder with wheels as a repo, like so:

pip config set global.find-links N:\shared\repo

Could we have similar functionality for poetry? Have a feature that when the [[tool.poetry.source]] url is a local path like "/home/repo" or "C:\repo", or starts with "file://", then look for archives in that directory listing?

The git documentation for --find-links give a clear explanation of it's behavior:

If (the link to the repo is) a URL or path to an html file, then parse for links to archives such as sdist (.tar.gz) or wheel (.whl) files. If a local path or file:// URL that’s a directory, then look for archives in the directory listing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how [[tool.poetry.source]] URLs are handled, especially local paths and file:// URLs. Compare the behavior with pip's --find-links documentation and verify that directory listings expose archive files such as .whl and .tar.gz as package sources.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.