[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Before disabling SIP, I found I could use fs_usage to get some visibility into fs changes: sudo fs_usage -w -f filesys | grep aliases.py To test my understanding of fs_usage, I deleted aliases.py (also confirming that triggers the error). When I did so, I

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Looks like I can [disable SIP](http://internals.exposed/blog/dtrace-vs-sip.html) and dtrace will be viable. -- ___ Python tracker

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: I thought I was on to something when I found this technique for using dtrace to detect a file deletion: https://blogs.oracle.com/zoneszone/entry/who_keeps_removing_that_file However, I don't seem to have privilege to run it. $ cat trap-aliases-delete #!

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: I am using the python.org rc1 installer, confirmed to match the public md5 sum: $ md5 ~/Downloads/python-3.6.0rc1-macosx10.6.pkg MD5 (/Users/jaraco/Downloads/python-3.6.0rc1-macosx10.6.pkg) = 404c390ae27f067aaab34f168cf913eb I downloaded ClamXav and had it

[issue28949] Unable to launch Python interpreter

Ned Deily added the comment: Jason, assuming you are using the python.org 3.6.0r1 installer, let us know what you find out! -- nosy: +ned.deily ___ Python tracker

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Hmm. Looks like I may [have a trojan](http://stackoverflow.com/a/4707258). -- ___ Python tracker ___

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Indeed it seems that aliases.py is missing. $ ls /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/encodings/a* /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/encodings/ascii.py --

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Spontaneously, this issue has arisen again. Without a system restart or any system-level configuration changes, launching the interpreter is once again causing crashes. In addition to the crash log I pasted earlier, I see this in the console when launching

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: A simple re-install corrected the issue and survived a restart. I suspect one or more components weren't properly upgraded or were corrupted for unrelated reasons. I suspect that it was an environmental issue and not an issue with the package itself.

[issue28949] Unable to launch Python interpreter

New submission from Jason R. Coombs: I recently upgraded Python 3.6.0rc1 over 3.6.0b4. Python would invoke just fine after the update, but following a system restart, I'm experiencing crashes on any invocation of Python. I suspect it's just a bad/corrupted install. I will do more