mitmproxy / mitmproxy/mitmproxy
Distribute via source tarball in additional to wheel on PyPI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 45.1k
- Forks
- 4.7k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 16
Description
Problem Description
I'd like to re-package mitmproxy as a package on conda-forge from an official source distribution.
Proposal
On conda-forge, we prefer to use official source distributions: for pure python projects, usually .tar.gz from PyPI. We'd love to use (noarch) whls someday, but it will take a while for all the PEPs to die down.
Alternatives
We can build directly from a VCS-generated tarball, but those have more of a habit of changing (e.g. the shasum changing) than an artifact generated by the project's owners/automation.
Additional context
Thanks for mitmproxy!
Contributor guide
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 by inspecting the PyPI publishing configuration and release automation mentioned in the proposal, including how the wheel artifacts are selected. Done means an official .tar.gz source distribution is published on PyPI alongside the wheel and can be consumed by conda-forge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100