Skip to content
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

setting pythonpath in launch.json fails #376

Closed
weinand opened this issue Dec 8, 2017 · 2 comments
Closed

setting pythonpath in launch.json fails #376

weinand opened this issue Dec 8, 2017 · 2 comments
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@weinand
Copy link

weinand commented Dec 8, 2017

From @elypma on December 6, 2017 13:5

  • VSCode Version: 1.18.1
  • OS Version: windows 7

Steps to Reproduce:

  1. Create an empty .env file in the ${workspaceRoot} (which is confusing with multiple folders)
  2. Set the pythonpath in launch.json:
    "envFile": "${workspaceRoot}/.env",
    "env": {
    "PYTHONPATH": "${workspaceRoot}/_common/packages"
    },
  3. This only works when the "envFile" setting is completely removed or when the .env file is deleted.

Reproduces without extensions: No (depends on python extension)

Copied from original issue: microsoft/vscode#39790

@brettcannon brettcannon added awaiting 1-verification bug Issue identified by VS Code Team member as probable bug labels Dec 11, 2017
@DonJayamanne DonJayamanne added info-needed Issue requires more information from poster and removed awaiting 1-verification labels Dec 20, 2017
@DonJayamanne
Copy link

@elypma

  • Please do not use ${workspaceRoot}, you need to use ${workspaceFolder} more info

This only works when the "envFile" setting is completely removed or when the .env file is deleted.

Please could you describe the behavior you are currently experiencing, and the expected behavior.

Please note, we have identified a couple of issues around this area that we'll be fixing in the next release (#466).

@DonJayamanne DonJayamanne added this to the January 2018 milestone Dec 20, 2017
@brettcannon brettcannon removed this from the January 2018 milestone Jan 9, 2018
@DonJayamanne
Copy link

I'm closing this issue for to inactivity. If you come across this issue again, please reply with the requested comments and reopen the issue.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants