Bug 971527

Description of problem:

Python:

https://www.openshift.com/forums/openshift/deployment-error-with-python-27-cartridge


2) Python:

During a git push, I get some errors, and the deployment of my application fails.

I'm not sure why python 2.6 appears in the paths below since this is a python 2.7 cartridge.

It looks like someone recently posted a similar error on Bugzilla for apps that use pymongo, and my app uses pymongo. https://bugzilla.redhat.com/show_bug.cgi?id=969953

Any help would be really appreciated!


remote: Installing setuptools................................................
remote:   Complete output from command /var/lib/openshift/5...n/virtenv/bin/python -c "#!python
remote: \"\"\"Bootstra...sys.argv[1:])
remote: NameError: global name 're' is not defined
remote: ----------------------------------------
remote: ...Installing setuptools...done.
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 2577, in <module>
remote:     main()
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 979, in main
remote:     no_pip=options.no_pip)
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 1091, in create_environment
remote:     search_dirs=search_dirs, never_download=never_download)
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 611, in install_setuptools
remote:     search_dirs=search_dirs, never_download=never_download)
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 583, in _install_req
remote:     cwd=cwd)
remote:   File "/usr/lib/python2.6/site-packages/virtualenv.py", line 1057, in call_subprocess
remote:     % (cmd_desc, proc.returncode))
remote: OSError: Command /var/lib/openshift/5...n/virtenv/bin/python -c "#!python
remote: \"\"\"Bootstra...sys.argv[1:])


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

The python-2.6 showing up in the backtrace isn't really the issue here.
It is because we use the virtualenv tool installed to system python-2.6
The real issue is the corrupted virtualenv for which we already have a bug open.

*** This bug has been marked as a duplicate of bug 969953 ***