Problem with parsing .env values during debugging
See original GitHub issueEnvironment data
- VS Code version: 1.27.2
- Extension version (available under the Extensions sidebar): 2018.8.0
- OS and version: Ubuntu 16.04
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.6
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): pipenv
Actual behavior
abcls -l
Expected behavior
abc!23
Steps to reproduce:
- In
launch.json
:
...
{
"name": "Python: Application",
"type": "python",
"request": "launch",
"program": "${workspaceFolder}/bin/application.py",
"envFile": "${workspaceFolder}/.env"
},
...
- In
.env
:
SOME_PASSWORD=abc!23
- In
application.py
:
import os
print(os.environ['SOME_PASSWORD'])
Issue Analytics
- State:
- Created 5 years ago
- Comments:9
Top Results From Across the Web
Using and Debugging Environment Variables - Software Verify
How to use environment variables to configure Validator tools, and how to debug them when the use of them doesn't work as expected....
Read more >Wrong parsing the environment variable
Hi all, I saw some other thread here having a similar problem with the environment variable of the debugging interface of the project...
Read more >Problem with parsing of environment variables - rclone forum
i am having issues with the parsing of environment variables. in this case, remote-x: does not exist, but rclone will use it.
Read more >How to resolve JSON Parse Error When Not in Debug Mode?
I have the following code block where I'm passing from my .env, in a string that stores a json with the credentials for...
Read more >Understanding Docker Build Args, Environment Variables and ...
An overview of ways to set and use variables when building images, starting containers and using docker-compose.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@GaramNick @PEKTOP please could you both install the insiders build of VS Code from here - https://code.visualstudio.com/insiders/. I believe this issue with (escaping) special characters in the terminal has been resolved.
Closing this as it’s an upstream issue (caused by a bug in VSCode(