These are chat archives for spyder-ide/public

18th
Apr 2019
paulgureghian
@paulgureghian_gitlab
Apr 18 01:39
I thought if I create a 3.6 env and put Spyder in that same env then Spyder runs on that version ?
CAM Gerlach
@CAM-Gerlach
Apr 18 01:40
Yes, but that's completely unnecessary. Please read the guide to working with packages and environments with Spyder; I would be surprised if I haven't sent it to you at least once before.
paulgureghian
@paulgureghian_gitlab
Apr 18 01:49
I switched interpreters and I got the version I wanted but then the packages would no longer import.
CAM Gerlach
@CAM-Gerlach
Apr 18 01:50
Of course. And you'd know why, if you read the article I asked you to, which is explicitly written to address that exact situation.

Literally the first line of the first section:

After installing a package (let's call it foo) outside Spyder, users may encounter an error trying to import it inside the IDE.

This happens because foo was installed (with either conda or pip) in a different conda or venv/virtualenv environment than the one in which Spyder is currently running.

And the entire rest of the article explains multiple options for resolving that situation.
paulgureghian
@paulgureghian_gitlab
Apr 18 01:59
I put them in the same env as Spyder
I didn't have these problems with Windows. if I installed a package with conda or pip it would still import
CAM Gerlach
@CAM-Gerlach
Apr 18 02:20
Probably because you have your environments set up differently.
paulgureghian
@paulgureghian_gitlab
Apr 18 20:26
In the Spyder terminal on Fedora, it has (base) user@host. Is the 'base' here , the base env or some Linux term ? Even when I am in a custom conda env I still have the 'base'
CAM Gerlach
@CAM-Gerlach
Apr 18 20:31

Spyder terminal

You mean Spyder-Terminal?

Is the 'base' here , the base env or some Linux term ?

Its the base env.

Even when I am in a custom conda env I still have the 'base'

Then you have not correctly activate-d your environment in the terminal.

paulgureghian
@paulgureghian_gitlab
Apr 18 20:36
I created the env in Navigator, I thought it automatically activates it ?
If I am outside of Spyder Terminal in a terminal session on the desktop is the (base) still the base env ?
CAM Gerlach
@CAM-Gerlach
Apr 18 20:40

I created the env in Navigator, I thought it automatically activates it ?

I have no idea if Navigator does, but using conda from the command line does not do so when creating a new environment (and it explicitly reminds you to do so). I'm not sure how what Navigator does or doesn't do is relevant, since you are discussing working in some terminal (which, you have not yet clarified in response to my question). Furthermore, I've long since lost how any of this has to do with Spyder, beyond the relevant parts already explained in the guide I linked you. Other than that, please direct your non-Spyder-related conda, Navigator and Anaconda questions to the appropriate people and venues, not the Spyder team. Thanks.

CAM Gerlach
@CAM-Gerlach
Apr 18 20:46

If I am outside of Spyder Terminal in a terminal session on the desktop is the (base) still the base env ?

I don't see how that has anything to do with Spyder, but...

If it says base, (base) is still the base env, because (base) is the base env. If (base) is shown, then base is the environment in which you are in. The purpose of (base) is to show you are in the base environment. The base environment is indicated by the (base) tag. All your base envs are belong to us.

So yes.