Be sure to check the existing issues, both open and closed.
I ran pipenv install into existing django 1.11 project, but it does not create two new files, Pipfile and Pipfile.lock, in project directory. However a new virtual environment is created.
$ python3 -V 3.5.2$ pipenv --version version 9.0.1This should create two new files, Pipfile and Pipfile.lock, in project directory
pipenv install
Creating a virtualenv for this projectβ¦
Using /usr/bin/python3.5m to create virtualenvβ¦
β Running virtualenv with interpreter /usr/bin/python3.5m
Using base prefix '/usr'
New python executable in /home/muhammadtaqi/.local/share/virtualenvs/projects-3nzJ4ToY/bin/python3.5m
Also creating executable in /home/muhammadtaqi/.local/share/virtualenvs/projects-3nzJ4ToY/bin/python
Installing setuptools, pip, wheel...done.
Virtualenv location: /home/muhammadtaqi/.local/share/virtualenvs/projects-3nzJ4ToY Installing dependencies from Pipfile.lock (b5430f)β¦
π ββββββββββββββββββββββββββββββββ 6/6 β 00:00:00
To activate this project's virtualenv, run the following:
$ pipenv shell
It creates Pipfiiles in one directory upto the project directory. in /home/muhammadtaqi/project directory
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
I am facing the same issue. Running pipenv install <some-package>, neither Pipfile nor Pipfile.lock are getting generated. Using latest pipenv v9.0.3.
Was this issue fixed?
I'm not sure, but in my case it generated the files one directory up from the project, I manually deleted those files and then again run pipenv install , then it generates in the directory i was running the command.
Thanks. I think I figured out what the issue is. Opened https://github.com/pypa/pipenv/issues/1317
I'm not sure, but in my case it generated the files one directory up from the project, I manually deleted those files and then again run
pipenv install, then it generates in the directory i was running the command.
I've had the same issue. For some reason it created those 2 files in my main directory. After deleting them and running pipenv install, it worked fine.
Thank you for the solution.
In my case both Pipfile and Pipfile.lock were created in home directory inside virtualenv, so I moved them into project directory
In my case, it worked when I changed my pipenv version to an earlier version (was using the latest version 2020.8.13):
pip install pipenv==2018.11.26
After I ran the above, the Pipfile and Pipfile.lock were created in the project directory.
Most helpful comment
I'm not sure, but in my case it generated the files one directory up from the project, I manually deleted those files and then again run
pipenv install, then it generates in the directory i was running the command.