View Single Post
Old 01-07-2021, 11:39 AM   #27
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,928
Karma: 6361444
Join Date: Nov 2009
Device: many
Going back to the original python error messages.

Because of a lack of a other working hypotheses, let's assume the original python error messages are somehow valid.

Is there a way to on Windows to test Sigil's embedded python interpreter directly from the command line?

If so I would love to fire it up and test the following:

import unicodedata

Just to be sure it can be imported and exists. If so, we can modify sigil_bs4 to import unicodedata first thing in its __init__.py code and then see what happens.
KevinH is offline   Reply With Quote