Issue 41468: IDLE: "Unrecoverable server exiting" message

How to solve unrecoverable server exiting in IDLE

To help us to reproduce and understand the issue, please could you give us 1) a more detailed explanation of the problem you are facing and 2) steps to reproduce the issue (maybe providing a minimal code example if that is the cause). Is this a bug with IDLE, though, as you say "solve" (which I interpret to mean you want help with your code) in which case it may be better suited to Stack Overflow?

Start IDLE in a Terminal/Command Prompt window with `python -m idlelib`, where 'python` is whatever runs your most recent 3.x python.  Then see if an error message shows up after IDLE exits.

One should never see this message.  As far as I remember, I have seen it only once in the last several years.  It is intended to indicate a 'random' non-reproducible glitch in the communication machinery connecting the IDLE GUI process and the user code execution process.  The most likely solution is to retry what you were doing.  A report should only be made is the error is reproducible. "Unrecoverable, server exiting" is meant to convey this, but the meaning should be explained in the message.  So I consider this a doc improvement issue.

If you report a repeatable failure, then we can look into that.

Dear Sir,

I got the solution. Thanks

On Tue, 4 Aug 2020, 16:55 Terry J. Reedy, <report@bugs.python.org> wrote:

>
> Terry J. Reedy <tjreedy@udel.edu> added the comment:
>
> One should never see this message.  As far as I remember, I have seen it
> only once in the last several years.  It is intended to indicate a 'random'
> non-reproducible glitch in the communication machinery connecting the IDLE
> GUI process and the user code execution process.  The most likely solution
> is to retry what you were doing.  A report should only be made is the error
> is reproducible. "Unrecoverable, server exiting" is meant to convey this,
> but the meaning should be explained in the message.  So I consider this a
> doc improvement issue.
>
> If you report a repeatable failure, then we can look into that.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue41468>
> _______________________________________
>

New changeset f2e161c27964a59bc5ab20d96f87ba5862c6222d by Terry Jan Reedy in branch 'master':
bpo-41468: Improve and test IDLE run error exit  (GH-21798)
https://github.com/python/cpython/commit/f2e161c27964a59bc5ab20d96f87ba5862c6222d

New changeset a9fa66377fbd9ea2fca1483345a8c27d1b32d5b4 by Miss Islington (bot) in branch '3.9':
bpo-41468: Improve and test IDLE run error exit  (GH-21798)
https://github.com/python/cpython/commit/a9fa66377fbd9ea2fca1483345a8c27d1b32d5b4

New changeset 61f23cb62d6bdd72b61fc36abf4c1492493d71af by Miss Islington (bot) in branch '3.8':
bpo-41468: Improve and test IDLE run error exit  (GH-21798)
https://github.com/python/cpython/commit/61f23cb62d6bdd72b61fc36abf4c1492493d71af

test_error() of test_idle fails when it's run twice in a row: bpo-41514 "test_idle: test_error() failed on aarch64 RHEL8 Refleaks 3.8".

Test error fixed on issue 41514.

Got it, thanks!

On Mon, 10 Aug 2020, 19:26 Terry J. Reedy, <report@bugs.python.org> wrote:

>
> Terry J. Reedy <tjreedy@udel.edu> added the comment:
>
> Test error fixed on issue 41514.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue41468>
> _______________________________________
>