-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add VS code settings.json file #42
Conversation
Just to note that my plan is not to use the *.ipynb format for Jupyter notebooks. See: I don't know if that changes the settings. |
Overview of VS code settings: https://code.visualstudio.com/docs/getstarted/settings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The testing options are for VSCode. Just setup.cfg
or pyproject.toml
is not enough.
], | ||
"python.testing.unittestEnabled": false, | ||
"python.testing.pytestEnabled": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be here, otherwise VSCode testing does not know what to use for tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still is set to true
! See below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
omg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Submitting a sample review.
So I think we can drop the |
Ok, we can leave it like that and change it if it does not work |
As discussed with @dalonsoa. I've also added a tests folder.
.vscode/settings.json
Outdated
@@ -1,7 +1,22 @@ | |||
{ | |||
"python.testing.pytestArgs": [ | |||
"." | |||
"python.linting.pylintEnabled": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like pylint
isn't in the poetry
dev dependencies btw. Do we want to enable it or not?
I suggest we either don't use this linter or add it to the dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to use it - and it seems we want, right @davidorme - it should be in the dependency list, yes.
We could remove the setting if it's not needed. It shouldn't break things though! I leave that decision to the VR dev team. Would you like me to remove it or no? 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping aside adding pylint
to the dependency list, it looks good to me
.vscode/settings.json
Outdated
@@ -1,7 +1,22 @@ | |||
{ | |||
"python.testing.pytestArgs": [ | |||
"." | |||
"python.linting.pylintEnabled": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to use it - and it seems we want, right @davidorme - it should be in the dependency list, yes.
], | ||
"python.testing.unittestEnabled": false, | ||
"python.testing.pytestEnabled": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
omg
@davidorme says the plan isn't to use it.
So I started out by adding the settings.json file suggested by @dalonsoa, but I've made
a few changes:
workbench.tree.ident
andfiles.autosave
settings as I think thosearen't specific to this repo (users might want different settings)
black
does this already)pytest
settings: this should be done in a project-wide config file (e.g.setup.cfg)
--no-cov
topytest
args otherwise breakpoints won't work (see Debugger doesn't stop at breakpoints with pytest if pytest-cov is used microsoft/vscode-python#693)Closes #27.