https://bugs.freedesktop.org/show_bug.cgi?id=66025
--- Comment #30 from David Bolen <db3l....@gmail.com> --- (In reply to comment #29) > * at least the stuff coming with LO from offapi/org/freedesktop/PackageKit/ > is not; > * anything coming with 3rd-party extensions should not be. Thanks, good to know. So assuming those other namespaces are also accessible from the uno import code, clearly that means hardcoded namespace checks can't work. It would still be a nice improvement if there was some way to avoid uno losing the original python import error and traceback for non-uno stuff, but offhand it sounds like there's no safe way to distinguish uno vs. non-uno in the failure case. I wonder if it might be better to prefer re-raising the original python import error if present if the default uno processing fails. The uno failure exception is pretty generic anyway, so the original Python exception should work about as well, while in the non-uno case, the original Python exception (and more critically, traceback) is far superior to the current uno exception. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
