PipfileNotFound raised for no Pipfile while installing

[nealyip]

from the previous version, when there is no Pipfile, one will be automatically created when executing pipenv install.
However, after 2018.11.14, an error is thrown
Pipfile not found! Aborting! Please ensure that the file exists and is located in your project root directory.

Steps to replicate

1, pipenv install

[duplicate-issues]

Hey @nealyip,

We did a quick check and this issue looks very darn similar to

• #3259 - Update pythonfinder for resilient parsing
• #3255 - Installation failed due to missing hashes when using --skip-lock
• #3252 - Updated graph command docstrings, fixes #3071

This could be a coincidence, but if any of these issues solves your problem then I did a good job 😄

If not, the maintainers will get to this issue shortly.

Cheers,
Your Friendly Neighborhood ProBot

[frostming]

pipenv install without package names is disallowed when there is no Pipfile present.

Any of the following is OK to initialize a pipenv project:

$ pipenv --python python
$ pipenv --two/--three
$ touch Pipfile && pipenv install

[ghost]

@nealyip @frostming I have this same issue. Wanted to file an issue today at 8 am but could not. This time I searched again for duplicates. And almost missed this. Had to read it to realise I had the same issue.

Use Case:
Use pipenv install to create a fresh env as its faster than pipenv install x. Then use pipenv shell to enter the env and setup the env.

Steps to repro+ error:
pipenv-WYDT.txt

Expected:
pipenv installs a new env with python, pip, setuptools, and wheel. And then you can install packages without pipenv slowing you down.

Details:-
OS Specs: Edition->Windows 10 Pro,
Version->1803,
Build->17134.407
Device Specs: System type->64-bit OS, x64-based processor,
Installed RAM: 16.0GB(15.9GB usable),
Processor: Intel Core i5-7400 CPU

Python: 3.7.1
Pipenv: 2018.11.14
WinPython: 3.7.1.0-64bit

Moreover-
WinPython is not registered as system Python. Python is not on user or system Path.
No other Python version is installed on the system.

[ghost]

@nealyip
Reply to:- https://github.com/pypa/pipenv/issues/3260#issuecomment-440193629

pipenv install without package names is disallowed when there is no Pipfile present.

Since when? I really don't know anything about this and I tried to. Can you please give a link?

Note( for Windows 10 1803 users): The top two methods have been tested succesfully on Windows 10 @1803!

1. pipenv --python python

Good to know. Thanks.

2. pipenv --two/--three

Good to know. Thanks. Also, this can be added to the error that suddenly appeared.

3. touch Pipfile && pipenv install

I am on windows. This causes error in Powershell and cmd. touch Pipfile followed by pipenv install also doesn't work.
So, I used Notepad++ to create Pipfile. After I copy a Pipfile from the other env, edit it and paste it in the current directory, it works!

PS:- I hope this and the above comment have been helpful.

[ghost]

@frostming Is there any chance this will get fixed? If yes, thanks a lot. I would like to help.

If no, thanks to all contributors for pipenv, it was like salt( is to food). I'll just have to stop using pipenv and go back to using virtualenv. I can't change my workflow. I would still like to help, but I am not sure if its okay to contribute to projects I don't use often. Am I mistaken?

[frostming]

I just reviewed the original issue linked above and find it was a bad fix to change the behavior. You are right, pipenv install should work to create the Pipfile correctly.

I will submit a fix soon. Thank you.

[techalchemy]

@snow8gaia I'm also interested in this comment specifically:

WinPython is not registered as system Python. Python is not on user or system Path.

can you run pipenv --support and provide the output?

[techalchemy]

Also in retrospect, there was no api change introduced and no flaw in the exception handling, there is just a bug in pipfile generation which results in the downstream exception which tells you there is no pipfile.

Fix will be up in a sec

[ghost]

WinPython is not registered as system Python. Python is not on user or system Path.

Correction: WinPython temporarily adds the required files to Path. I don't see(by using path in cmd) WinPython's additions to the beginning of the Path in another cmd prompt that is open at the same time.

When I compare the output of path in the two cmd prompts:- WinPython prompt's path prepends some extra stuff. While a regular prompt does not have the prepends.

[ghost]

I forgot, thanks a lot for the quick response.

[ghost]

This issue is resolved in:-
pipenv version: 2018.11.26
released on- Nov 26, 2018

[ghost]

Thanks a lot to the pipenv team, especially @techalchemy and @frostming.

[techalchemy]

Thanks for the message, it helps to know it is appreciated!

[vhosakot]

Saw the same error with python 3.7:

[pipenv.exceptions.PipfileNotFound]: raise exceptions.PipfileNotFound

and pipenv --python python3.7 resolved it for me.