python-poetry / python-poetry/poetry

Allow appending caller-supplied data to the User-Agent (pip's PIP_USER_AGENT_USER_DATA equivalent)

Open
#11,012 1 comment 0 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

Issue Kind

Brand new capability

Description

pip lets us set PIP_USER_AGENT_USER_DATA, which it embeds as user_data in its User-Agent. We use it to add extra information to our requests. It would be important for us to have an equivalent in poetry (measured on 2.3.4, the User-Agent is fixed: poetry/2.3.4 CPython/3.14.4 Darwin/25.6.0).
Is there anything compatible we can use today?

Impact

Requests made by poetry can't carry caller context the way pip's can.

Workarounds

None found, no environment variable or config alters the User-Agent.

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 locating where Poetry constructs its User-Agent and how outbound requests are configured. Compare the expected behavior with pip's PIP_USER_AGENT_USER_DATA, then identify the relevant request tests or add coverage for caller-supplied data. Done means a documented, configurable way to include that data in Poetry's User-Agent.

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
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.