| What | Removed | Added |
|---|---|---|
| Severity | Critical | Major |
thank you. lowering severity because this is something that doesn't happen on usual configurations; definitely not out of the box. I was able to reproduce the issue when I added "/usr/lib64/python3.4/_import_failed" to PYTHONPATH explicitly. Given that your sys.path contains an awful lot of eggs, and a custom entry to boot, I suspect that the env variable is at fault. Please check that _import_failed doesn't get added to your PYTHONPATH. Alternately, please try checking contents of sys.path with python3 -S (ignores site.py) or -E (ignores env variables). the default path should look like this: $ python3 -ES -c "import sys; print(sys.path)" ['', '/usr/lib/python34.zip', '/usr/lib64/python3.4/', '/usr/lib64/python3.4/plat-linux', '/usr/lib64/python3.4/lib-dynload']