How can I manage the modules for python2 when python3 installed as well. In OSX












1















I'm using OSX and I installed python3 with anaconda installed. In my OSX, there exists two versions of python, i.e. python2 and python3.



I managed the modules in anaconda which only affect modules in python3. But how can I manage(install, delete, update) the modules for python2?



I've checked some posts about 'python2 is at /usr/bin/python' . So it's ok to use python2 by '/usr/bin/python' without configuring alias. But, how can I manage(install, delete, update) the modules for python2 when python3 installed as well. In OSX.



Below is some cmds result. Thank you!!



$ pip --version
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ pip3 -V
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ echo $PATH
~/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin









share|improve this question

























  • Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

    – Paulo Scardine
    Nov 20 '18 at 2:47













  • default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

    – e.maguire
    Nov 20 '18 at 2:51
















1















I'm using OSX and I installed python3 with anaconda installed. In my OSX, there exists two versions of python, i.e. python2 and python3.



I managed the modules in anaconda which only affect modules in python3. But how can I manage(install, delete, update) the modules for python2?



I've checked some posts about 'python2 is at /usr/bin/python' . So it's ok to use python2 by '/usr/bin/python' without configuring alias. But, how can I manage(install, delete, update) the modules for python2 when python3 installed as well. In OSX.



Below is some cmds result. Thank you!!



$ pip --version
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ pip3 -V
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ echo $PATH
~/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin









share|improve this question

























  • Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

    – Paulo Scardine
    Nov 20 '18 at 2:47













  • default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

    – e.maguire
    Nov 20 '18 at 2:51














1












1








1








I'm using OSX and I installed python3 with anaconda installed. In my OSX, there exists two versions of python, i.e. python2 and python3.



I managed the modules in anaconda which only affect modules in python3. But how can I manage(install, delete, update) the modules for python2?



I've checked some posts about 'python2 is at /usr/bin/python' . So it's ok to use python2 by '/usr/bin/python' without configuring alias. But, how can I manage(install, delete, update) the modules for python2 when python3 installed as well. In OSX.



Below is some cmds result. Thank you!!



$ pip --version
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ pip3 -V
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ echo $PATH
~/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin









share|improve this question
















I'm using OSX and I installed python3 with anaconda installed. In my OSX, there exists two versions of python, i.e. python2 and python3.



I managed the modules in anaconda which only affect modules in python3. But how can I manage(install, delete, update) the modules for python2?



I've checked some posts about 'python2 is at /usr/bin/python' . So it's ok to use python2 by '/usr/bin/python' without configuring alias. But, how can I manage(install, delete, update) the modules for python2 when python3 installed as well. In OSX.



Below is some cmds result. Thank you!!



$ pip --version
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ pip3 -V
pip 18.0 from ~/anaconda/lib/python3.5/site-packages/pip (python 3.5)

$ echo $PATH
~/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin






python development-environment






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 4:15







sonictl

















asked Nov 20 '18 at 2:41









sonictlsonictl

136




136













  • Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

    – Paulo Scardine
    Nov 20 '18 at 2:47













  • default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

    – e.maguire
    Nov 20 '18 at 2:51



















  • Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

    – Paulo Scardine
    Nov 20 '18 at 2:47













  • default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

    – e.maguire
    Nov 20 '18 at 2:51

















Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

– Paulo Scardine
Nov 20 '18 at 2:47







Although there are pip3 I never heard of pip2 - for me it is either pip or pip3. For OSX I recommend brew install pyenv and then pyenv to see the usage.

– Paulo Scardine
Nov 20 '18 at 2:47















default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

– e.maguire
Nov 20 '18 at 2:51





default pip on macos is the shipped 2.7. All python 2.7 versions ship as python

– e.maguire
Nov 20 '18 at 2:51












3 Answers
3






active

oldest

votes


















0














Anaconda comes with a package and environment manager called conda. This is what you need to do:



Create a separate Python 2.7 environment, let's call it old and busted.



conda create --name old_and_busted python=2.7



Now switch to this environment:



conda activate old_and_busted



Verify it worked if you want:



python --version



Install something cool:



conda install flask



Bonus, use pip to install something cool in the same environment:



pip install flask



What environment are we in again?



conda env list



Let's check for that package:



conda list



Now this part is very important, make sure to do it often - go back to your Python 3 environment:



conda activate base



pipenv manages environments in a similar way. Anaconda specializes in packaging for scientific computing handling packaging non-python extensions (e. g. C, C++) dependencies well.



