Skip to content

Environment gets activated after debugger starts (hence debugging with conda envs fail) #5559

Closed
Closed
Environment gets activated after debugger starts (hence debugging with conda envs fail)#5559
Assignees
DonJayamanne
Labels
area-debuggingbugIssue identified by VS Code Team member as probable bug
Milestone
FY20Q2

Description

@crackcomm
Łukasz Kurowski (crackcomm)
opened on May 5, 2019

Environment data

  • VS Code version: Just updated
  • Extension version (available under the Extensions sidebar): Just updated
  • OS and version: Windows 10
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3.7, Conda3
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Issue

Use Debug Python: Current File...

> cd ...
[...]
    from matplotlib import afm, cbook, ft2font, rcParams, get_cachedir
ImportError: DLL load failed: The specified module could not be found.

>D:/Anaconda3/Scripts/activate
>conda activate base

Terminal stays open so I can click again the play icon and it works because conda activate base activated Python environment just AFTER the debugger FAILED to start.

Thank you.

Activity

  1. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on May 5, 2019

  2. karrtikr commented on May 14, 2019

    @karrtikr
    Kartik Raj (karrtikr)
    on May 14, 2019

    Can you please be more clear here. I am not sure I understand the issue here.

    Terminal stays open so I can click again the play icon and it works

    • ... what works?
    • Please provide file content, complete exact terminal display (for eg. what does [...] represent in cd ...) and clarify the steps to reproduce.
  3. Kartik Raj (karrtikr)
    self-assigned this
    on May 14, 2019
  4. Kartik Raj (karrtikr)
    added
    info-neededIssue requires more information from poster
    triage
    on May 14, 2019
  5. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on May 14, 2019
  6. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on May 14, 2019

  7. crackcomm commented on May 15, 2019

    @crackcomm
    Łukasz Kurowski (crackcomm)
    on May 15, 2019
    Author
    • ... debugger?
    • Use Debug Python: Current File...

  8. karrtikr commented on May 15, 2019

    @karrtikr
    Kartik Raj (karrtikr)
    on May 15, 2019

    Please fill the issue template and provide the requested information. The issue is not clear.

  9. crackcomm commented on May 15, 2019

    @crackcomm
    Łukasz Kurowski (crackcomm)
    on May 15, 2019
    Author

    No, thanks.

  10. karrtikr commented on May 15, 2019

    @karrtikr
    Kartik Raj (karrtikr)
    on May 15, 2019

    Closing this as sufficient clarification info was not provided.

  11. Kartik Raj (karrtikr)
    closed this as completedon May 15, 2019
  12. ghost removed
    info-neededIssue requires more information from poster
    on May 15, 2019
  13. ghost removed
    triage
    on May 15, 2019

  14. crackcomm commented on May 15, 2019

    @crackcomm
    Łukasz Kurowski (crackcomm)
    on May 15, 2019 · Hidden as abuse
    Author

  15. 21 remaining items

  16. Don Jayamanne (DonJayamanne)
    removed
    triage
    on May 16, 2019

  17. DonJayamanne commented on May 16, 2019

    @DonJayamanne
    Don Jayamanne (DonJayamanne)
    on May 16, 2019

    Solution identified in microsoft/vscode#67692 could fix this.

    Updated Solution - Use conda run.

  18. Don Jayamanne (DonJayamanne)
    self-assigned this
    on Aug 7, 2019

  19. bryceschober commented on Aug 7, 2019

    @bryceschober
    Bryce Schober (bryceschober)
    on Aug 7, 2019

    Don Jayamanne (@DonJayamanne) Can you clarify your proposed solution of conda run? Are you proposing a modified launch configuration? Could you provide an example?

  20. DonJayamanne commented on Aug 12, 2019

    @DonJayamanne
    Don Jayamanne (DonJayamanne)
    on Aug 12, 2019

    Bryce Schober (@bryceschober) this isn't a change to the launch configuration. Instead of running user code using <python executable> <user code> we'll be using conda run <env name> python <user code>.

  21. Don Jayamanne (DonJayamanne)
    changed the title [-]Environment is activated after debugger fails[/-] [+]Environment gets activated after debugger starts (hence debugging with conda envs fail)[/+] on Aug 15, 2019

  22. AlexH415 commented on Oct 11, 2019

    @AlexH415
    AlexH415
    on Oct 11, 2019

    I seem to have this problem too. I don't understand what is meant by "Instead of running user code using we'll be using conda run python .". Is this a fix I can apply myself now? If so, how do I do it please?

  23. damdaepark commented on Oct 15, 2019

    @damdaepark
    Damdae Park (damdaepark)
    on Oct 15, 2019

    Don Jayamanne (@DonJayamanne) You mean this conda run solution will be updated soon?

  24. DonJayamanne commented on Oct 15, 2019

    @DonJayamanne
    Don Jayamanne (DonJayamanne)
    on Oct 15, 2019

    That is the plan.

  25. Graham Wheeler (gramster)
    added this to the FY20Q2 milestone on Oct 30, 2019

  26. kimadeline commented on Apr 8, 2020

    @kimadeline
    Kim-Adeline Miguel (kimadeline)
    on Apr 8, 2020

    Closing in favour of #10626

  27. Kim-Adeline Miguel (kimadeline)
    closed this as completedon Apr 8, 2020
  28. ghost removed
    needs PR
    on Apr 8, 2020
  29. ghost removed
    needs upstream fix
    on Apr 8, 2020
  30. lock
    locked as resolved and limited conversation to collaborators on Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-debuggingbugIssue identified by VS Code Team member as probable bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions