
This requires one more initial step, but requires less maintenance in the long run and avoids duplicate Spyder installs.

#Spyder ide install#
Install just the spyder-kernels package into the myenv environment, and set your Python interpreter path in Spyder's Preferences to point to myenv's Python executable (see the final section.This is a little simpler than the third option and has the same effect, but more overhead and is less flexible. Install Spyder into the existing myenv environment, or any other you'd like to work in, and run it from there (see following section).If you try to install future packages in another environment (like myenv), you'll get the same ModuleNotFoundError. Activate the environment in which Spyder is installed and install your package on it (see next section).If the resulting paths are different, then you have three choices: If the resulting paths are the same, then Spyder and the package are in the same environment, and import foo shouldn't produce an error (or else there is likely an unrelated issue with your installation).

Start Spyder and run the same command shown in Step 3 in a Console. The most common problem: Using newly-installed packages inside SpyderĪfter installing a package (let's call it foo) outside Spyder, users may encounter an error trying to import it inside the IDE:
