https://bugs.freedesktop.org/show_bug.cgi?id=66025
--- Comment #21 from David Bolen <db3l....@gmail.com> ---
These two statements seem contradictory:
"We / I have never used pygments."
"At that point OpenLP creashed looking for pygments so I needed to install
that."
So it sounds like you're saying OpenLP does use (or conditionally support)
pygments, right?
It's probably not critical though since that was just once instance of the
issue, so we can pick another instead.
Would it be possible to provide me (here or offline) with some specific
instructions on how to set up an environment similar to yours and run exactly
the same scenario you are? Can I just start with the bzr python3-productive
branch and run setup.py? Are you using the LO python to run setup or a system
version?
"Now the remotes plugin is a wrapper for CherryPy and has nothing to do with
uno so how it is needing uno is a mystery at present by I am continuing to
hunt."
It doesn't really, but once uno.py is imported any import statement runs
through that that code since it intercepts the global import hook. What still
has me confused though is that even though that code runs and you'll see uno
stuff in the exception traceback, you only get into the uno code if Python
already rejected the import and the final result for a bad import should still
be an ImportError with or without uno.
For example, in your first case:
-----------------------------
DEBUG Importing remoteplugin from
/home/tim/Projects/openlp/python3-run/openlp/plugins/remotes. Depth 10
2013-07-18 21:02:53,304 openlp.core.lib.pluginmanager
ERROR Failed to import module remoteplugin on path
/home/tim/Projects/openlp/python3-run/openlp/plugins/remotes/remoteplugin.py:
type openlp.plugins.remotes.lib.RemoteTab is unknown
Traceback (most recent call last):
File "/usr/lib64/python3.3/site-packages/uno.py", line 295, in _uno_import
d[x] = pyuno.getClass( name + "." + x )
uno.com.sun.star.uno.RuntimeException: pyuno.getClass: uno exception
openlp.plugins.remotes.lib.RemoteTab is unknown
-----------------------------
The ERROR line is from pluginmanager.py in the "except ImportError" clause, so
that indicates that the attempt to import remoteplugin failed with an
ImportError. The rest of the traceback is from when the uno codes runs. It
appears to have been triggered by a failure on the line:
from openlp.plugins.remotes.lib import RemoteTab, HttpServer
Now, it's flowing through the uno code, but that can only happen if treating it
as a regular Python import already failed (and it was a from xxx import yyy
syntax). But there's no import failure protection here, so I'd expect to see
some sort of failure even without uno imported - so that's perplexing.
The comments in pluginmanager (where it uses imp directly to get around a PyUNO
issue) references tests. So are you seeing errors during tests, or in actual
operation? The pluginmanager code avoids the uno path for the actual module
load, but not for internal imports within the module itself (e.g., the above
import in remoteplugin.py itself).
I may just be missing something obvious though, so being able to run this
locally might help.
BTW, in the other traceback the missing print attribute bit is because it
should be print_exc not print.exc
--
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
