On Tuesday 24 February 2009 17:20:04 Frank wrote: > Hello everyone, > > I'm rather new to mnemosyne, but I've encountered a big problem that's > messing things up big time for me. > > The scenario is as follows: I have my mnemosyne data on a usb stick > and am running mnemosyne 1.2 in linux with ~/.mnemosyne symlinked to > the corresponding directory on the usb device. > > This works fine for my computer at home and at work that both use > Debian Etch. However, I've recently tried it on my EeePC with Eeebuntu > and that's where things got messy. I think the root of the problem is > that Debian Etch sticks to python version 2.4, whereas on Eeebuntu I > use python 2.5 and apparently there seems to be a difference in how > cPickle works. > > The result of this is pretty rough: the .mem file written by a 2.4 > version is not loadable in the 2.5 version and vice versa. > > So I basically have two questions: > - Can anyone confirm this is a problem of differing python versions?
That is indeed the problem. > - Does anyone have a good solution or knows a better work-around (than > making an XML export after each repetition and when switching python > versions first create a new database and import that XML data)? Upgrading Debian to 2.5 seems the easiest thing to do. Peter ------------------------------------------------ Peter Bienstman Ghent University, Dept. of Information Technology Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium tel: +32 9 264 34 46, fax: +32 9 264 35 93 WWW: http://photonics.intec.UGent.be email: [email protected] ------------------------------------------------ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" 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/mnemosyne-proj-users?hl=en -~----------~----~----~----~------~----~------~--~---
