Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot launch Spyder after updating to macOS 11 Big Sur, please help. #14222

Closed
jzzhou715 opened this issue Nov 13, 2020 · 64 comments · Fixed by #14256
Closed

Cannot launch Spyder after updating to macOS 11 Big Sur, please help. #14222

jzzhou715 opened this issue Nov 13, 2020 · 64 comments · Fixed by #14256
Assignees
Milestone

Comments

@jzzhou715
Copy link

After updating my OS to macOS 11 today, I cannot seem to launch Spyder. I tried reinstall everything even reconstruct the python framework. Still does not work. When I run the following command in my terminal, the Spyder icon pops up but it stops there, nothing is being loaded and the Spyder window do not show up.

Last login: Fri Nov 13 16:07:21 on ttys000
Zhou@Jizhous-iMac ~ % Spyder/bin/spyder

I am not using Anaconda, I installed Spyder using pip.

How can I fix this? Thanks.

@gvizkelethy
Copy link

Same here. On all three of my Macs the same thing happened. After upgrading to Big Sur Spyder starts but the IDE never shows up. When I click on the Spyder icon in the dock it does not switch to Python in the title bar as before but stays in the terminal. I reinstalled my virtual environment, 3.9 then back to 3.8 it is the same. Any idea?

@adamgarbo
Copy link

I'm also experiencing this issue when attempting to launch Spyder using Anaconda Navigator. After upgrading to Big Sur, the Spyder icon will appear in the Dock, but never load.

When attempting to load Spyder from the Terminal, it appears to never make it past line 3 of: /Users/adam/opt/anaconda3/envs/icebergdrift/bin/pythonw

#!/bin/bash
export PYTHONEXECUTABLE=/Users/adam/opt/anaconda3/envs/icebergdrift/bin/python
/Users/adam/opt/anaconda3/envs/icebergdrift/python.app/Contents/MacOS/python "$@"

Additionally, spyder --debug-info verbose --debug-output file does not produce any debugging information to the Terminal.

Keen to learn what the cause and/or solution is!

@gvizkelethy
Copy link

gvizkelethy commented Nov 14, 2020 via email

@jzzhou715 jzzhou715 reopened this Nov 14, 2020
@wenlzhang
Copy link

wenlzhang commented Nov 14, 2020

The same issue happened to me after updating to Big Sur.

I don't know why, but I somehow resolved this issue by following the method as indicated in the following issue:
#9951

More specifically, I tried the following steps:

  1. Re-create the environment (I am using miniconda) for Spyder
  2. Re-install Spyder in the new conda environment
  3. Un-install the python.app package within the Spyder environment, if it already exists
  4. Re-install the python.app package as follows:
    • conda install -f python.app
  5. Launch Spyder as usual

Although I am able to launch and use Spyder now, there are some latency issues, as reported in the following issue:
#14218

@jzzhou715
Copy link
Author

I tried everything you said, still no luck.

@bendermh
Copy link

I had successfully installed Spyder in Big Sur without Anaconda. I installed the python 3.9 from homebrew and made it default, then I installed Spyder via pip, it works fine, with no delays or writing.
spyder

@ccordoba12
Copy link
Member

@bendermh, thanks for digging deeper into this!

Could the others download our macOS appilcation and see if it works for you? According to what @bendermh posted above, it should.

@adamgarbo
Copy link

Hi @ccordoba12,

I attempted to install Spyder using the macOS .dmg file you provided but the program doesn't load. The icon appears in the Dock, but stops responding. Would having Anaconda installed cause a conflict with running Spyder on its own?

Cheers,
Adam

@wenlzhang
Copy link

@ccordoba12 It's the same for me. The .dmg installs Spyder successfully, but Spyder would not load after clicking the Spyder icon.

@wiktornis
Copy link

@ccordoba12 It's the same for me. The .dmg installs Spyder successfully, but Spyder would not load after clicking the Spyder icon.

Same problem here

@rsxy09
Copy link

rsxy09 commented Nov 16, 2020

@ccordoba12 It's the same for me. The .dmg installs Spyder successfully, but Spyder would not load after clicking the Spyder icon.

same here

@impact27
Copy link
Contributor

impact27 commented Nov 16, 2020

