Python developers struggle to keep project environments reproducible
Python developers spend time setting up, updating, and reproducing environments because dependency files, interpreters, and project workflows can be difficult to keep aligned. They resort to manual scripts, multiple requirements files, or even Docker for small scripts, while incompatible dependencies and machine-specific package indexes can still block a working setup. A solo-built tool could make one slice of this workflow easier, but replacing Python’s packaging ecosystem is not a realistic MVP.
For python developers and maintainers. Mentioned from Jun 2018 to Jun 2026 on Bluesky, GitHub, Hacker News and Stack Exchange.
36 different people described this problem in 28 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.8/10
- Frequency
- 10.0/10
- Willingness to pay
- 1.7/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
So you end up with something like two different requirements.txt where you use a frozen one for development and then switch to an unfrozen one for release or when you need to add or change dependencies, and regenerate the frozen one every so often.
lmm on Hacker NewsFeb 2025requirements.txt and the madness around it has been a hell for over a decade. It's been so pointlessly hard to replicate what the authors of Python projects want the state of your software to be in
echelon on Hacker NewsOct 2025
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 34 more quotes from people who have this problem
- Current workarounds, existing solutions and risks