Thomas Grainger

Probably not worth doing the /json endpoint now as the simple api will already have been downloaded with the hashes in

Imho pip-compile should reuse whatever line separator it finds first in requirements.txt, and fall back to the first line separator it finds in requirements.in

In the usecase stated in the issue "preserve" is a better choice. The pre-commit hook https://github.com/pre-commit/pre-commit-hooks#mixed-line-ending in combination with "preserve" will handle this

> preserve, with no alternatives means pip-compile crashes when used with data from stdin?

`--newline=native` is useful for backwards compatibility `--newline=CRLF` is useful for some users who are Windows only

Also as it happens, I've got a bunch of these directories nested. I'd like to update all the `f'requriements{category}.txt'` files in one shot.

I think this is a duplicate of https://github.com/jazzband/pip-tools/issues/1526 Rather than add interfaces for pip-tools, pip should vendor this project and support both the constraints.txt format and the PEP 665 format...

~I'm a -1 on this because I'm only impacted by pip-compile producing incorrect line separators when it's run misconfigured. Eg the user forgot to run my shim wrapper that emits...

> > I'm a -1 on this because I'm only impacted by pip-compile producing incorrect line separators when it's run misconfigured. Eg the user forgot to run my shim wrapper...

I think this is close to https://github.com/jazzband/pip-tools/issues/215 eg you want to make sure a package is not installed and a replacement is installed instead, or you want to force a...