View Single Post
Old 12-13-2014, 10:29 AM   #2
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi turbulent,
I think this is an artifact of python 2.7, that keeps its internal search paths as bytestrings, not full unicode. The launcher itself is full unicode. Being marked as unequal is the safest path forward and should not hurt anything. If the plugin actually started then this warning can be safely ignored. I will include a work around for this for python 2.7 in the next release to prevent the warning.

Thank you for your bug report!

KevinH

Quote:
Originally Posted by turbulent View Post
When running a Sigil plugin, if the current path contains non-ASCII character, the plugin runner dialog will display the message:

C:\Program Files\Sigil\plugin_launchers\\python\launcher.py:2 43: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if script_home not in sys.path:

The message is displayed only when the plugin is running. When the plugin finishes running, the message will be replaced by the output of plugin.
KevinH is offline   Reply With Quote