Tag Info

New answers tagged

0

I seem to have fixed this issue for myself, I think it's due to a corrupt/buggy "egg" file. I cannot guarantee this will work for you, but I've had this problem for the last 2 months, word for word. And now, I can at least get into scapy. First of all, I found my Python install's paths, with this command: python -c "import sys; print sys.path" In my ...


2

What you're doing is destructive. Each apple update can and will either break or re-introduce parts or all of the python files to are about to delete. Why don't you simply change your path so that the homebrew version of the tool is used? The danger of hacking the core OS is that it's tightly bound into receipts and software update by Apple and you risk ...


0

pip (1.5.6) setuptools (5.4.2) wsgiref (0.1.2) Yosemite 10.10.2


0

Signing the python application, using the instruction in the answer to this question, worked for me.


3

The way I've solved this is in the past is by bundling the contents of the virtualenv directory into Platypus and then activating the bundled Python interpreter with a script. Here's a screencap of the Platypus interface to show you what I mean: You'll notice that I've bundled the entire venv directory (which was created with the virtualenv command), and ...


-1

I happened to notice that on a Yosemite machine where I spend a lot of time in the bash Python interpreter that it was running 2.7.8, as opposed to 2.7.3 which existed on this problematic computer. Installing 2.7.8 from the Python website overwrite the old 2.7.3 and seems to have resolved the issue.



Top 50 recent answers are included