On Mon, 20 Aug 2018 at 13:21, Wes Turner
Something as simple as reading a requirements.txt file into JSON must either reimplement or wrongly import from pip._internal.
Or copy pip's code and maintain it locally...
Anyways, Tool authors reimplementing in particular the requirements.txt functionality shouldn't be necessary.
Agreed. Maybe someone should write a package to handle requirements.txt reading API. They could copy the code from pip with our blessing, and we'd happily vendor them and use their code. As you can see, it's very easy to suggest that someone *else* should do something. The problem is finding someone who has both the interest in solving the problem, and the time to do so. The "why doesn't pip have a stable API" question is very much about the fact that we don't have the *resources* to support one, not about any dislike of programmatic APIs... Paul