Hi, I'd suggest running the instructions on the website first.
Cheers, Peter > -----Original Message----- > From: [email protected] [mailto:mnemosyne- > [email protected]] On Behalf Of eyeorama > Sent: 02 February 2015 19:16 > To: [email protected] > Subject: [mnemosyne-proj-users] Re: installing on Mac OS X > > I have a similar problem, and I am unsure how the remedy previously > outlined in this thread works, or if it applies to my situation. I am trying > to > install Mnemosyne 2.3.1 on my Mac running Snow Leopard. I am currently > running Mnemosyne 2.2. I believe I have upgraded from a previous > Mnemosyne version, because I have in my Library folder both Mnemosyne > and Mnemosyne_1 directories. I am very hesitant to mess with these, since I > have been a Mnemosyne user for many years and I have thousands of cards. > My main interest in upgrading was to use sync to backup my database and > not lose learning data. (I tried a while back to import into the newer version > of Mnemosyne running on a Debian machine, and I couldn't get it to work. I > thought syncing would be better than import/export) > > I first followed the instructions at http://mnemosyne-proj.org/os-x- > installation , but when I looked at the README that came in the tarball and > the final instructions were different. I went with the README, which in > retrospect seems like a mistake. Instead of running 'sudo make osx' in the > unpacked source directory, I ran 'sudo port select python python27', then > 'python setup.py install' as root. When I try to run the program by typing > 'mnemosyne,' I get the following errors: > > Traceback (innermost last): > File "/usr/local/bin/mnemosyne", line 5, in <module> > pkg_resources.run_script('Mnemosyne==2.3.1', 'mnemosyne') > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/p > ython/pkg_resources.py", line 442, in run_script > self.require(requires)[0].run_script(script_name, ns) > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/p > ython/pkg_resources.py", line 1167, in run_script > exec script_code in namespace, namespace > File "/Library/Python/2.6/site-packages/Mnemosyne-2.3.1-py2.6.egg/EGG- > INFO/scripts/mnemosyne", line 101, in <module> > ImportError: No module named PyQt4.QtGui An unexpected error has > occurred. > Please forward the following info to the developers: > > Traceback (innermost last): > File "/usr/local/bin/mnemosyne", line 5, in <module> > pkg_resources.run_script('Mnemosyne==2.3.1', 'mnemosyne') > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/p > ython/pkg_resources.py", line 442, in run_script > self.require(requires)[0].run_script(script_name, ns) > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/p > ython/pkg_resources.py", line 1167, in run_script > exec script_code in namespace, namespace > File "/Library/Python/2.6/site-packages/Mnemosyne-2.3.1-py2.6.egg/EGG- > INFO/scripts/mnemosyne", line 101, in <module> > ImportError: No module named PyQt4.QtGui > > When I open IDLE, I have no problem importing the PyQt4.QtGui module. > > Do I need to retrace my steps and follow the instructions at > http://mnemosyne-proj.org/os-x-installation ? If so, is there an uninstall > script? Or is there some other problem? > > I appreciate your help. > > J > > On Tuesday, August 30, 2011 at 5:48:54 PM UTC-5, Patrick Kenny wrote: > > The latest version installed properly! > > > > Thank you! > > > Patrick > > On 8月31日, 午前3:48, Peter Bienstman > <[email protected]> wrote: > > > > Can you restore your > u'/Volumes/Ocean/Users/patrick/Library/Mnemosyne > > > > directory to what it was before the update, and help me debug > some things > > > > here? > > > > > Actually, Mnemosyne was never installed on this Mac > > > > Ah, that's probably the reason. Could you delete the > Library/Mnemosyne and > > Library/Mnemosyne_1 and try again with the latest version? > > > > > > > mnemosyne/mnemosyne/libmnemosyne/upgrades/upgrade1.py > > > > > I executed this script manually but it didn't seem to do anything. > (I > > > assume it shouldn't, since I have no Mnemosyne data.) > > > > Actually, I was referring to doing some debugging by adding some > print > > statements to that file, etc, ..., but I think the latest commit fixes > this. > > > > Peter > > -- > You received this message because you are subscribed to the Google Groups > "mnemosyne-proj-users" 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 mnemosyne-proj- > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mnemosyne-proj-users/e4801792- > 858e-402b-abf9-e028d7183a15%40googlegroups.com > <https://groups.google.com/d/msgid/mnemosyne-proj-users/e4801792- > 858e-402b-abf9- > e028d7183a15%40googlegroups.com?utm_medium=email&utm_source=foo > ter> . > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/006e01d03f90%246e5ddcb0%244b199610%24%40UGent.be. For more options, visit https://groups.google.com/d/optout.
