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.
`flush_std` is spamming Spyder-kernels
See original GitHub issueProblem Description
There is a flush_std message sent to the kernel every second, preventing the kernel from going to sleep. I think given that this solves a minor issue, only flushing after the execution is done would be sufficient. I worry that this behaviour negatively impacts spyder energy performances.
The alternatives are:
- only flush after execution
- poll during execution every X seconds
I would be in favour of the first approach, but what do you think @spyder-ide/core-developers ?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Common Illnesses — Spyder 5 documentation
If you receive the message An error occurred while starting the kernel in the IPython Console, Spyder was unable to launch a new...
Read more >D12740 Update python-spyder-kernels to 2.2.1 - Solus
IOStream.flush timed out message shown after every evaluation · Issues handling Matplotlib backend settings · Namespace issues · Shapely 1.8 and ...
Read more >googlelist.counts - Massachusetts Institute of Technology
... 147679720 535 against 147263356 536 standard 147186626 537 tax 146917186 ... 2574 strategic 30931502 2575 judge 30908029 2576 spam 30895005 2577 acid ......
Read more >7.16.1 PDF - IPython Documentation
An enhanced interactive Python shell. • A decoupled two-process communication model, which allows for multiple clients to connect to a ...
Read more >Release notes | Dataproc Serverless Documentation
Upgraded versions of Python packages: nbdime 2.1 -> 3.0 , pyarrow 2.0 -> 3.0 , spyder 4.2 -> 5.0 , spyder-kernels 1.10 ->...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The idea would be to flush the underlying cout and cert at the end of every commands instead of every second like now
It is possible some things will not be printed if this is changed unless a command is run. Not the python code but c code could be writing to the underlying cout instead of using the sockets