![]() ![]() usr/bin/python2.7 -c 'import numpy print(numpy._file_)' usr/bin/python2.7 -c 'import sys print(sys.version)' The following two commands should give results the same as those shown On the most up-to-date 10.7 Lion system (10.7.5), typing The py2app glue code could be looking for Pythons in various spots Hon-framework-to-the-new-app-while-using-virutalenv And I find that the message is coming from a py2app-builtĪpplication (and it seems I answered the question 3 years ago!): I just did what I should have done earlier: googled for that Long and somewhat risky process so should only be done as a last resort.īut. To restore user files and settings from the backup. If it did though, then the safestĪpproach is to do a full Time Machine or other backup and restore theīase system from the recovery partition and use the Migration Assistant Unlikely that it would be fooling with the Apple-supplied system Python Good idea, but, even if it is as crappy as its sounds, I would think it ![]() Have noted, running third-party apps like CleanMyMac is probably not a If that doesn't work, restoring files from a backup would be in order,Īgain most likely /Library/Frameworks/amework/*. That wouldīe likely the easiest thing to do and is unlikely to make matters worse. , install it, and see if that solves the problem. Well, she could just download a current Python 2.7.x for OS X from > file you can go take a look at to find out, but I don't know > the name of the Utility - the Error message really does say > I asked her to come here, but I fear she is feeling a tad too Failing that, Cem’s suggestions are good. Best possible solution would be a clean boot and restore from a recent clone (either CarbonCopy Cloner or SuperDuper) followed by a restore of intervening files from Time Machine. > On May 28, 2015, at 11:47 PM, Laura Creighton wrote:Īs a minor addendum - you can point out that “Clean My Mac” is a well-known piece of crap-ware that is so badly written as to be labeled by most people as malware. ![]() > On May 29, 2015, at 9:12 AM, Cem Karan wrote: I've had to do recoveries a couple of times, and it can really save you. Honestly, I hope she has a time machine backup. I **think** its supposed to save all the data on the drive, but again, I've not done this, so I can't make any guarantees.ģ) Wipe it clean and reinstall from scratch. Note that Python 3 won't work none of the built-in scripts expect it.Ģ) OS X recovery - I've never had to do that, so I have no idea how easy/reliable it is. Then figure out where to put symlinks that point back to the install (mildly annoying/hard). > So, I assume this poor soul has done precisely that.ĭoes she have a recent Time Machine backup that she can restore from? Otherwise the solutions are all fairly painful:ġ) Install Python 2.7 from scratch (easy). > Apple-controlled and are used by Apple- or third-party software. You should never modify or delete these, as they are > /System/Library/Frameworks/amework and /usr/bin/python, > The Apple-provided build of Python is installed in > framework build of Python or edit the PyRuntimeLocations array in this > Utility has encountered a fatal error, and will now terminate. > soul who ran this program and broke their Python install. > just got some mail from some poor embarrased ![]() On May 28, 2015, at 11:47 PM, Laura Creighton wrote: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |