Quote:
Originally Posted by darkbreath
Ah I see it. I didn't fully understand that part of the instructions at first, but I did some reading about pip afterward, and I see what it meant now.
When I tried to install the package, I ran into that PEP 668 error and realized that I could potentially break os Python packages if I proceeded. Is there another option such as maybe installing a version of Python in Conda or some other virtual environment, then pointing Sigil there?
|
Yes. If you have a virtual environment with all the necessary modules installed to it, you can point Sigil to the python binary in the virtual one in Sigil's preferences.
But since Ubuntu/Mint doesn't provide their own PySide6 package in their repos, there's very little chance that anything will break. I'm not a big fan of PEP 668, or it's notion to try and prevent people from installing modules to the system python. I dislike any kind of organized Linux practice that exists to save users from themselves. I also find the idea of needing to keep track of scads of virtual python environments a bit preposterous. I've never broken my system python by installing modules with sudo pip in the 30+ years I've been doing it. But everyone is free to override (or abide by) PEP 668 as they see fit.