Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Intended behaviour of add_pathlist_to_PYTHONPATH not clear
See original GitHub issueWhat is the intended behaviour is of the function add_pathlist_to_PYTHONPATH() in spyder.utils.misc? That function is used in the unittest plugin, but I’m not sure what it is supposed to do and whether it is used correctly in the plugin.
This is prompted by the following comment in PR spyder-ide/spyder-unittest#150 (but I remember that I was puzzled by this in the past):
I’m not sure if this isn’t a logic flaw in
add_pathlist_to_PYTHONPATH: I think ifipyconsoleisFalseit should look forPYTHONPATHnot in the actual OS environment but in the passed-inenvlist.
This function is ten years old and added in commit eeb594aec07ac6d854177179fcf226febd3379e3 by Pierre.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It looks much better now, thanks!
Great! I think the original intent of that function was the one I left in PR #14022.
The problem is I hijacked it to use it in our kernelspec several years ago.