This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients serhiy.storchaka, terry.reedy
Date 2014-10-12.07:39:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499286.R7R8dPKtsE@raxxla>
In-reply-to <1413065880.69.0.0818621344041.issue22614@psf.upfronthosting.co.za>
Content
> In msg228954, Serhiy reported a new problem, which I an transferring to this
> new issue, with 2.7 and 3.4 but not 3.5.

I now can reproduce the issue on 3.5 too. But with Lib/test/test_decimal.py, not Lib/decimal.py. The difference between 3.4 and 3.5 is that Lib/decimal.py is large in 3.4, but it is tiny in 3.5.

I can easy reproduce this issue because my netbook is too slow. When I wait some time, and then close editor window, there is no traceback. This time is needed to colorize sources in editor window. May be you will reproduce this issue when open very large Python file and then quickly close editor window. If you have no such file, just concatenate large file with itself many times:

    cp Lib/test/test_decimal.py+Lib/test/test_decimal.py+Lib/test/test_decimal.py+Lib/test/test_decimal.py+Lib/test/test_decimal.py testfile.py

> What system? I do not reproduce on Win 7 with an Oct 9 build.

I believe you will reproduce with enough large file.

> When?  If the command line worked for 2.7 in Jan and fails now, when did it
> start failing?  If the command worked for 3.4 after the Feb patches and
> fails now, same question.

At least with 3.4.0 I don't see this traceback. May it is hidden by the 'can't invoke "bind" command' error.

> How? You did not state, but in a later message implied that the file opened
> in the editor and the problem only happened when you closed, as with the
> January report.  However, the traceback says that the problem occurred
> during initialization.  According to Find in Files, the only call to
> color_breakpoint_text is that one __init__ call.  I therefore do not
> understand your msg228957 comment "The code runs up to self.text.update()
> in restore_file_breaks() and runs further only after windows closing."

Sorry for my ugly English. I meant that the interpreter enters in self.text.update(), then hangs inside it and exits from it only when the windows is closed. I added print's before and after this statement and the print after the statement was not executed until I had closed the window.
History
Date User Action Args
2014-10-12 07:39:05serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy
2014-10-12 07:39:05serhiy.storchakalinkissue22614 messages
2014-10-12 07:39:04serhiy.storchakacreate