** Note on conda vs source for environment activation **



If conda activate does not work use source activate. This was changed in Anaconda 4.4.0 Release Notes.



If you have this in your .bash_profile (or .profile or other magical dotfile) you use source activate:




export PATH="$HOME/anaconda3/bin:$PATH"



If you have this updated code in your shell startup then you can use conda activate:




. $HOME/anaconda3/etc/profile.d/conda.sh
conda activate






share|improve this answer


























  • it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

    – sonictl
    Nov 20 '18 at 5:10











  • I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

    – dwagnerkc
    Nov 20 '18 at 5:13













  • This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

    – sonictl
    Nov 20 '18 at 5:19













  • Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

    – dwagnerkc
    Nov 20 '18 at 5:25











  • Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

    – dwagnerkc
    Nov 20 '18 at 5:28



















0














You can use pyenv



Firstly you should install pyenv.



use



pyenv versions


check all version on your computer.



use



pyenv global 3.4.0


setting your current gobal python version.



use



pyenv install 3.4.0



install a specific version of Python.



You can find more usage in the documentation.






share|improve this answer
























  • My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

    – sonictl
    Nov 20 '18 at 4:12













  • @sonictl So you should try pyenv install 2.7.0

    – Mark White
    Nov 20 '18 at 4:57



















0














Python ships in two primary ways, python for Python 2, and python3 for Python 3.x. The pips for both are pip and pip3, respectively.



Echoing what @Mark White said in his answer, you should use pyenv to ensure env parity.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385448%2fhow-can-i-manage-the-modules-for-python2-when-python3-installed-as-well-in-osx%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Anaconda comes with a package and environment manager called conda. This is what you need to do:



    Create a separate Python 2.7 environment, let's call it old and busted.



    conda create --name old_and_busted python=2.7



    Now switch to this environment:



    conda activate old_and_busted



    Verify it worked if you want:



    python --version



    Install something cool:



    conda install flask



    Bonus, use pip to install something cool in the same environment:



    pip install flask



    What environment are we in again?



    conda env list



    Let's check for that package:



    conda list



    Now this part is very important, make sure to do it often - go back to your Python 3 environment:



    conda activate base



    pipenv manages environments in a similar way. Anaconda specializes in packaging for scientific computing handling packaging non-python extensions (e. g. C, C++) dependencies well.



    ** Note on conda vs source for environment activation **



    If conda activate does not work use source activate. This was changed in Anaconda 4.4.0 Release Notes.



    If you have this in your .bash_profile (or .profile or other magical dotfile) you use source activate:




    export PATH="$HOME/anaconda3/bin:$PATH"



    If you have this updated code in your shell startup then you can use conda activate:




    . $HOME/anaconda3/etc/profile.d/conda.sh
    conda activate






    share|improve this answer


























    • it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

      – sonictl
      Nov 20 '18 at 5:10











    • I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

      – dwagnerkc
      Nov 20 '18 at 5:13













    • This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

      – sonictl
      Nov 20 '18 at 5:19













    • Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

      – dwagnerkc
      Nov 20 '18 at 5:25











    • Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

      – dwagnerkc
      Nov 20 '18 at 5:28
















    0














    Anaconda comes with a package and environment manager called conda. This is what you need to do:



    Create a separate Python 2.7 environment, let's call it old and busted.



    conda create --name old_and_busted python=2.7



    Now switch to this environment:



    conda activate old_and_busted



    Verify it worked if you want:



    python --version



    Install something cool:



    conda install flask



    Bonus, use pip to install something cool in the same environment:



    pip install flask



    What environment are we in again?



    conda env list



    Let's check for that package:



    conda list



    Now this part is very important, make sure to do it often - go back to your Python 3 environment:



    conda activate base



    pipenv manages environments in a similar way. Anaconda specializes in packaging for scientific computing handling packaging non-python extensions (e. g. C, C++) dependencies well.



    ** Note on conda vs source for environment activation **



    If conda activate does not work use source activate. This was changed in Anaconda 4.4.0 Release Notes.



    If you have this in your .bash_profile (or .profile or other magical dotfile) you use source activate:




    export PATH="$HOME/anaconda3/bin:$PATH"



    If you have this updated code in your shell startup then you can use conda activate:




    . $HOME/anaconda3/etc/profile.d/conda.sh
    conda activate






    share|improve this answer


























    • it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

      – sonictl
      Nov 20 '18 at 5:10











    • I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

      – dwagnerkc
      Nov 20 '18 at 5:13













    • This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

      – sonictl
      Nov 20 '18 at 5:19













    • Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

      – dwagnerkc
      Nov 20 '18 at 5:25











    • Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

      – dwagnerkc
      Nov 20 '18 at 5:28














    0












    0








    0







    Anaconda comes with a package and environment manager called conda. This is what you need to do:



    Create a separate Python 2.7 environment, let's call it old and busted.



    conda create --name old_and_busted python=2.7



    Now switch to this environment:



    conda activate old_and_busted



    Verify it worked if you want:



    python --version



    Install something cool:



    conda install flask



    Bonus, use pip to install something cool in the same environment:



    pip install flask



    What environment are we in again?



    conda env list



    Let's check for that package:



    conda list



    Now this part is very important, make sure to do it often - go back to your Python 3 environment:



    conda activate base



    pipenv manages environments in a similar way. Anaconda specializes in packaging for scientific computing handling packaging non-python extensions (e. g. C, C++) dependencies well.



    ** Note on conda vs source for environment activation **



    If conda activate does not work use source activate. This was changed in Anaconda 4.4.0 Release Notes.



    If you have this in your .bash_profile (or .profile or other magical dotfile) you use source activate:




    export PATH="$HOME/anaconda3/bin:$PATH"



    If you have this updated code in your shell startup then you can use conda activate:




    . $HOME/anaconda3/etc/profile.d/conda.sh
    conda activate






    share|improve this answer















    Anaconda comes with a package and environment manager called conda. This is what you need to do:



    Create a separate Python 2.7 environment, let's call it old and busted.



    conda create --name old_and_busted python=2.7



    Now switch to this environment:



    conda activate old_and_busted



    Verify it worked if you want:



    python --version



    Install something cool:



    conda install flask



    Bonus, use pip to install something cool in the same environment:



    pip install flask



    What environment are we in again?



    conda env list



    Let's check for that package:



    conda list



    Now this part is very important, make sure to do it often - go back to your Python 3 environment:



    conda activate base



    pipenv manages environments in a similar way. Anaconda specializes in packaging for scientific computing handling packaging non-python extensions (e. g. C, C++) dependencies well.



    ** Note on conda vs source for environment activation **



    If conda activate does not work use source activate. This was changed in Anaconda 4.4.0 Release Notes.



    If you have this in your .bash_profile (or .profile or other magical dotfile) you use source activate:




    export PATH="$HOME/anaconda3/bin:$PATH"



    If you have this updated code in your shell startup then you can use conda activate:




    . $HOME/anaconda3/etc/profile.d/conda.sh
    conda activate







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Nov 20 '18 at 5:20

























    answered Nov 20 '18 at 4:30









    dwagnerkcdwagnerkc

    25417




    25417













    • it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

      – sonictl
      Nov 20 '18 at 5:10











    • I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

      – dwagnerkc
      Nov 20 '18 at 5:13













    • This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

      – sonictl
      Nov 20 '18 at 5:19













    • Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

      – dwagnerkc
      Nov 20 '18 at 5:25











    • Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

      – dwagnerkc
      Nov 20 '18 at 5:28



















    • it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

      – sonictl
      Nov 20 '18 at 5:10











    • I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

      – dwagnerkc
      Nov 20 '18 at 5:13













    • This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

      – sonictl
      Nov 20 '18 at 5:19













    • Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

      – dwagnerkc
      Nov 20 '18 at 5:25











    • Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

      – dwagnerkc
      Nov 20 '18 at 5:28

















    it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

    – sonictl
    Nov 20 '18 at 5:10





    it asked me to run "source activate old_and_busted" rather than "conda activate old_and_busted"

    – sonictl
    Nov 20 '18 at 5:10













    I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

    – dwagnerkc
    Nov 20 '18 at 5:13







    I'll update the answer for clarity, its a version difference: github.com/conda/conda/blob/…

    – dwagnerkc
    Nov 20 '18 at 5:13















    This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

    – sonictl
    Nov 20 '18 at 5:19







    This answer quickly solved my problem and let my python2.7 code got launched. But I still do not systematically understand about how the python2 or 2+3 env works. Where can i find some comprehensive documents to learn about this? thank you guys so much!!

    – sonictl
    Nov 20 '18 at 5:19















    Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

    – dwagnerkc
    Nov 20 '18 at 5:25





    Great! Start here: conda.io/docs/user-guide/concepts.html One particular thing that helped me was knowing that uninstalling Anaconda and all environments is as easy as rm -rf ~/anaconda/ It is all contained in there. Go ahead and cd ~/anaconda/envs/ and see the environment you created. Also, for historical understanding this is one of my favorite posts ever (question isn't asked about conda, but goes over all the virtual environment managers): stackoverflow.com/questions/41573587/…

    – dwagnerkc
    Nov 20 '18 at 5:25













    Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

    – dwagnerkc
    Nov 20 '18 at 5:28





    Since this is your first question I'll add be sure to accept an answer so that others can reference it in the future.

    – dwagnerkc
    Nov 20 '18 at 5:28













    0














    You can use pyenv



    Firstly you should install pyenv.



    use



    pyenv versions


    check all version on your computer.



    use



    pyenv global 3.4.0


    setting your current gobal python version.



    use



    pyenv install 3.4.0



    install a specific version of Python.



    You can find more usage in the documentation.






    share|improve this answer
























    • My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

      – sonictl
      Nov 20 '18 at 4:12













    • @sonictl So you should try pyenv install 2.7.0

      – Mark White
      Nov 20 '18 at 4:57
















    0














    You can use pyenv



    Firstly you should install pyenv.



    use



    pyenv versions


    check all version on your computer.



    use



    pyenv global 3.4.0


    setting your current gobal python version.



    use



    pyenv install 3.4.0



    install a specific version of Python.



    You can find more usage in the documentation.






    share|improve this answer
























    • My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

      – sonictl
      Nov 20 '18 at 4:12













    • @sonictl So you should try pyenv install 2.7.0

      – Mark White
      Nov 20 '18 at 4:57














    0












    0








    0







    You can use pyenv



    Firstly you should install pyenv.



    use



    pyenv versions


    check all version on your computer.



    use



    pyenv global 3.4.0


    setting your current gobal python version.



    use



    pyenv install 3.4.0



    install a specific version of Python.



    You can find more usage in the documentation.






    share|improve this answer













    You can use pyenv



    Firstly you should install pyenv.



    use



    pyenv versions


    check all version on your computer.



    use



    pyenv global 3.4.0


    setting your current gobal python version.



    use



    pyenv install 3.4.0



    install a specific version of Python.



    You can find more usage in the documentation.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 20 '18 at 2:53









    Mark WhiteMark White

    407310




    407310













    • My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

      – sonictl
      Nov 20 '18 at 4:12













    • @sonictl So you should try pyenv install 2.7.0

      – Mark White
      Nov 20 '18 at 4:57



















    • My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

      – sonictl
      Nov 20 '18 at 4:12













    • @sonictl So you should try pyenv install 2.7.0

      – Mark White
      Nov 20 '18 at 4:57

















    My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

    – sonictl
    Nov 20 '18 at 4:12







    My cmd does not show all the versions i installed: pyenv versions shows me : * system (set by ~/.pyenv/version)

    – sonictl
    Nov 20 '18 at 4:12















    @sonictl So you should try pyenv install 2.7.0

    – Mark White
    Nov 20 '18 at 4:57





    @sonictl So you should try pyenv install 2.7.0

    – Mark White
    Nov 20 '18 at 4:57











    0














    Python ships in two primary ways, python for Python 2, and python3 for Python 3.x. The pips for both are pip and pip3, respectively.



    Echoing what @Mark White said in his answer, you should use pyenv to ensure env parity.






    share|improve this answer




























      0














      Python ships in two primary ways, python for Python 2, and python3 for Python 3.x. The pips for both are pip and pip3, respectively.



      Echoing what @Mark White said in his answer, you should use pyenv to ensure env parity.






      share|improve this answer


























        0












        0








        0







        Python ships in two primary ways, python for Python 2, and python3 for Python 3.x. The pips for both are pip and pip3, respectively.



        Echoing what @Mark White said in his answer, you should use pyenv to ensure env parity.






        share|improve this answer













        Python ships in two primary ways, python for Python 2, and python3 for Python 3.x. The pips for both are pip and pip3, respectively.



        Echoing what @Mark White said in his answer, you should use pyenv to ensure env parity.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 '18 at 2:53









        e.maguiree.maguire

        79112




        79112






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385448%2fhow-can-i-manage-the-modules-for-python2-when-python3-installed-as-well-in-osx%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith