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.
Update Working with packages and environments in Spyder?
See original GitHub issueHi and thanks for your great work, it is much appreciated 😃
I’ve been using Spyder for a while and like the approach of having just one Spyder instance installed in its dedicated conda environment (that I simply call spyder), it makes maintaining/updating Spyder easier if it’s just there on its own and not put together with 200 other packages. If I wanna connect Spyder to an other environment, I install spyder-kernels in that environment and change the Interpreter in the settings to point to the python executable of that environment. That works fine (most of the time!) and this way I have just one Spyder version installed, not in each environment (which would be a pain to maintain).
I got this trick from your wiki, here exactly. The page is a little old though, 09/2018, and maybe it needs to be updated? For instance, it suggests to run conda install spyder-kernels=0.*, which pins spyder-kernels to older (spyder 3.X?) versions.
I also wonder if my approach is still the right way? If so, I believe it should be better documented and probably added to the official docs, as it’s kind of hidden now unfortunately.
In the long run, I hope your team will have enough funding to get closer to the experience provided by vscode, i.e. a super smooth way to activate any environment from the GUI.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (9 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
@ccordoba12 @maximlt Done, just added a few commas, tweaked syntax a few places, cleaned up a few stray spaces/line breaks, and made one content-relevant change: added the manual venv activation script since
workonisn’t always available everywhere. Thanks so much for your help!I support adding this to the docs; I believe we initially wanted to but for whatever reason we didn’t. I’d be happy to submit a PR to get that done when the time is right; it also reflects a lot of what we tell people in our Pip vs. Conda video that we’re working on right now…maybe as material to accompany that? Or we can do it separately or later.
@ccordoba12 Sure, in work.