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

Allow empty requirements.txt #343

Closed
craigkerstiens opened this issue Aug 25, 2011 · 4 comments
Closed

Allow empty requirements.txt #343

craigkerstiens opened this issue Aug 25, 2011 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality

Comments

@craigkerstiens
Copy link
Contributor

Viewing requirements.txt as a canonical form for specifying dependencies it should allow for an empty requirements.txt to be installed in case a package needs no other dependencies.

Currently it throws the exception:
You must give at least one requirement to install (see "pip help install")

This does not need to be the case for any pip install, but should be allowed when a requirements file is specified.

@jwineinger
Copy link

+1

mihneadb added a commit to mihneadb/pip that referenced this issue Jun 16, 2012
@mihneadb
Copy link

#580

@xavfernandez
Copy link
Member

Since pip 1.1, it simply prints a warning but does not error anymore:

$ touch empty.txt
$ pip install -r empty.txt
You must give at least one requirement to install (see "pip help install")
$ echo $?
0

@xavfernandez xavfernandez added the type: enhancement Improvements to functionality label Oct 8, 2015
@dstufft
Copy link
Member

dstufft commented Mar 18, 2017

This seems to be the case now.

@dstufft dstufft closed this as completed Mar 18, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality
Projects
None yet
Development

No branches or pull requests

5 participants