-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Test Discovery failed: Error: EISDIR: illegal operation on a directory, read #435
Comments
Please could you provide the contents of your workspace settings (settings.json) |
Of course, thank you for fast response {
"editor.fontSize": 12,
"terminal.integrated.fontSize": 12,
"git.enableSmartCommit": true,
"html.format.contentUnformatted": "pre, style",
"html.format.maxPreserveNewLines": 0,
"editor.renderControlCharacters": true,
"editor.renderWhitespace": "none",
"editor.minimap.enabled": true,
"python.unitTest.pyTestEnabled": true,
"python.unitTest.pyTestArgs": [
"--exitfirst"
,"--verbose"
,"--disable-warnings"
,"--no-cov"
,"-s"
],
"python.linting.enabled": true,
"python.linting.pylintEnabled": true,
"python.linting.pylintArgs": [
"--disable=E1101,C0103,C0111,C0301,W0235,R0903,R0913"
],
"python.linting.pep8Enabled": true,
"python.linting.pep8Args": [
"--ignore=W291,W293,E501"
],
"python.formatting.provider": "autopep8",
"files.exclude": {
"**/*.pyc": true
},
"javascript.format.enable": true,
"standard.autoFixOnSave": true,
"window.zoomLevel": 0,
"workbench.colorTheme": "Visual Studio Light",
"workbench.editor.enablePreview": true,
"extensions.ignoreRecommendations": false,
"terminal.integrated.shell.osx": "/bin/zsh",
"search.exclude": {
"**/node_modules": true,
"**/bower_components": true,
"**/htmlcov": true
}
} |
"python.envFile": "${workspaceFolder}/.envFile" |
That made the fix. Test discovery and execution is running as normal. Thanks very much for the fast support, my env is up and running for now! Did I screw up anything in my configs or actually helped find out a bug? |
Please could you confirm the above. |
Yes I do, I used to setup virtualenv on .env/, then activate it on terminal then opening code . to start working |
Thanks, yes you have helped us find an interesting bug. Looks like a nodejs bug of some sorts. Will have to implement a workaround. Thanks, should be easy enough to fix. |
Happy for that! Thank you very much! |
It looks like I have hit a similar bug to this. For me the symptom was after creating a virtualenv in After creating the empty |
I got here from #482 , and just wanted to confirm that this solution worked for me as well. None of the Python linters or Mypy were working, and I had a .env directory in the workspace. Thanks for the solution! |
I had the same problem, the .envFile worked for me too 😄 |
Refactor how environment variables are parsed and used in tools, language server and debugger Fixes #316 (PYTHONPATH not used as extra path for auto complete) Fixes #183 (changes to .env file requires restarts of vscode) Fixes #436 (Path variables not inherited when debugging) Fixes #435 (Virtual environment name is same as the default environment file)
Environment data
VS Code version: November 2017 (version 1.19)
Python Extension version: Version 0.9.0 (14 December 2017)
Python Version: 2.7.14
OS and version: OSX 10.13.1
Actual behavior
Test discovery is not working.
Steps to reproduce:
Logs
Output from
Python
output panelOutput from
Console window
(Help->Developer Tools menu)The text was updated successfully, but these errors were encountered: