-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Failure to run on MacOSX (underlying qt problem?) #134
Comments
Please run
That should fix your error. |
Sadly, it doesn't:
|
Ok, I don't know what's happening in your case then. Could you try with other Python versions (3.9, 3.8)? Perhaps it's an issue with Python 3.10. |
Same result with 3.8:
|
It works on my M1, but I realize you're using Intel Mac...
|
btw I noticed something odd: In my fresh, conda-forge-only env, I see
same as in OP's env. But why would
|
Thanks for answering the call for testing @leofang. Glad it works on M1. I'm still puzzle why it fails on Intel Mac. (It also worked in my tests on Windows and Linux). BTW, the pypi label in the listing is an old bug that still eludes conda devs but it is "mostly harmless." |
This is odd because we haven't received issues about this problem in our main issue tracker. @mrclary, do you have an Intel Mac to test this? |
Unfortunately, I only have the following combinations at present:
So I cannot test 12.4 on Intel. I may be able to test this in the near future, however, when my company's IT allows me to update to Monterey. |
This looks like a problem with Qtwebengine compilation and packaging. icudtl.dat provides support for International Components for Unicode (ICU). It is the Chromium version of ICU, which is not needed if Qt WebEngine was configured to use the system ICU. The error messages show "Resources" not being found after a search, followed by halting on "Couldn't mmap icu data file". |
I now have Chrome running--it doesn't make a difference. Nevertheless, the error messages point to a problem with Resource configuration and packaging. |
conda-forge/qt-webengine-feedstock@7edb14f |
@efiring, could you try with older qt-main and webengine builds to see if the error is not present? |
Only 5.15.4 builds are available. Do you mean try the earliest of these? |
Using
to get the earliest 5.15.4 builds, I get the same error. |
@ccordoba12 I'm still in Catalina |
I can make environment in which Spyder works on my machine with:
The only terminal message when running it is
The package list is
|
On 12.3.1 I get:
And Spyder works fine. I'll install the update to 12.4 now and restart... |
I get the same message after launching spyder on I tried using spyder in both conda environments suggested above: Upon launching spyder, both environments produce a segmentation fault: I have also tried creating many other environments with different versions of Python, to no avail. So far, I can only run it from a bare base environment, with the message: Note that I have the Brave browser installed, which is built on Chrome. It doesn't matter whether Brave is open or not, spyder crashes in any non-base environment. |
@ccordoba12, can we close this issue as stale? |
This is still a problem that affects some users to this day and I don't know how to solve it. It seems the trick that did it before (see #134 (comment)), fails to fix it now. |
Solution to issue cannot be found in the documentation.
Issue
Building Spyder in a minimal environment on a Macbook Pro (Intel), Macosx 12.4, it fails to run:
This is prompted by problems with Qt in more complex contexts; I am using Spyder as a self-contained way to test the PyQt and Qt stack for basic functionality.
The problem here is not encountered universally; another Matplotlib developer performed the same test, with no failure. I don't know what environment he was testing.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: