1

Specifically I'm thinking about conflicting preferences/config/autosave files, since spyder (currently installed to my default base cond env) creates a .spyder-py3 directory in my userprofile as well as many other things.

Are there any special considerations I should take into account before installing a second instance in another conda env. I want to install a newer version of spyder that conflicts with some files in my monolithic base environ.

Greedo
  • 4,967
  • 2
  • 30
  • 78
  • 1
    Personally, I would only ever install infrastructure, such as Spyder, once on a system, and provide a dedicated environment (not **base**) for it. [Spyder supports loading other Conda environments as kernels](https://github.com/spyder-ide/spyder/wiki/Working-with-packages-and-environments-in-Spyder#working-with-other-environments-and-python-installations). – merv Oct 23 '21 at 21:29
  • @merv yeah that's broadly my plan, although it kind of defeats one of the 2 reasons to use anaconda which is that its base environ comes with a load of common packages installed by default. This was the main selling point when I was a beginner. (The other reason is conda package management) – Greedo Oct 26 '21 at 08:19
  • 1
    (*Spyder maintainer here*) There's no problem on installing Spyder in as many environments as you want. The only thing to take into account is that all installed Spyder's read their configuration from the same directory (i.e. the `spyder-py3` directory you mentioned above), and that could give you problems when running different versions. – Carlos Cordoba Dec 09 '21 at 23:56
  • 1
    However, in Spyder **5.1.2** we added a command line option called `--conf-dir` to point to a specific directory to read and write Spyder's configuration. That will avoid that issue. – Carlos Cordoba Dec 09 '21 at 23:58

0 Answers0