I'll try to update to Big Sur this evening. In the meantime, could someone that feels confortable doing that try cloning the repo (see instructions at https://github.com/spyder-ide/spyder/blob/master/CONTRIBUTING.md#setting-up-a-development-environment), and run spyder with python3 bootstrap.py (or python) to see if an error is shown in a terminal?

@almarklein
Copy link

Pyzo users on Big Sur are experiencing the same issue. @ccordoba12 I also ran a new CI build this morning using Python 3.9 and the latest PyInstaller, but this seems not to fix it, which seems similar to the experience with Spyder, I think. Let's keep each-other informed :)

@wenlzhang
Copy link

I'll try to update to Big Sur this evening. In the meantime, could someone that feels confortable doing that try cloning the repo (see instructions at https://github.com/spyder-ide/spyder/blob/master/CONTRIBUTING.md#setting-up-a-development-environment), and run spyder with python3 bootstrap.py (or python) to see if an error is shown in a terminal?

@impact27 I tried the method you suggested on the branch 4.x, and the latency issue was not resolved. Also, I got the following output in the terminal:

Executing Spyder from source checkout
*. Patched sys.path with /.../spyder
*. Patched sys.path with /.../spyder/external-deps/spyder-kernels
*. Patched sys.path with /.../spyder/external-deps/python-language-server
*. Installing PyLS locally
*. PyQt5 is detected, selecting
*. Imported Spyder 4.3.0.dev0 - Revision 9344ec517, Branch: 4.x
    [Python 3.8.5 64bits, Qt 5.9.7, PyQt5 5.9.2 on Darwin]
*. Running Spyder
Bootstrap completed in 00:00:09.0267

@impact27
Copy link
Contributor

@wenlzhang thanks! That means that Spyder did launch? There might be two different problems:

  • Spyder not launching
  • Spyder being slow

@wenlzhang
Copy link

@wenlzhang thanks! That means that Spyder did launch? There might be two different problems:

  • Spyder not launching
  • Spyder being slow

@impact27 I should have been more clear in the description... Spyder launches successfully but it has a very slow response.

@ccordoba12
Copy link
Member

ccordoba12 commented Nov 16, 2020

@wenlzhang, please run the following commands to see see if that helps:

  • conda create -n pip-env python=3.8
  • conda activate pip-env
  • cd /path/to/your/spyder/clone
  • pip install -e .
  • pip uninstall spyder
  • python bootstrap.py

If that still shows slowness, please run

  • pip install -U pyqt5
  • pip install -U pyqtwebengine
  • python3 bootstrap.py

@ccordoba12
Copy link
Member

Pyzo users on Big Sur are experiencing the same issue. @ccordoba12 I also ran a new CI build this morning using Python 3.9 and the latest PyInstaller, but this seems not to fix it, which seems similar to the experience with Spyder, I think. Let's keep each-other informed :)

Hey @almarklein! Sure, we should keep in touch. I think the problem is because Anaconda ships with a very old Qt version. Things should be fixed with Qt 5.12 (our current pip requirement) or 5.15 (hopefully).

@wenlzhang
Copy link

wenlzhang commented Nov 16, 2020

@ccordoba12 Neither of the two methods worked. Spyder would not launch this time, and I had to Force Quit Spyder from the Dock.

With the first method, i.e. the following steps:

  • conda create -n pip-env python=3.8
  • conda activate pip-env
  • cd /path/to/your/spyder/clone
  • pip install -e .
  • pip uninstall spyder
  • python bootstrap.py

I got the following output in the terminal:

Executing Spyder from source checkout
*. Patched sys.path with /.../spyder
*. Patched sys.path with /.../spyder/external-deps/spyder-kernels
*. Patched sys.path with /.../spyder/external-deps/python-language-server
*. Removing previous PyLS local installation.
*. Installing PyLS locally
*. PyQt5 is detected, selecting
*. Imported Spyder 4.3.0.dev0 - Revision 9344ec517, Branch: 4.x
    [Python 3.8.5 64bits, Qt 5.12.10, PyQt5 5.12.3 on Darwin]
*. Running Spyder
Bootstrap completed in 00:00:00.9424

With the second method, i.e. by using the following commands:

  • pip install -U pyqt5
  • pip install -U pyqtwebengine
  • python3 bootstrap.py

