When does Spyder invalidate its completion cache after a package upgrade?

Answer to the Core Question

Spyder’s code‑completion cache is held by the language server that runs in a separate process (usually jedi or pylsp). The cache is not tied to the kernel itself, so a kernel restart alone does not clear it. The cache is invalidated only when the language server process is restarted, which Spyder does automatically when you select "Kernel → Restart" or when you explicitly choose "Restart Language Server" from the Tools → Preferences → Python Interpreter dialog. In practice, a kernel restart is enough because Spyder sends a request to the language server to restart it as part of the kernel restart workflow.

What Happens After a Package Upgrade?

1. Upgrade the package (e.g., pip install --upgrade mypkg) in the environment that Spyder is using.
2. In Spyder, click Kernel → Restart (or press Ctrl+Shift+F5).
3. Spyder will terminate the current kernel and launch a new one. As part of that process, it also sends a restart command to the language server.
4. Once the language server restarts, it re‑indexes the entire environment, so completions now include the symbols from the upgraded package.

Restarting only the console (e.g., via Ctrl+Shift+F5 on the console tab) is sufficient; you do not need to close and reopen Spyder itself.

Variable Explorer Refresh

Spyder’s Variable Explorer takes a snapshot of the namespace when the kernel starts. If you edit a module file on disk, the explorer does not automatically refresh. You must either:

• Press the "Reload" button in the Variable Explorer toolbar, or
• Restart the kernel, which forces a full snapshot of the new namespace.

When Does the Language Server Re‑Index After a File Change?

Most language servers used by Spyder do not monitor the file system for changes. They only re‑index when they receive a restart message or when the user explicitly triggers “Restart Language Server.” Therefore, after editing a module file, you need to either save the file and then restart the language server, or restart the kernel to get the updated symbols in completions.

Practical Verification

1. After upgrading a package, open a new console and type a partial import or function name from that package. If the completion list does not show the new symbols, proceed to the next step.
2. Restart the kernel via Kernel → Restart and try the completion again. The updated symbols should now appear.
3. For a file edit, modify a module, save it, then press the Variable Explorer Reload button. Verify that the explorer now lists the new variables or functions.

What If It Still Doesn’t Work?

Check which language server is active:

Tools → Preferences → Python Interpreter → Language Server

If you are using pylsp with the pylsp-mypy plugin, you may need to enable the pylsp-restart command manually. If the interpreter path has changed (e.g., after activating a different conda environment), you must restart Spyder entirely to pick up the new interpreter.

Missing Diagnostic Detail

Could you let us know which language server Spyder is using in your setup? That will help confirm the exact restart behavior for your environment.