Just updated the trunk (it's r2784 now) and launched leo. It printed
the following traceback to its log pane:
unexpected exception in g.importFromPath(rst3)
Traceback (most recent call last):
File "/home/shadow/leo/leo-current/leo/core/leoGlobals.py", line
6677, in importFromPath
module = imp.load_module(moduleName,theFile,pathname,description)
File "/home/shadow/leo/leo-current/leo/plugins/rst3.py", line 78, in
<module>
import mod_http
File "/home/shadow/leo/leo-current/leo/plugins/mod_http.py", line
254, in <module>
class escaped_StringIO(StringIOClass):
TypeError: Error when calling the metaclass bases
module.__init__() takes at most 2 arguments (3 given)
Can not import rst3 from plugin rst3
But leo still started.
I remember that the rst3 stuff went into leo's core a long time ago,
but today I saw this traceback for the first time.
Indeed, my ancient myLeoSettings.leo contains an "rst3.py" line in the
@enabled-plugins node. The global leoSettings.leo's trunk contains the
following concerning rst3:
# The rst3 plugin is no longer needed.
# It's code has been moved to Leo's core
# rst3.py
So I've removed that line from myLeoSettings.leo and restarted leo.
The traceback disappeared.
This is not a complaint, I'm posting it in hope it could be helpful to
other people. This is a very possible situation after a major leo
release, due to differences in the global leoSettings.leo and the
outdated myLeoSettings.leo that users can have from the previous leo
version.
The only thing that could be possibly better in this situation is leo
providing some explicit hint for the user about eventual differences
between myLeoSettings.leo and leoSettings.leo when it tries to import
a certain plugin and fails.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
