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 culler
Recipients culler, serhiy.storchaka, terry.reedy
Date 2017-05-12.22:41:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494628916.29.0.143962831956.issue30310@psf.upfronthosting.co.za>
In-reply-to
Content
The name of a Tk font family is a byte sequence obtained from the operating system.  But, this being Python 2.7, there is no distinction between the str type and the bytes type.  The byte sequence is definitely not ascii encoded on a Japanese Windows system.  It is a utf8-encoded byte string.  This is why I called v.decode('utf8') in my patch.  Note that this bug does not occur with Python 3.6.

Terry, I understand that text is better and I hope I never have to resort to an image again.  Since I don't speak Japanese myself, even setting up a Japanese Windows VM for testing was pretty challenging for me.  I was able to take a screenshot without having to translate any Japanese menus, so I took that shortcut.  Sorry about that.

This report was indeed triggered by a real "crash" in your sense.  It occurred in a GUI application bundled with pyinstaller.  Any unhandled exception in a pyinstaller app results in termination of the process and posts a Windows error message box saying 'Failed to execute script XXX'.  For the report, however, I was isolating the underlying unhandled exception in Font.copy() that had caused the real crash of the GUI application.
History
Date User Action Args
2017-05-12 22:41:56cullersetrecipients: + culler, terry.reedy, serhiy.storchaka
2017-05-12 22:41:56cullersetmessageid: <1494628916.29.0.143962831956.issue30310@psf.upfronthosting.co.za>
2017-05-12 22:41:56cullerlinkissue30310 messages
2017-05-12 22:41:56cullercreate