Spyder Debug Again: Resource Temporarily Unavailable

Basic First Help¶

These suggestions, while more of a shotgun arroyo, tend to fix the majority of reported problems just on their own.

Recommended troubleshooting steps¶

1. Restart Spyder, and try what you were doing before again.

2. Upgrade Spyder to the latest release, and you might find your issue is resolved (forth with new features, enhancements, and other issues fixes). Minor releases come up out every couple months, so unless yous've updated recently, there is a good chance your version isn't the latest. You can discover out with the Check for updates command under the Help menu.

   

   To perform the update with Conda (strongly recommended), from your terminal (or Anaconda Prompt on Windows) run:

                     conda update anaconda conda update spyder                

3. Update Spyder's dependencies and environment, either by installing the latest version of your distribution (eastward.grand. the recommended Anaconda), or with the relevant "update all" command in your terminal (or Anaconda Prompt on Windows). To get the latest stable version of everything using Conda, you lot tin run:

                     conda update qt pyqt spyder-kernels ipython ipykernel jupyter_client jupyter_core pyzmq                

4. Restart your car, in case the trouble lies with a lingering process or another such issue.

5. Restore Spyder's config files to their defaults, which solves a huge diverseness of Spyder issues. From your last (or Anaconda Prompt on Windows), run:

   Note

   This will reset your preferences, as well as any custom keyboard shortcuts or syntax highlighting schemes. If y'all particularly care almost any of those, you should brand a copy of the .spyder-py3 folder in your user home directory ( C:/Users/YOUR_USERNAME on Windows, /Users/YOUR_USERNAME on macOS, or /domicile/YOUR_USERNAME on Linux), and restore it afterwards if this doesn't solve the problem.

6. Effort installing Spyder into a new Conda environment (recommended) or virtualenv / venv , and see if the issue reoccurs.

In your system terminal (or Anaconda Prompt on Windows), run the following commands to create an a fresh, make clean environment and start Spyder in it:

              conda create -n spyder-env spyder -y conda activate spyder-env spyder            

If this fixes the issue, the problem was probable due to another package installed on your organization, peculiarly if washed with pip, which can cause many problems and should be avoided if at all possible.

1. Spotter our video on solving and fugitive issues with pip, Conda and Conda-Forge, and follow its instructions.

Reinstalling Spyder¶

If none of the previous steps solve your issue, yous should practice a total uninstall of Spyder by whatever ways you originally installed it.

For Anaconda, follow all the steps under Option B in the Anaconda uninstall guide, delete the Anaconda directory wherever it was originally installed, and (on Windows) remove the %appdata%/python directory if it exists.

Then, practice a make clean install of the latest version of the Anaconda distribution which is how we recommend you install Spyder and keep it upward to date.

Important

While you are welcome to get Spyder working on your own by ane of the many other means we offer, we are only able to provide individual back up for install-related issues for users of the Anaconda distribution. In particular, pip installation, while doable, is just really for experts, every bit in that location are many pitfalls involved and different issues specific to your setup, which is why we recommend using Conda whenever possible. For further information, please visit our Installation Guide.

Isolating problems¶

If you become an fault while running a specific line, cake, or script/program, it may non be an issue with Spyder, but rather something lower down in the packages it depends on. Effort running it in the following in guild if and until it starts working as you expect. If you manage to isolate the bug, report it to the last 1 it doesn't work in.

1. Spyder itself, of course! Brand sure you tin can reproduce the error later on closing and reopening information technology, if possible.

2. A bare QtConsole instance, e.m. launched from Anaconda navigator or from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux) with jupyter qtconsole .

   

   QtConsole is the GUI console backend Spyder depends on to run its lawmaking, then most bug involving Spyder's :doc`ipythonconsole` are actually something with QtConsole instead, and can be reported to their event tracker.

3. An IPython command line shell, launched with e.thou. ipython from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). Reproducible bugs can exist reported to their Github page, though make sure to read their guidelines and docs showtime.

4. A standard Python interpreter, either run as a script file with python path/to/your/file.py or launched interactively with python from your Anaconda Prompt/Terminal/control line (Windows/Mac/Linux). While it is not impossible that y'all've found Python bug, it is much more likely to be an result with the code itself or a packet you are using, so your all-time sources are the Python docs and the other resources listed to a higher place.

Tip

If the problem reoccurs in a similar or identical way with any of these methods (other than only Spyder itself), and so it is most certainly not an event with Spyder, and would be all-time handled elsewhere. As we ordinarily aren't able to do much about issues non related to Spyder, a forum like Stack Overflow or the relevant package's docs is a much better place to get assistance or study the issue.

See the Calling for Help section for other places to look for information and assistance.

Debugging and patching¶

If you know your manner around Python, you lot can often diagnose and even fix Spyder problems yourself, since the IDE is written in the same language you utilise in it. You can explore the mistake letters y'all're receiving and Spyder's inner workings with the Internal Panel, available under the menu particular .

For more detailed debug output, start Spyder from the command line (Anaconda Prompt on Windows) with spyder --debug-info verbose .

Even if you lot don't manage to fix the problem yourself, this output can be very helpful in aiding us to quickly narrow downward and solve your issue for you.

kaypirclue.blogspot.com

Source: https://docs.spyder-ide.org/4/troubleshooting/basic-first-aid.html

Share this post