Ned Deily added the comment:
To add to Zach's comment, there have been extended discussions in the past
about whether there should be a separate set of environment variables for
Python 3 vs Python 2 interpreters; see, for instance, Issue2375 and
http://comments.gmane.org/gmane.comp.python.deve
Zachary Ware added the comment:
> That seems crazy...
What's crazy about it? There are very very few legitimate situations where you
need to permanently set any PYTHON* variable, particularly PYTHONPATH and
PYTHONHOME. Adding site-packages to sys.path via PYTHONPATH is completely
unnecessar
Steven D'Aprano added the comment:
It looks like your Python 3 is somehow using your Python 2 site directory. What
does your PYTHONPATH contain?
Try running this:
python3 -E -S -c "import sys; print(sys.path)"
and see what it says.
--
nosy: +steven.daprano
type: crash -> behavior
__
Richard Penman added the comment:
Apparently "The PYTHONPATH variable is used by all versions of Python 2 and
Python 3, so you should not permanently configure this variable unless it only
includes code that is compatible with all of your installed Python versions."
That seems crazy...
--
Richard Penman added the comment:
The full error log:
$ python3
Failed to import the site module
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/site.py", line 75, in
__boot()
File "/usr/local/lib/python2.7/site-packages/site.py", line 23, in __boot
l
New submission from Richard Penman:
I installed latest release
(https://www.python.org/downloads/release/python-351/) on OSX and get this
error:
$ python3
...
ImportError: This package should not be accessible on Python 3. Either you are
trying to run from the python-future src folder or your
