pypa/hatch

Making TIMEOUT used by pip install configurable

Open

#2158 opened on Jan 15, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Python (4,451 stars) (240 forks)batch import
good first issue

Description

Description

In https://github.com/pypa/hatch/pull/1531 a DEFAULT_TIMEOUT has been implemented. I think it would be better to be configurable.

Use case/motivation

I use hatch on a server protected by a VPN that slow down the connection and the current default timeout is too small. To make hatch worked I patched the DEFAULT_TIMEOUT value and increased. But that's a dirty temporary solutions.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
python
Domain
developer experiencebackend
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic PythonFamiliarity with Hatch configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine PR #1531 for the current DEFAULT TIMEOUT implementation. Understand how Hatch handles configuration (e.g., env vars, config file). Propose a way to let users set the timeout, such as an environment variable HATCH PIP TIMEOUT or a pyproject.toml option. Ensure backward compatibility. Update relevant documentation and add a test for the new configuration.