Package context file causing problems with pylint
up vote
0
down vote
favorite
I have been trying to setup a tests directory using the following document as a guide.
https://docs.python-guide.org/writing/structure/
In particular, when setting up a tests directory it mentions using a context.py file containing code similar to the following:
import os
import sys
sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), '..')))
import sample
and then importing it into a test file such as test_basic.py using something similar to:
from context import sample
This works perfectly well when I run my test script. The only problem I have is that within visual studio code, pylint highlights the context.py file red, which is annoying. The line that says 'import sample' is highlighted red and indicates that it is unable to import sample. Clearly pylint isn't seeing the parent directory being added to path before sample is imported.
Does anybody know how to fix this problem ?
Thanks
Mark
python unit-testing visual-studio-code package pylint
asked Nov 11 at 14:21
MarkyMark1000
11
add a comment |
up vote
0
down vote
favorite
I have been trying to setup a tests directory using the following document as a guide.
https://docs.python-guide.org/writing/structure/
In particular, when setting up a tests directory it mentions using a context.py file containing code similar to the following:
import os
import sys
sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), '..')))
import sample
and then importing it into a test file such as test_basic.py using something similar to:
from context import sample
This works perfectly well when I run my test script. The only problem I have is that within visual studio code, pylint highlights the context.py file red, which is annoying. The line that says 'import sample' is highlighted red and indicates that it is unable to import sample. Clearly pylint isn't seeing the parent directory being added to path before sample is imported.
Does anybody know how to fix this problem ?
Thanks
Mark
python unit-testing visual-studio-code package pylint
asked Nov 11 at 14:21
MarkyMark1000
11
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have been trying to setup a tests directory using the following document as a guide.
https://docs.python-guide.org/writing/structure/
In particular, when setting up a tests directory it mentions using a context.py file containing code similar to the following:
import os
import sys
sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), '..')))
import sample
and then importing it into a test file such as test_basic.py using something similar to:
from context import sample
This works perfectly well when I run my test script. The only problem I have is that within visual studio code, pylint highlights the context.py file red, which is annoying. The line that says 'import sample' is highlighted red and indicates that it is unable to import sample. Clearly pylint isn't seeing the parent directory being added to path before sample is imported.
Does anybody know how to fix this problem ?
Thanks
Mark
python unit-testing visual-studio-code package pylint
asked Nov 11 at 14:21
MarkyMark1000
11
I have been trying to setup a tests directory using the following document as a guide.
https://docs.python-guide.org/writing/structure/
In particular, when setting up a tests directory it mentions using a context.py file containing code similar to the following:
import os
import sys
sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), '..')))
import sample
and then importing it into a test file such as test_basic.py using something similar to:
from context import sample
This works perfectly well when I run my test script. The only problem I have is that within visual studio code, pylint highlights the context.py file red, which is annoying. The line that says 'import sample' is highlighted red and indicates that it is unable to import sample. Clearly pylint isn't seeing the parent directory being added to path before sample is imported.
Does anybody know how to fix this problem ?
Thanks
Mark
python unit-testing visual-studio-code package pylint
python unit-testing visual-studio-code package pylint
asked Nov 11 at 14:21
MarkyMark1000
11
asked Nov 11 at 14:21
MarkyMark1000
11
asked Nov 11 at 14:21
MarkyMark1000
11
asked Nov 11 at 14:21
MarkyMark1000
11
asked Nov 11 at 14:21
MarkyMark1000
11
11
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08
add a comment |
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249645%2fpackage-context-file-causing-problems-with-pylint%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
For anyone who is interested, you can turn off linting for a particular line of code using something like (error number obtained by hanging the mouse over the error): # pylint: disable=E0401
– MarkyMark1000
Nov 11 at 20:08