Spyder
A Python IDE for scientific computing and data analysis with an editor, IPython console, variable explorer, plots and integrated help.
What Spyder is for
Spyder combines a code editor, IPython console, variable explorer, plots and documentation panes for Python data work. It is useful for notebooks, scripts, numerical experiments and classroom exercises, while the Python environment that runs a script still needs to be identified separately.
Separate the IDE from the execution environment
A standalone installer has its own Python environment. A Conda installation may run inside a dedicated environment, and an external interpreter can be selected for a project. Installing a package into one interpreter does not make it available in another, so always check the active path before changing dependencies.
Make analysis sessions reproducible
Keep code, input data, generated figures and dependency notes in separate locations. Export an environment description before upgrading packages, and use a small sample before opening a large dataset in the variable explorer. This makes memory and dependency problems easier to isolate.
Maintenance note
This page covers Spyder installation, interpreter selection, IPython workflows and environment boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Spyder to this cloud drive
Baidu Netdisk
Save Spyder to this cloud drive
Spyder installation, interpreter selection and first analysis
First identify the Python interpreter used by the console, then run a small script and inspect its variables and plot output before importing a real dataset.
Before you start
- Choose a standalone installer for common use or a dedicated Conda environment for project-specific packages and plugins.
- Avoid mixing pip and Conda packages in a shared base environment until the dependency set is understood.
- Record the Python version, dependency list and data paths for an existing project.
Installation steps
- 01
Choose an installation mode
Use the standalone build for a quick start; use a dedicated environment when a project needs specific packages or integrations.
- 02
Launch and inspect the console
Open Spyder through the selected installation and check the Python path shown by the IPython console before installing anything.
- 03
Connect the intended interpreter
In the Python interpreter settings, choose the environment that will execute the project and restart the console to apply the change.
Quick start
- 01
Run a small script
Save a short Python file, run it in the console and read the full traceback if it fails. Confirm the file path so an old tab is not being executed.
- 02
Inspect variables and plots
Create a small array or table and a simple figure, then compare the variable explorer and plot pane with the expected values.
- 03
Record the environment
Export the dependency list and data assumptions after the test works. Install new packages into the same interpreter and restart the kernel.
Usage tips
- Check the current interpreter before responding to a missing-module error; reinstalling into another Python will not fix the active console.
- Large datasets should be sampled before expanding every variable, because the explorer can consume considerable memory.
- Rebuild a dedicated environment when upgrades create conflicts instead of repeatedly overwriting a shared base environment.
Troubleshooting and uninstall
Why does ModuleNotFoundError remain after installing a package?
Compare the package installation path with the Python path reported by the IPython console. Install into that interpreter, restart the kernel and run the import again.
Why will Spyder not start after an environment update?
Try a clean or reset configuration, then inspect Qt and environment dependencies. A fresh dedicated environment helps distinguish a package conflict from a project issue.
- Export code and environment informationSave scripts, data definitions, dependency files and any interpreter selection notes before removing Spyder.
- Remove the selected installationUninstall the standalone app or delete the dedicated environment through its package manager, keeping project data and backups separate.
Frequently asked questions
Can the standalone Spyder installer use every package in my existing environment?
It has its own environment. To use packages from another environment, configure a supported external interpreter and verify the selected path.
Why is a dedicated environment preferable for Spyder projects?
Spyder, Qt and scientific packages have dependency constraints. A dedicated environment is easier to export, rebuild and diagnose than a shared base environment.
Does the variable explorer replace a data validation workflow?
No. It is useful for inspection, but scripts should still validate types, shapes, missing values and output files with repeatable checks.