![]() ![]() It features a unique combination of the advanced editing, analysis, debugging and profiling functionality of a comprehensive development tool with the data exploration, interactive execution, deep inspection and beautiful visualization capabilities of a scientific package.\n Furthermore, Spyder offers built-in integration with many popular scientific packages, including NumPy, SciPy, Pandas, IPython, QtConsole, Matplotlib, SymPy, and more.\n Beyond its many built-in features, Spyder can be extended even further via third-party plugins.\n Spyder can also be used as a PyQt5 extension library, allowing you to build upon its functionality and embed its components, such as the interactive console or advanced editor, in your own software. Objc: Class RunLoopModeTracker is implemented in both /anaconda3/lib/python3.Spyder is a powerful scientific environment written in Python, for Python, and designed by and for scientists, engineers and data analysts. Xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun You can set this up via the following commands in the Anaconda prompt/Terminal/command line ![]() Now that Spyder 3.3.0's out (and Spyder 3.3.1, due out very soon, will improve it further), we have a much easier and better way to handle this situation: just install Spyder in its own environment, and then install just the spyder-kernels package in whatever environment(s) you want to use Spyder with (this can be different Anaconda envs, virtualenvs/venvs, or even a totally different Python install) and just point Spyder to the Python interpreter of whatever environment you want to use (under Tools -> Preferences -> Python interpreter -> Use the following Python interpreter). Other than that, the only real way I can immediatly think of to debug it further would be dig into the mainwindow.py file and put print()/debug statements or something at regular intervals between the last debug message you see ( Loading editor.) and the first you don't (usually Introspection Plugin Loaded: rope), to narrow down more precisely where the hang is Sorry to hear you're still having issues.īasically, the problem seems to be that Spyder is installed in the environment as other packages that depend on Qt4 or other versions of Qt5, which is a recipe for problems no matter what you're trying to do, as is using pip to do that which is likely to cause major issues down the line in the future. With regard to narrowing down what's actually going on-to confirm, you tried the advanced startup troubleshooting procedure discussed in the comments to issue #6023 that I brought up previously, running start.py and mainwindow.py (with set SPYDER_DEBUG=3 beforehand for extra info)? If there's anything there that's unclear, I can post a more detailed guide if anything will reveal what's going on, that will. Also, any significant system configuration changes between when it worked and when it didn't? A few other things to try, just in case: Try running Spyder as admin (through the shortcut or an elevated anaconda prompt) make sure you have no Spyder plugins installed, no spaces, special/non-ASCII characters, or funky permissions on your user/home and Anaconda directory path, try installing just Spyder into a new, fresh Python 3 Anaconda environment and starting it from the command line and Anaconda Navigator with that environment activated, and if you've installed for just you, try installing for all users or vice versa, and make sure Anaconda is installed to the default location for that. I'm honestly baffled at this one, and I'm almost out of the standard toolbox of troubleshooting fixes, and there appears to be no particular indication what's going on. Thanks again for following up, and really sorry you're still having issues. My machine is a simple Windows 10 Home.
0 Comments
Leave a Reply. |