pipenv does not create Pipfile and Pipfile.lock if they exist in parent directories

Describe your environment

1. OS Type - OSX - Darwin Kernel Version 16.7.0
2. Python version: $ python -V - Python 2.7.10
3. Pipenv version: $ pipenv --version - pipenv, version 9.0.3

Steps to replicate:

cd ~/
pipenv install <any-package>
mkdir hello
cd hello
pipenv install <any-package>

Expected result

Pipfile and Pipfile.lock should be created in the current directory (~/hello in the above example)

Actual result

If Pipfile exist in home (parent) directory, no Pipfile or Pipfile.lock is created in current directory. pipenv keeps adding packages to the parent Pipfile (in home directory in above example). And pipenv --where returns home directory path.

[halloleo]

Another, newer way to do it is to set the env variable PIPENV_NO_INHERIT. Then Pipenv won’t look in the parent directory.

[uranusjr]

This is deliberate, and normally is what people want. Say you’re developing a package with a tools directory. It would be strange if you can’t run scripts inside the tools subdirectory, only in the root. The Pipfile should work for all directories inside that project.

You can create a Pipfile manually inside hello to get the behaviour you want.