I can reliably hard-crash Leo (Python 3.2) on Windows 7 when searching
for MacOS in LeoDocs.leo.
My attention was drawn to todo.py because of this soft crash when
searching for MacOS when using Python 2.6.4.
Traceback (most recent call last):
File "c:\leo.repo\trunk\leo\core\leoPlugins.py", line 336, in
callTagHandler
result = handler(tag,keywords)
File "c:\leo.repo\trunk\leo\plugins\todo.py", line 999, in updateUI
self.ui.UI.createdTxt.setText(created.strftime("%d %b %y?"))
ValueError: year=1214 is before 1900; the datetime strftime() methods
require year >= 1900
The hard crash happens with only the following plugins enabled:
plugins_menu.py
free_layout.py
todo.py
The crash disappears whenever todo.py is disabled.
This isn't conclusive proof, but I would say todo.py is likely the
culprit. Perhaps the soft crash will pinpoint the problem. My guess
is that there is a related Qt bug too: one does not expect a
ValueError to take down Python :-)
Edward
P.S. I am not at present able to test with Python3.1 on Ubuntu because
I am having trouble installing PyQt4 with Python3.1. PyQt4 works fine
on Python 2.6.
This is what I absolutely *hate* about Linux: when installs go bad it
is *impossible* to determine, with installation files spread all over
creation, what the culprit is. In Windows, installs are always
localized, and it is *much* easier to find out what is, and is not,
installed.
So now I am reduced to installing various packages in the *hope* that
they will cure a seemingly endless stream of installation errors.
EKR
--
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.
