At 12:01 PM 3/24/2010 -0700, Aaron Brice wrote:

I am working on a RHEL5 system with python 2.4 installed as /usr/bin/python and python 2.6 installed as /usr/bin/python2.6.

When I run "python2.6 setup.py install" in a module it generally does the right thing and installs to /usr/lib/python2.6/site-packages/. So I want to generate a rpm to deploy the module, but "python2.6 setup.py bdist_rpm" does not do the right thing, the .spec file generated uses "python" and not "python2.6" and the resulting rpm installs to /usr/lib/python2.4/site-packages/.

Is there a way to override this behavior?

The --fix-python option hardcodes the path to the currently-running python. Run "setup.py bdist_rpm --help" for more details.