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

5.1.2 Mac installer broken? #16336

Closed
gctwnl opened this issue Sep 2, 2021 · 11 comments · Fixed by #16337
Closed

5.1.2 Mac installer broken? #16336

gctwnl opened this issue Sep 2, 2021 · 11 comments · Fixed by #16337

Comments

@gctwnl
Copy link

gctwnl commented Sep 2, 2021

What steps will reproduce the problem?

I installed the update (my first update after installing and working with Spyder for the last 2 days). In the update, the kernel will not load (macOS Catalina):

NotADirectoryError: [Errno 20] Not a directory: '/Applications/Spyder.app/Contents/Resources/lib/python39.zip/debugpy/_vendored'

@ccordoba12
Copy link
Member

Hey @gctwnl, thanks for reporting. That's a problem with the Mac installer only.

@mrclary, could you take a look at this one?

@ccordoba12 ccordoba12 changed the title Spyder 5.1.2 broken? 5.1.2 Mac installer broken? Sep 2, 2021
@dkmj
Copy link

dkmj commented Sep 2, 2021

installs fine but fails 'cannot load kernel'.

@mrclary
Copy link
Contributor

mrclary commented Sep 2, 2021

PR #16337 should fix the issue. Note that this only affects IPython consoles that use the internal (same as Spyder) interpreter. External interpreters are not affected.

@mrclary
Copy link
Contributor

mrclary commented Sep 2, 2021

Your options are: (a) use an external interpreter until 5.1.3 is released or (b) use the artifact from the pull request.

@mrclary
Copy link
Contributor

mrclary commented Sep 2, 2021

For documentation, the full traceback:

Traceback (most recent call last):
File "runpy.pyc", line 197, in _run_module_as_main
File "runpy.pyc", line 87, in _run_code
File "/Users/rclary/Applications/Spyder.app/Contents/Resources/lib/python3.9/spyder_kernels/console/__main__.py", line 23, in 
start.main()
File "/Users/rclary/Applications/Spyder.app/Contents/Resources/lib/python3.9/spyder_kernels/console/start.py", line 282, in main
from ipykernel.kernelapp import IPKernelApp
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File "ipykernel/kernelapp.pyc", line 42, in 
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File "ipykernel/ipkernel.pyc", line 20, in 
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File "ipykernel/debugger.pyc", line 17, in 
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File "debugpy/server/__init__.pyc", line 9, in 
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 627, in _load_backward_compatible
File "", line 259, in load_module
File "debugpy/_vendored/__init__.pyc", line 18, in 
NotADirectoryError: [Errno 20] Not a directory: '/Users/rclary/Applications/Spyder.app/Contents/Resources/lib/python39.zip/debugpy/_vendored'

@ccordoba12
Copy link
Member

Thanks for your help @mrclary! I'll wait a couple of days to see if other major problems appear, otherwise I'll release 5.1.3 with your fix.

However, we should find a way to automatically test our installers to avoid this problem in the future.

@mrclary
Copy link
Contributor

mrclary commented Sep 2, 2021

However, we should find a way to automatically test our installers to avoid this problem in the future.

See #14138.
I'd love to figure out a way to run our unit tests inside our macOS application, but I don't know how to do that and it may not be possible.
Another option would be to have a separate set of unit tests specifically for the macOS application, although I don't know how to accomplish that either...
In the short term, probably the best thing is to just download the latest artifact, just prior to release, and perform a cursory verification (does it launch? is there any obvious issues?).

@IvanLiuTW

This comment has been minimized.

@IvanLiuTW
Copy link

Thanks for taking a look of my problem.

@ccordoba12
Copy link
Member

@IvanLiuTW, please open a new issue about your problem because it's different from this one.

@IvanLiuTW
Copy link

ok, got it. Thanks for reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants