Add HTTPS_PROXY support for hatch publish
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 462
- Avg merge
- 19h 36m
- Merged PRs (30d)
- 10
Description
Hi,
I'm facing timeout issue on my university gitlab-ci which seems to be related to the proxy configuration not being detected by hatch:
$ echo $HTTPS_PROXY
https://proxy-server.tld:xxxx/
$ hatch publish
...
Error uploading to repository: https://test.pypi.org/legacy/ - [Errno 99] Address not available
When I use the same configuration outside the university (without the proxy) everything works as expected.
This issue does not appear with twine which have HTTPS_PROXY build-in support.
Would it be possible to do the same on hatch publish?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the hatch publish command and trace how it uploads to the configured repository. Compare its proxy handling with the HTTPS_PROXY behavior documented for twine. Done means hatch publish recognizes HTTPS_PROXY and can upload through the proxy without the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100