vscode-python: Debugging stops working when the .env file has more than 556 characters
Environment data
- VS Code version: 1.22.2
- Extension version: 2018.3.1
- OS and version: Windows 7 64bits
- Python version: 3.6.5 64bits
- Type of virtual environment used: pipenv
Actual behavior
Debugging completely stops working when the .env
file has more than 556 characters and does not display any error or log message. It’s necessary to restart the VSCode to work again if the .env
file is less than 556 characters long (ignoring spaces).
Expected behavior
Debugging well…
Steps to reproduce:
- Type more than 556 characters in
.env
file (sum of var names, values, etc). - Type F5 or click menu Debug>Start Debugging.
Logs
Output for Python
in the Output
panel
(View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
NOTHING!
Output from Console
under the Developer Tools
panel (toggle Developer Tools on under Help
)
NOTHING!
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 19 (2 by maintainers)
@FlavioCestari I believe the issue has been resolved in the insiders version of VS Code. Please could you test this out and let us know how it is. Please ensure you test this with the Insiders Build of VS Code