Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spyder on macOS latest apparently never terminates shell process after closing main window

See original GitHub issue

Spyder is installed via MiniConda. It says everything is up to date. I launch it from a command line shell, with, simply, “Spyder”. If I immediately choose “Quit” the main window closes, but the process in the shell sticks around and has to be killed violently. I’ve followed the hints in the FAQ and this is not solved. Is this a known bug?

p.s. I see this when I run it but I think I saw somewhere that it is benign:

[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0

Issue Analytics

State:
Created 5 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

pitosalascommented, Apr 24, 2018

Sorry about the lack of the image. But anyway, I spoke too soon… Spyder did in the end exit, it was just not immediately. I think your first fix did it.

Do you have a use for the console log? Here it is. screen shot 2018-04-23 at 8 32 09 pm

If you want me to do the additional steps above I am glad to do so.

Spyder is a really nice product for me. I’ve tried each of the alternatives and I’ve come back to Spyder.

0reactions

CAM-Gerlachcommented, Apr 24, 2018

Spyder did in the end exit, it was just not immediately.

Yeah, it can take anywhere from a second or two to ten+ seconds in my experience, depending on the version, how it was installed, the performance of your machine, etc.

I think your first fix did it.

Which would that be?

Do you have a use for the console log? Here it is.

Oh, I thought you meant the log from Spyder, haha. In that case, not really…it just shows you updated what Carlos asked you to.

If you want me to do the additional steps above I am glad to do so.

No need; from what you’ve said everything is behaving as expected.

Spyder is a really nice product for me. I’ve tried each of the alternatives and I’ve come back to Spyder.

Thanks! We really appreciate your support, particularly given we are now relying on our users and donations for funding after our institutional support ended. Glad you like it!

Top Results From Across the Web

macos - Ways to invoke python and Spyder on OSX

To make spyder callable from Spotlight or Finder: Locate where your spyder executable is by running in Terminal: which spyder.

Avoiding [process completed] prompt after terminal script ends ...

In Terminal Preferences, in Profiles pane select the Profile you use (should say "default" under it's name), select sub-pane Shell and ...

In Python, when I run my program, it closes right away ... - Quora

Your terminal window (aka command shell window or console window) is closing when your console application terminates. That's how it's supposed to work, ......

Curses Programming with Python — Python 3.11.1 ...

This document describes how to use the curses extension module to control text-mode displays. What is curses?¶. The curses library supplies a terminal- ......

Interacting With Python

The Python interpreter (REPL) running inside a terminal window. Alternatively, you can open a terminal window and run the interpreter from the command...