Creating python virtual environment in Visual Studio fails: returned non-zero exit status 1










0















In Visual Studio 2015 and 2017, I always get an error when trying to create a virtual environment with certain base interpreters.



Base interpreters that work:



  • Python 3.6 32-bit

  • Python 2.7, 64-bit

  • Anaconda 5.0.1 (2.7, 64-bit)

Base interpreters that give error:



  • Anaconda 5.0.1 (3.6, 64-bit)

  • Python 3.6 64-bit

The error:




Error: Command '['F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4Scriptspython.exe', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'. Exit code: 1
Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'











share|improve this question




























    0















    In Visual Studio 2015 and 2017, I always get an error when trying to create a virtual environment with certain base interpreters.



    Base interpreters that work:



    • Python 3.6 32-bit

    • Python 2.7, 64-bit

    • Anaconda 5.0.1 (2.7, 64-bit)

    Base interpreters that give error:



    • Anaconda 5.0.1 (3.6, 64-bit)

    • Python 3.6 64-bit

    The error:




    Error: Command '['F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4Scriptspython.exe', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
    Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'. Exit code: 1
    Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'











    share|improve this question


























      0












      0








      0








      In Visual Studio 2015 and 2017, I always get an error when trying to create a virtual environment with certain base interpreters.



      Base interpreters that work:



      • Python 3.6 32-bit

      • Python 2.7, 64-bit

      • Anaconda 5.0.1 (2.7, 64-bit)

      Base interpreters that give error:



      • Anaconda 5.0.1 (3.6, 64-bit)

      • Python 3.6 64-bit

      The error:




      Error: Command '['F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4Scriptspython.exe', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
      Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'. Exit code: 1
      Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'











      share|improve this question
















      In Visual Studio 2015 and 2017, I always get an error when trying to create a virtual environment with certain base interpreters.



      Base interpreters that work:



      • Python 3.6 32-bit

      • Python 2.7, 64-bit

      • Anaconda 5.0.1 (2.7, 64-bit)

      Base interpreters that give error:



      • Anaconda 5.0.1 (3.6, 64-bit)

      • Python 3.6 64-bit

      The error:




      Error: Command '['F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4Scriptspython.exe', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
      Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'. Exit code: 1
      Virtual environment was not created at 'F:OneDriveVisual Studio 2017 ProjectsWeb TestDjangoWebProject1DjangoWebProject1env4'








      python visual-studio virtual-environment






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 11 '18 at 5:06









      Shiladitya

      9,39391830




      9,39391830










      asked Nov 11 '18 at 4:57









      AbbarnesAbbarnes

      12




      12






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Turns out this was a known issue with previous versions of Anaconda. The Python 3.6 64-bit interpreter that was listed as giving an error was actually an Anaconda version of Python as well.



          Simply using the package manager to upgrade to the most recent versions of Anaconda fixed the issues.






          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%2f53245974%2fcreating-python-virtual-environment-in-visual-studio-fails-returned-non-zero-ex%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Turns out this was a known issue with previous versions of Anaconda. The Python 3.6 64-bit interpreter that was listed as giving an error was actually an Anaconda version of Python as well.



            Simply using the package manager to upgrade to the most recent versions of Anaconda fixed the issues.






            share|improve this answer



























              0














              Turns out this was a known issue with previous versions of Anaconda. The Python 3.6 64-bit interpreter that was listed as giving an error was actually an Anaconda version of Python as well.



              Simply using the package manager to upgrade to the most recent versions of Anaconda fixed the issues.






              share|improve this answer

























                0












                0








                0







                Turns out this was a known issue with previous versions of Anaconda. The Python 3.6 64-bit interpreter that was listed as giving an error was actually an Anaconda version of Python as well.



                Simply using the package manager to upgrade to the most recent versions of Anaconda fixed the issues.






                share|improve this answer













                Turns out this was a known issue with previous versions of Anaconda. The Python 3.6 64-bit interpreter that was listed as giving an error was actually an Anaconda version of Python as well.



                Simply using the package manager to upgrade to the most recent versions of Anaconda fixed the issues.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 30 '18 at 14:58









                AbbarnesAbbarnes

                12




                12



























                    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%2f53245974%2fcreating-python-virtual-environment-in-visual-studio-fails-returned-non-zero-ex%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

                    𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                    Crossroads (UK TV series)

                    ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế