Debugging fails when using a pipenv environment that gets activated with pipenv shell #4203

Activity

1. Don Jayamanne (DonJayamanne)

   added

   triage

   on Jan 29, 2019
2. Don Jayamanne (DonJayamanne)

   self-assigned this

   on Jan 29, 2019
3. Adanteh commented on Jan 30, 2019

   

   Adanteh

   on Jan 30, 2019

   Last edited by Adanteh

   More actions

   Got this issue since today. Was perfectly fine before.

   PS <path> pipenv shell
   Loading .env environment variables…
   Launching subshell in virtual environment…
   Windows PowerShell
   Copyright (C) Microsoft Corporation. All rights reserved.
   

   is all it does when I open up debugging.

   👍React with 👍1Reacted by Andrea
4. DonJayamanne commented on Jan 30, 2019

   

   Don Jayamanne (DonJayamanne)

   on Jan 30, 2019

   Author

   More actions

   Temporary work around

   • Go into settings (workspace settings, .vscode/settings.json)
   • Add the following:
     "python.terminal.activateEnvironment": false,

   👍React with 👍9Reacted by Felipe Lube de Bragança, JoBrad, olegasdo, Russell Davis, 里丰, Pedro Igor, Roman Lukomskyi, Roman Kornev and Bao Ho

   🎉React with 🎉1Reacted by 里丰
5. Don Jayamanne (DonJayamanne)

   added

   importantIssue identified as high-priorityIssue identified as high-priority

   on Jan 30, 2019
6. Handsome2734 commented on Jan 31, 2019

   

   Handsome2734 (Handsome2734)

   on Jan 31, 2019

   Last edited by Handsome2734

   More actions

   Temporary work around

   • Go into settings (workspace settings, .vscode/settings.json)
   • Add the following:
     "python.terminal.activateEnvironment": false,

   This works for the first time. But the issue still happens after "Restart" debugger.
   
   And I think I heard a beep after I clicked Restart...

   👍React with 👍2Reacted by Felipe Lube de Bragança and Adanteh
7. JoBrad commented on Jan 31, 2019

   

   JoBrad

   on Jan 31, 2019

   Last edited by JoBrad

   More actions

   I just started having this issue today, and noticed the debug command was being cut off. Adding the python.terminal.activateEnvironment setting corrected this, but I can only execute the script completely - line-by-line debugging doesn't work (tried in VS Code Insiders and stable).

   👍React with 👍1Reacted by Felipe Lube de Bragança
8. Don Jayamanne (DonJayamanne)

   added

   bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

   area-debugging

   area-terminal

   and removed

   triage

   on Jan 31, 2019
9. Don Jayamanne (DonJayamanne)

   modified the milestones: 2019, week 5 - Jan Sprint 3, 2019, week 7 - Jan Sprint 4 on Jan 31, 2019
10. Don Jayamanne (DonJayamanne)

    added

    P0

    on Feb 1, 2019
11. 20 remaining items

    Load more
12. Luciana Abud (luabud)

    removed

    needs upstream fix

    upstream-vscode

    on Mar 11, 2020
13. ghost added

    triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

    on Mar 11, 2020
14. ghost added

    triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

    on Mar 11, 2020
15. ghost added

    triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

    on Mar 11, 2020
16. Luciana Abud (luabud)

    added

    needs PR

    and removed

    triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

    on Mar 11, 2020
17. DonJayamanne commented on Mar 29, 2020

    

    Don Jayamanne (DonJayamanne)

    on Mar 29, 2020

    Author

    More actions

    We reverted old implementation #4394
18. Brett Cannon (brettcannon)

    added

    regressionBug didn't exist in a previous releaseBug didn't exist in a previous release

    on Apr 7, 2020
19. GBrachetta commented on Dec 3, 2020

    

    Guillermo Brachetta (GBrachetta)

    on Dec 3, 2020

    More actions

    In my case, "python.terminal.activateEnvironment": false doesn't prevent pipenv from starting a new shell.
    My workaround is to temporarily rename Pipfile before running the debugger, and that's the only way to get it working as far as I can tell.
    I'd love to know if the launch.json file could be tweaked to sort this issue more elegantly!
20. Kartik Raj (karrtikr)

    added this to the October 2021 milestone on Oct 22, 2021
21. karrtikr commented on Oct 22, 2021

    

    Kartik Raj (karrtikr)

    on Oct 22, 2021

    More actions

    Closing as we no longer use pipenv shell command: #10611 (comment)
22. Kartik Raj (karrtikr)

    closed this as completedon Oct 22, 2021
23. Kartik Raj (karrtikr)

    added

    verifiedVerification succeededVerification succeeded

    on Oct 25, 2021
24. github-actions

    locked as resolved and limited conversation to collaborators on Nov 26, 2021