[MacPorts] #44612: Python error while using pip with py33-virtualenv
MacPorts
noreply at macports.org
Mon Aug 11 14:06:58 PDT 2014
#44612: Python error while using pip with py33-virtualenv
---------------------------------------+--------------------------------
Reporter: charlie.clark@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.1
Resolution: | Keywords:
Port: python33 py33-virtualenv |
---------------------------------------+--------------------------------
Comment (by nad@…):
I don't recognize this specific failure mode but there are a number of
possible explanations. Given that a new virtualenv does not exhibit the
problem (I'm assuming that's what you mean by fresh folder), I'd think the
most likely scenarios are either that: (1) the existing virtualenvs have
an incompatible extension module installed (check the virtualenv's
`lib/python3.3` folder; or (2) (more likely) the `python3.3` port was
updated since the old virtualenv's were created and there is now an
incompatibility between the `python3.3` executable in the virtualenv bin
directory and the shared standard library modules in the virtualenv `lib`
directory (by default, virtualenv creates symlinks to the Python framework
directory). Other things to look at are settings of environment
variables, in particular, LANG, LC_*, and PYTHON* ones. But, if the
problem goes away by creating a new virtualenv, I'd just create new ones,
perhaps using the virtualenv `--always-copy` option to avoid future
problems. Or use Python's built-in `pyvenv` (`pyenv-3.3`), the standard
library's implementation of virtual envs introduced in 3.3, which avoids
the symlink issues. (Also Python 3.3 is no longer being actively
maintained upstream. Consider moving to Python 3.4.x).
--
Ticket URL: <https://trac.macports.org/ticket/44612#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list