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.
Feature request: per-project Python interpreter
See original GitHub issueRelated issues: #9804 (project settings, you guys are considering Conda envs which is a similar usecase) #1014 (exactly this, imported from google code and seemingly abandoned)
Currently interpreters are a global setting. It would be great to have a Python interpreter selectable as a project-level preference instead.
In #9804 it looks like you are considering allowing project-level Conda, but I don’t use Conda. I just use a virtualenv per project (managed by poetry; pipenv users will have a similar/identical setup). This means I just want to set every project’s interpreter to ./.venv/bin/python, relative to the project root.
For bonus points it would be nice to detect the existence of a pyproject.toml (https://www.python.org/dev/peps/pep-0518/), check if poetry is used (likewise for any other pyproject.toml-using tools), and if so then autoconfigure project interpreter to be the default under poetry env.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:20 (7 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
This feature hasn’t been implemented yet, sorry.
@svdHero, sorry to hear that. Unfortunately, we are a small team and this is kind of a big feature. We’ll try to implement it for Spyder 6, to be released at the end of this year or the beginning of 2022.