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

Support for stdin / stdout #104

Closed
blueyed opened this Issue Jul 3, 2014 · 2 comments

Comments

Projects
None yet
3 participants
@blueyed
Contributor

blueyed commented Jul 3, 2014

It would be useful if pip-compile would accept input from stdin and allowed to write to stdout.

pip-compile might detect if stdin/stdout is used, but an explicit option should work, too:

git show :requirements.in | pip-compile > requirements.txt
git show :requirements.in | pip-compile - -o > requirements.txt

This would allow to easily compile only what's in Git's index, for example.

@nvie

This comment has been minimized.

Show comment
Hide comment
@nvie

nvie Jul 23, 2014

Member

+1 to this idea.

Member

nvie commented Jul 23, 2014

+1 to this idea.

@nvie nvie added the future label Sep 1, 2014

@bardo

This comment has been minimized.

Show comment
Hide comment
@bardo

bardo Sep 28, 2014

Seconded. It would also enable modular dependencies in a simple way:

$ cat requirements-{base,dev}.in | pip-compile - -o >requirements-dev.txt
$ cat requirements-{base,production}.in | pip-compile - -o >requirements-production.txt

Great way to share a common versioned package list between different environments. The proper way to allow this would require quite a bit of reworking of .in files, allowing for some kind of "include" directive, but I think it's overkill at the moment.

bardo commented Sep 28, 2014

Seconded. It would also enable modular dependencies in a simple way:

$ cat requirements-{base,dev}.in | pip-compile - -o >requirements-dev.txt
$ cat requirements-{base,production}.in | pip-compile - -o >requirements-production.txt

Great way to share a common versioned package list between different environments. The proper way to allow this would require quite a bit of reworking of .in files, allowing for some kind of "include" directive, but I think it's overkill at the moment.

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