Opened 13 years ago

Closed 10 years ago

#11184 closed Bug (fixed)

scripts/ does not respect options passed to

Reported by: pgriess@… Owned by: nobody
Component: Uncategorized Version: 1.0
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Setuptools supports changing the target installation environment when building an RPM ( bdist_rpm) with the --python or --fix-python options. These have the effect of changing the path to the python executable to invoke in the generated .spec file.

However, Django's specifies a custom installation script in scripts/, which always invokes python directly:

# This is what normally does.
python install --root=${RPM_BUILD_ROOT} --record="INSTALLED_FILES"

As a result, it's impossible to generate a Django install to target non-default environments.

Attachments (1)

t11184-r11366.patch (527 bytes) - added by rjc 12 years ago.
use ${python} instead of python in

Download all attachments as: .zip

Change History (7)

comment:1 Changed 13 years ago by Karen Tracey

milestone: 1.1

Not 1.1 material at this point.

comment:2 Changed 13 years ago by anonymous

This can be worked around by manually specifying the correct path in scripts/ before running

comment:3 Changed 12 years ago by Alex Gaynor

Triage Stage: UnreviewedAccepted

Changed 12 years ago by rjc

Attachment: t11184-r11366.patch added

use ${python} instead of python in

comment:4 Changed 11 years ago by Julien Phalip

Severity: Normal
Type: Bug

comment:5 Changed 10 years ago by Aymeric Augustin

Easy pickings: unset
Triage Stage: AcceptedReady for checkin
UI/UX: unset

comment:6 Changed 10 years ago by Aymeric Augustin

Resolution: fixed
Status: newclosed

In [17331]:

Fixed #11184 -- Made it possible to build RPMs with a non-default python executable.

Note: See TracTickets for help on using tickets.
Back to Top