View Single Post
Old 11-16-2023, 05:39 AM   #23
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,735
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
That environment variable is only relevant when building PySide6.

I've not had much experience with a Sigil plugin Python environment that includes packages installed to a user site directory instead of the system one. Can you show me what the test p!gain shows for sys.path locations? It should be some of the very first output when running the testplugin.

The fact that Debian/Ubuntu doesn't yet supply their own PySide6 packages (to be installed via apt-get) is unfortunate. Problems like yours are not likely to go away until they do.

One quick thing to try is to skip the sigil launch script in /usr/local/bin and launch sigil directly from a command prompt using:

/usr/local/lib/sigil/sigil

If Sigil starts ok, try running the test plugin again.

Last edited by DiapDealer; 11-16-2023 at 05:59 AM.
DiapDealer is offline   Reply With Quote