Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using the --newline=[LF|CRLF|native|preserve] option in pip-compile #6186

Closed
1 task done
jeffwidman opened this issue Nov 21, 2022 · 1 comment
Closed
1 task done

Comments

@jeffwidman
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Code improvement description

New pip-compile feature: jazzband/pip-tools#1652

@jeffwidman jeffwidman changed the title Investigate using the --newline=[LF|CRLF|native|preserve] option in pip-compile Investigate using the --newline=[LF|CRLF|native|preserve] option in pip-compile Nov 21, 2022
@jeffwidman
Copy link
Member Author

From that URL:

The default is preserve, which tries to be consistent with an existing output file, or input file, or falls back to LF, in that order.

That's the behavior we'd want, so no need to be explicit about it unless it starts causing problems, in which case I expect users will report problems with unexpected diffs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant