With the recent changes in PyKrita's lookup path (bool Python::setPath(const QStringList& scriptPaths)), it's impossible to start Krita without either of the following:

• a ModuleNotFoundError for the 'encodings' module, followed by a SIG_ABRT crash
• a ModuleNotFoundError for the 'sip' module, but Krita continues running.

The first happens because when runningInBundle, only Krita's library directories are preserved in the lookup path, thus breaking lookup of system package. The second is usually a consequence of attempting to fix the first by setting runningInBundle to false, and it happens because in the lookup path the site-packages folder isn't taken into account.

Fortunately, it is easy to fix this: by checking the result of findKritaPythonLibsPath on the Python dylib, and if it's not found in the app bundle, preserving the original lookup path as returned by Py_GetPath and adding the missing site-packages directories..