I tried installing it in a virtualenv and then I saw it installed virtualenv inside the virtualenv, which is like virtualenv inception. I'm going to try it again tomorrow. I think the change of workflow will take some time to adapt for me. I weirdly like uninstalling everything in my virtualenv and then installing from scratch from my requirements.txt, and the reason behind that is I work on some projects that have a huge list of dependencies(far too many for my liking) and often a package gets out of date or can't install anymore or a certain bug only creeps in with a specific version of a package. Are there any tools out there for converting your requirements.txt to the format that pipenv uses?
I haven't used it in a virtualenv environment, but I believe it will read in a .env file. I would recommend removing the virtual env all together, and reinstalling the packages using pipenv install ... and it will handle it all.
Just make sure you are in the project folder.
pipenv makes it really easy to uninstall/install modules and will handle adding only modules you need.
Cool thanks you are right. I see in the documentation here: https://docs.pipenv.org/basics/#importing-from-requirements-txt it says: "If you only have a requirements.txt file available when running pipenv install, pipenv will automatically import the contents of this file and create a Pipfile for you." and it says: "You can also specify $ pipenv install -r path/to/requirements.txt to import a requirements file." and that pretty means you can also install from a file that isn't named requirements.txt also for example: pipenv install -r dev-requirements.txt Thanks for sharing all the info. Would you mind if I add you on discord?
Let me know what you think!
I tried installing it in a virtualenv and then I saw it installed virtualenv inside the virtualenv, which is like virtualenv inception. I'm going to try it again tomorrow. I think the change of workflow will take some time to adapt for me. I weirdly like uninstalling everything in my virtualenv and then installing from scratch from my requirements.txt, and the reason behind that is I work on some projects that have a huge list of dependencies(far too many for my liking) and often a package gets out of date or can't install anymore or a certain bug only creeps in with a specific version of a package. Are there any tools out there for converting your requirements.txt to the format that pipenv uses?
I haven't used it in a virtualenv environment, but I believe it will read in a .env file. I would recommend removing the virtual env all together, and reinstalling the packages using
pipenv install ...and it will handle it all.Just make sure you are in the project folder.
pipenvmakes it really easy to uninstall/install modules and will handle adding only modules you need.Cool thanks you are right. I see in the documentation here: https://docs.pipenv.org/basics/#importing-from-requirements-txt it says: "If you only have a requirements.txt file available when running pipenv install, pipenv will automatically import the contents of this file and create a Pipfile for you." and it says: "You can also specify $ pipenv install -r path/to/requirements.txt to import a requirements file." and that pretty means you can also install from a file that isn't named requirements.txt also for example:
pipenv install -r dev-requirements.txtThanks for sharing all the info. Would you mind if I add you on discord?I ran into this isssue when I ran:
$pipenv install -r requirements.txt: "Unkown locale: UTF-8" and I solved it with this:https://stackoverflow.com/questions/38916461/valueerror-unknown-locale-utf-8-when-importing-pandas-in-python-2-7
I added this to ~/.bash_profile:
export=LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8and did:
$ source ~/.bash_profileand then this worked:
$ pipenv install -r requirements.txt