I got the following output in the terminal:

Executing Spyder from source checkout
*. Patched sys.path with /.../spyder
*. Patched sys.path with /.../spyder/external-deps/spyder-kernels
*. Patched sys.path with /.../spyder/external-deps/python-language-server
*. Removing previous PyLS local installation.
*. Installing PyLS locally
*. PyQt5 is detected, selecting
*. Imported Spyder 4.3.0.dev0 - Revision 9344ec517, Branch: 4.x
    [Python 3.8.5 64bits, Qt 5.15.1, PyQt5 5.15.1 on Darwin]
*. Running Spyder
Bootstrap completed in 00:00:00.9155
The available OpenGL surface format was either not version 3.2 or higher or not a Core Profile.
Chromium on macOS will fall back to software rendering in this case.
Hardware acceleration and features such as WebGL will not be available.
qt.qpa.fonts: Populating font family aliases took 770 ms. Replace uses of missing font family "Quattrocento Sans" with one that exists to avoid this cost.

@ccordoba12
Copy link
Member

Spyder would not launch this time, and I had to Force Quit Spyder from the Dock.

Ok, thanks for trying. Could you post a screenshot of what you're seeing?

@wenlzhang
Copy link

wenlzhang commented Nov 16, 2020

@ccordoba12 Besides the terminal output described above, nothing else is special to me. The Spyder icon pops up in the Dock as follows, but Spyder does not launch. When I right click the Spyder icon in the Dock, it says that Application Not Responding.
Spyder

Also, python3 gives CPU usage of around 99% as can be seen from the Activity Monitor, and my MacBook starts to heat up.

@impact27
Copy link
Contributor

impact27 commented Nov 16, 2020

I updated and can't reproduce with :
Python 3.8.6 64-bit | Qt 5.12.9 | PyQt5 5.12.3 | Darwin 20.1.0
or:
Python 3.8.6 64-bit | Qt 5.15.1 | PyQt5 5.15.1 | Darwin 20.1.0

@ccordoba12
Copy link
Member

Great news @impact27! Two additional questions for you:

  • What about the reported slowness? Are you experiencing it too?
  • Could you try to debug our Mac app to understand why it's failing?

@impact27
Copy link
Contributor

impact27 commented Nov 17, 2020

The Mac app fails to start. I am not even sure it actually loads spyder code before blocking, so this could be PY2APP related. I will investigate further later.
This is where I see the process stalling:

