#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 | ---------------------------------------+-------------------------------- Changes (by larryv@…): * cc: jwa@…, stromnov@…, nad@… (added) * keywords: Python => * port: python33 setuptools => python33 py33-virtualenv Comment: I cannot reproduce this, but that “no mem” error looks dire. {{{ % port installed py33-virtualenv The following ports are currently installed: py33-virtualenv @1.11.6_0 (active) % virtualenv-3.3 virtualenv-test Using base prefix '/opt/local/Library/Frameworks/Python.framework/Versions/3.3' New python executable in virtualenv-test/bin/python3.3 Also creating executable in virtualenv-test/bin/python Installing setuptools, pip...done. % cd virtualenv-test % bin/pip list pip (1.5.6) setuptools (3.6) % }}} Have you tried with other versions of Python? -- Ticket URL: <https://trac.macports.org/ticket/44612#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#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

#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@…): Not to belabor the point, but note I wrote "Python 3.3 is no longer being actively maintained upstream". By upstream, I mean the CPython development project at python.org. Python 3.3.x entered security-fix only mode back in March when Python 3.4.0 was released; non-security bugs are no longer accepted or fixed for 3.3.x. See http://legacy.python.org/dev/peps/pep-0398/ -- Ticket URL: <https://trac.macports.org/ticket/44612#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X