Pipenv does not find pipfile in upper directory

Pipenv virtualenv created for a project, at the top of my project are a pipfile and pipfile.lock files. When executing pipenv commands in sub directory (3 levels below), a new virtual env gets created.

I thought it would not be the case and pipenv would use the one at the top

Describe your environment

1. OS Type: Windows 10
2. Python version: $ python -V Python 3.6.1 :: Anaconda 4.4.0 (64-bit)
3. Pipenv version: $ pipenv --version pipenv, version 11.1.6

Expected result

I expect no new environment to be created

Actual result

Passing the option --verbose to pipenv does not work

Steps to replicate

• created a virtualenv with pipenv, and a pipfile
• create some subdirs
• in the subdir, execute pipenv --shell It creates a new env instead of using the one at the top. Please note that sometimes it works, sometimes not.

Top Pipfile [[source]]

url = “https://pypi.python.org/simple” verify_ssl = true name = “pypi”

[packages]

“pyqt5” = “" pyedflib = "” psutil = “*”

[dev-packages]

[requires]

python_version = “3.6”

[kennethreitz]

We only check 2 or 3 levels above. This is configurable by setting the PIPENV_MAX_DEPTH environment variable.

[keysmusician]

you’re the first person who’s raised any concern over the default so far, so i think we’ve picked a good sane default 😃

Perhaps my experience is another outlier, but I thought creating a subshell was default behavior for about 6 months now because using the project root environment almost never worked for me (though I do seem to recall from documentation that it was supposed to). I find the default max depth surprising and incredibly annoying, but didn’t realize I could do anything about it.

For the record, the reason my projects were so nested is because I created an environment for a series of school projects in which the file structure was dictated by the school. Our projects’ “working directories” typically start at the third level down from the project root.