``` 0 libobjc.A.dylib 0x00007fff201d65dd class_copyProtocolList + 46 1 com.apple.CoreFoundation 0x00007fff204204e0 __methodDescriptionForSelector + 74 2 com.apple.CoreFoundation 0x00007fff2043a5f4 -[NSObject(NSObject) methodSignatureForSelector:] + 30 3 libqcocoa.dylib 0x0000000124ef7b79 0x124ee3000 + 84857 4 libqcocoa.dylib 0x0000000124ef774d 0x124ee3000 + 83789 5 QtGui 0x000000011ae59f27 QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) + 1207 6 QtWidgets 0x000000011a7107ee 0x11a6f8000 + 100334 7 QtWidgets 0x000000011a714aa2 0x11a6f8000 + 117410 8 QtWidgets 0x000000011a7655c4 0x11a6f8000 + 447940 9 QtWidgets 0x000000011a762944 0x11a6f8000 + 436548 10 QtWidgets 0x000000011a70867d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269 11 QtWidgets 0x000000011a709a82 QApplication::notify(QObject*, QEvent*) + 594 12 QtWidgets.so 0x000000011a3933ca sipQApplication::notify(QObject*, QEvent*) + 234 13 QtCore 0x0000000119e49324 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 14 QtGui 0x000000011acd1115 QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 309 15 QtGui 0x000000011acaf0e3 bool QWindowSystemInterfacePrivate::handleWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 115 16 QtGui 0x000000011acb60c2 void QWindowSystemInterface::handleExposeEvent(QWindow*, QRegion const&) + 178 ```
0   libsystem_malloc.dylib        	0x00007fff201587cb tiny_malloc_should_clear + 62
1   libsystem_malloc.dylib        	0x00007fff20157793 szone_malloc_should_clear + 66
2   libsystem_malloc.dylib        	0x00007fff20170dfe _malloc_zone_malloc + 118
3   com.apple.CoreGraphics        	0x00007fff24f16625 CGGStackCreateWithGState + 20
4   com.apple.CoreGraphics        	0x00007fff24f16162 CGContextCreateWithDelegateAndInfo + 162
5   com.apple.AppKit              	0x00007fff22f0190e -[NSView lockFocusIfCanDraw] + 192
6   libqcocoa.dylib               	0x0000000124fa8063 0x124f94000 + 82019
7   QtGui                         	0x000000011af1cf27 QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) + 1207
8   QtWidgets                     	0x000000011a7d37ee 0x11a7bb000 + 100334
9   QtWidgets                     	0x000000011a7d7aa2 0x11a7bb000 + 117410
10  QtWidgets                     	0x000000011a8285c4 0x11a7bb000 + 447940
11  QtWidgets                     	0x000000011a825944 0x11a7bb000 + 436548
12  QtWidgets                     	0x000000011a7cb67d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
13  QtWidgets                     	0x000000011a7cca82 QApplication::notify(QObject*, QEvent*) + 594
14  QtWidgets.so                  	0x000000011a4563ca sipQApplication::notify(QObject*, QEvent*) + 234
15  QtCore                        	0x0000000119f0c324 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
16  QtGui                         	0x000000011ad94115 QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 309
17  QtGui                         	0x000000011ad720e3 bool QWindowSystemInterfacePrivate::handleWindowSystemEvent<QWindowSystemInterface::SynchronousDelivery>(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 115
18  QtGui                         	0x000000011ad790c2 void QWindowSystemInterface::handleExposeEvent<QWindowSystemInterface::SynchronousDelivery>(QWindow*, QRegion const&) + 178
0   libobjc.A.dylib               	0x00007fff201eb8db objc_object::sidetable_release(bool, bool) + 197
1   libobjc.A.dylib               	0x00007fff201ec39d AutoreleasePoolPage::releaseUntil(objc_object**) + 167
2   libobjc.A.dylib               	0x00007fff201cf33e objc_autoreleasePoolPop + 161
3   com.apple.CoreFoundation      	0x00007fff203e91e0 _CFAutoreleasePoolPop + 22
4   com.apple.Foundation          	0x00007fff21184e01 -[NSAutoreleasePool drain] + 129
5   QtCore                        	0x0000000119ef41e8 QMacAutoReleasePool::~QMacAutoReleasePool() + 40
6   libqcocoa.dylib               	0x000000012509f7a8 0x12508b000 + 83880
7   QtGui                         	0x000000011ae22f27 QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) + 1207
8   QtWidgets                     	0x000000011a6d97ee 0x11a6c1000 + 100334
9   QtWidgets                     	0x000000011a6ddaa2 0x11a6c1000 + 117410
10  QtWidgets                     	0x000000011a72e5c4 0x11a6c1000 + 447940
11  QtWidgets                     	0x000000011a72b944 0x11a6c1000 + 436548
12  QtWidgets                     	0x000000011a6d167d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
13  QtWidgets                     	0x000000011a6d2a82 QApplication::notify(QObject*, QEvent*) + 594
14  QtWidgets.so                  	0x000000011a35c3ca sipQApplication::notify(QObject*, QEvent*) + 234
15  QtCore                        	0x0000000119e12324 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
16  QtGui                         	0x000000011ac9a115 QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 309
17  QtGui                         	0x000000011ac780e3 bool QWindowSystemInterfacePrivate::handleWindowSystemEvent<QWindowSystemInterface::SynchronousDelivery>(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 115
18  QtGui                         	0x000000011ac7f0c2 void QWindowSystemInterface::handleExposeEvent<QWindowSystemInterface::SynchronousDelivery>(QWindow*, QRegion const&) + 178

@vancromy
Copy link

Just tried downloading the dmg and get the same issue as @wenlzhang. Spyder icon pops up and down on dock then gets marked as opened but no window ever appears and I have to Force Quite Spyder because it's not responding. I also have Spyder installed via conda and that still opens up fine on Big Sur :). Even with multiple environments and changing python interpreters. But when opening the conda version I am getting the very high latency on keystrokes as mentioned in #14218.

@impact27
Copy link
Contributor

impact27 commented Nov 18, 2020

I could use this technique to launch the macOS appilcation but it is a bit laggy (not as bad as with Qt 5.9): https://stackoverflow.com/questions/16184505/set-environment-variable-for-the-process-before-startup

You need to add to Spyder.app/Contents/Info.plist :

<key>LSEnvironment</key>
<dict>
    <key>QT_MAC_WANTS_LAYER</key>
    <string>1</string>
</dict>

Info.plist is cached, so it might not work directly. If that doesn't work, the solution is to kill and rebuild the cache:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed
my Info.plist now looks like:

``` LSEnvironment QT_MAC_WANTS_LAYER 1 CFBundleDevelopmentRegion English CFBundleDisplayName Spyder CFBundleDocumentTypes CFBundleTypeExtensions py pyw ipy pyx pxd pxi c h cc cpp cxx h hh hpp hxx cl f for f77 f90 f95 f2k f03 f08 pro m jl yaml yml patch diff rej bat cmd txt txt rst po pot nsi nsh scss css htm html xml js json ipynb enaml properties session ini inf reg cfg desktop md CFBundleTypeName Text File CFBundleTypeRole Editor CFBundleExecutable Spyder CFBundleIconFile spyder.icns CFBundleIdentifier org.spyder-ide CFBundleInfoDictionaryVersion 6.0 CFBundleName Spyder CFBundlePackageType APPL CFBundleShortVersionString 4.2.0 CFBundleSignature ???? CFBundleVersion 0.0.0 LSHasLocalizedDisplayName NSAppleScriptEnabled NSHumanReadableCopyright Copyright not specified NSMainNibFile MainMenu NSPrincipalClass NSApplication PyMainFileNames __boot__ PyOptions alias argv_emulation emulate_shell_environment no_chdir prefer_ppc site_packages use_faulthandler use_pythonpath verbose PyResourcePackages PyRuntimeLocations @executable_path/../Frameworks/Python.framework/Versions/3.8/Python PythonInfoDict PythonExecutable /usr/local/opt/python@3.8/bin/python3.8 PythonLongVersion 3.8.6 (default, Oct 8 2020, 14:06:32) [Clang 12.0.0 (clang-1200.0.32.2)] PythonShortVersion 3.8 py2app alias template app version 0.22 ```

@impact27

This comment has been minimized.

@wiktornis

This comment has been minimized.

@impact27
Copy link
Contributor

impact27 commented Nov 18, 2020

You probably didn't run it in the correct environment. You can just uninstall everything and try again. Let me update the instructions:
Installation:

conda create -n spyder-dev python=3
conda activate spyder-dev
pip install -U spyder

Run:

conda activate spyder-dev
export QT_MAC_WANTS_LAYER=1
spyder

@wiktornis
Copy link

wiktornis commented Nov 18, 2020

You probably didn't run it in the correct environment. You can just uninstall everything and try again. Let me update the instructions:
Installation:

conda create -n spyder-dev python=3
conda activate spyder-dev
pip install -U spyder

Run:

conda activate spyder-dev
export QT_MAC_WANTS_LAYER=1
spyder

It helped - thank you!

@jileltgen
Copy link

Thank you @impact27 ! Got the same issue. It worked fine for me.

@MarcosCarreira
Copy link

MarcosCarreira commented Nov 18, 2020

Thank you @impact27 ! When I first "upgraded" to Big Sur, Spyder 4.1.5 was running from Anaconda, but today it was not. I tried the direct install (Mac OS) but it was not working. I run just the lines:

pip install -U spyder
export QT_MAC_WANTS_LAYER=1
spyder

On my existing environment and it worked (launches 4.2.0), although the pip install means that Anaconda Navigator is not recognizing Spyder 4.2.0 and the app doesn't work.

Any long term solution?

Thanks

Marcos

@impact27
Copy link
Contributor

impact27 commented Nov 18, 2020

Any long term solution?

We can probably add QT_MAC_WANTS_LAYER=1 to spyder so you wouldn’t need to set it. To make conda work instead of pip however we probably need to wait for conda to update the Qt version they distribute.

The app can be updated however

@km5ar
Copy link

km5ar commented Nov 18, 2020

I download the Spyder app, when i try to open it, it shows as the picture below. Which is almost the same when i open annaconda, so far, i can only open jupyter lab through terminal, i try to call Spyder(Anaconda) from the terminal, it result the same thing as a try to open the Spyder app alone.

image

@almarklein
Copy link

I've made a new build for Pyzo that does QT_MAC_WANTS_LAYER=1 and multiple users have confirmed that it works. So I think this should be a viable solution for Spyder as well. Thanks folks!

@wenlzhang
Copy link

wenlzhang commented Nov 18, 2020

@km5ar The following two methods given above worked for me:

Method 1:

I could use this technique to launch the macOS appilcation but it is a bit laggy (not as bad as with Qt 5.9): https://stackoverflow.com/questions/16184505/set-environment-variable-for-the-process-before-startup

You need to add to Spyder.app/Contents/Info.plist :

<key>LSEnvironment</key>
<dict>
    <key>QT_MAC_WANTS_LAYER</key>
    <string>1</string>
</dict>

Info.plist is cached, so it might not work directly. If that doesn't work, the solution is to kill and rebuild the cache:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed
my Info.plist now looks like:

Method 2:

You probably didn't run it in the correct environment. You can just uninstall everything and try again. Let me update the instructions:
Installation:

conda create -n spyder-dev python=3
conda activate spyder-dev
pip install -U spyder

Run:

conda activate spyder-dev
export QT_MAC_WANTS_LAYER=1
spyder

@roryjbd
Copy link

roryjbd commented Nov 18, 2020

Hi all, I am experiencing this issue with spyder, but I also seem to be getting the exact same symptoms when I try to launch anaconda navigator (icon appears in dock but will not open). It seems like big sur has potentially caused a wider anaconda issue?

@MarcosCarreira
Copy link

I can use Navigator and JupyterLab, but not Spyder and Notebook.

@km5ar
Copy link

km5ar commented Nov 18, 2020

@km5ar The following two methods given above worked for me:

Method 1:

I could use this technique to launch the macOS appilcation but it is a bit laggy (not as bad as with Qt 5.9): https://stackoverflow.com/questions/16184505/set-environment-variable-for-the-process-before-startup
You need to add to Spyder.app/Contents/Info.plist :

<key>LSEnvironment</key>
<dict>
    <key>QT_MAC_WANTS_LAYER</key>
    <string>1</string>
</dict>

Info.plist is cached, so it might not work directly. If that doesn't work, the solution is to kill and rebuild the cache:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed
my Info.plist now looks like:

Method 2:

You probably didn't run it in the correct environment. You can just uninstall everything and try again. Let me update the instructions:
Installation:

conda create -n spyder-dev python=3
conda activate spyder-dev
pip install -U spyder

Run:

conda activate spyder-dev
export QT_MAC_WANTS_LAYER=1
spyder

thank you so much, this works for me!!!!!

@km5ar
Copy link

km5ar commented Nov 18, 2020

just wondering, now Spyder from Anaconda works for me,
but the Spyder app still doens't work, is there any method to solve that? I knew this is probably too much to ask.
image

@wenlzhang

This comment has been minimized.

@gvizkelethy

This comment has been minimized.

@ccordoba12

This comment has been minimized.

@ccordoba12

This comment has been minimized.

@ccordoba12
Copy link
Member

ccordoba12 commented Nov 19, 2020

Sorry guys but I'm going to lock this issue because it's starting to accumulate incorrect answers (some of which are very bad advice).

Bottom line is this:

  • Spyder will work with Big Sur in our next version (4.2.1), to be released in one month.
  • The workaround for now is described in the last comment on issue High typing latency in MacOS Big Sur #14218.
  • Our Mac app is going to be updated in 4.2.1 too to work with Big Sur. Please don't mess with it because it will defeat its purpose of providing a very stable way to deliver Spyder to users.
  • Additional issues about Big Sur will be closed and people will be pointed to issue High typing latency in MacOS Big Sur #14218 for the workaround.

Thanks for understanding.

@spyder-ide spyder-ide locked and limited conversation to collaborators Nov 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.