-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Question: pipenv and conda #699
Comments
use pipenv outside of conda, but you can use it to create virtualenvs with an anaconda python. For example:
|
Can confirm that this works. |
@kennethreitz, do I need to install pipenv using another python, then point it to the conda installed one? |
yes |
This issue is related to #288 |
I have been seeing some weird issues with pipenv and conda. I am posting this issue here, but it may be an issue for elsewhere, but your help in working this out is greatly appreciated. What i am seeing is some dependency issues where it seems that although i have specified my python3 path one of my packages wants to use my anaconda path, even through its been installed via pipenv install Does anyone know how to fix this? Answers much appreciated The detailsI am wanting to build a flask app using zappa to put it on AWS. So i am using pipenv to create a new python3 env that i specify then i install the rele
check the env
install zappa and flask
check zappa
You can see that for some reason it wants to use the python that is associated with anaconda (i think). The pipenv graph looks ok (??)
|
@kadlugan I'm facing a similar AWS install with pipenv as a conda user I'm curious how this worked for you. |
Thanks for your work on pipenv!
I have some question as I'm struggling to understand if I can use pipenv in my workflow. I am a conda user and I am pretty familiar with conda environments but I have rarely used virtualenvs.
Can pipenv be used together within a conda/anaconda installation?
I tried to install pipenv but I get an error about virtualenvs:
EDIT: typos
The text was updated successfully, but these errors were encountered: