You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking a glance at pipenv's migration progress from its #11 issue, the whole process is a lot easier right now. Now, all it takes is one command, and the output would be as follows:
$ pipenv install
Creating a virtualenv for this project...
Pipfile: D:\Workspace\spotify-tensorflow\Pipfile
Using c:\users\user\appdata\local\programs\python\python36\python.exe (3.6.6) to create virtualenv...
...
New python executable in C:\Users\User\.virtualenvs\spotify-tensorflow-h7W8yBNY\Scripts\python.exe
Installing setuptools, pip, wheel...done.
Setting project for spotify-tensorflow-h7W8yBNY to D:\Workspace\spotify-tensorflow
Virtualenv location: C:\Users\julio\.virtualenvs\spotify-tensorflow-h7W8yBNY
requirements.txt found, instead of Pipfile! Converting...
Migration also doesn't seem difficult if we're also talking about changes in CI tools.
Seems to be the future: https://github.com/pypa/pipenv
The text was updated successfully, but these errors were encountered: