If rebuilding that DB was a major time consumption you wanted to avoid the Leo
code could be modified to use two DB's, one for Py2 and one for Py3. Beyond
that, I don't think there's much alternative. Don't imagine anyone wants to
backport the new protocol to 2.
Cheers -Terry
From: Edward K. Ream <[email protected]>
To: leo-editor <[email protected]>
Sent: Tuesday, January 24, 2017 9:03 AM
Subject: Python 3 -> 2 pickling problems with bigdash plugin
I have just discovered another pickling problem when going backwards from
Python 3 to 2. This happens often enough in my testing. I think there is an
easy workaround, but I'd like your comments.
The bigdash.py plugin uses the whoosh package if it exists, and whoosh has
fallen into the common trap of specifying the latest version for pickling
rather than a fixed version, as discussed on this page.
Terry worked around a similar problem in PickleShareDB ctor. The error message
there is:
Unpickling error - Python 3 data accessed from Python 2?
For bigdash.py, the plan is to have LeoFts.__init__ delete the old database in
~/.leo/fts_index and post a similar error message. This will erase history,
but I see no real alternative.
Your comments, please.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
