Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

give a try to pipenv? #51

Open
yonromai opened this issue May 1, 2018 · 1 comment
Open

give a try to pipenv? #51

yonromai opened this issue May 1, 2018 · 1 comment
Labels
packaging question Further information is requested

Comments

@yonromai
Copy link
Contributor

yonromai commented May 1, 2018

Seems to be the future: https://github.com/pypa/pipenv

@yonromai yonromai added the question Further information is requested label May 1, 2018
@jcezarms
Copy link
Contributor

jcezarms commented Jul 22, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packaging question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants