diff options
author | David Malcolm <dmalcolm@redhat.com> | 2012-06-25 19:52:24 (GMT) |
---|---|---|
committer | David Malcolm <dmalcolm@redhat.com> | 2012-06-25 19:52:24 (GMT) |
commit | 555bfc7ed08e25f40342d7f0bc24e5380d515bfe (patch) | |
tree | ee228eef2ead41560bb181b557048a33aa5771fd /Python/formatter_unicode.c | |
parent | 2e5f371210d91442ec67073bb4dfc52d46e51ef8 (diff) | |
download | cpython-555bfc7ed08e25f40342d7f0bc24e5380d515bfe.zip cpython-555bfc7ed08e25f40342d7f0bc24e5380d515bfe.tar.gz cpython-555bfc7ed08e25f40342d7f0bc24e5380d515bfe.tar.bz2 |
Issue #14443: ensure that brp-python-bytecompile is invoked with the correct
python executable
The __os_install_macro defines some post-processing activities during an rpm
build; one of the scripts it calls is brp-python-bytecompile, which can take
an argument: the python executable with which to byte-compile .py files in the
package payload.
In some older versions of rpm (e.g. in RHEL 6), this invocation doesn't pass
in an argument, and brp-python-bytecompile defaults to using /usr/bin/python,
which can lead to the .py files being byte-compiled for the wrong version of
python. This has been fixed in later versions of rpm by passing in
%{__python} as an argument to brp-python-bytecompile.
Workaround this by detecting if __os_install_post has a 0-argument invocation
of brp-python-bytecompile, and if so generating an equivalent macro that has
the argument, and explicitly provide the new definition within the specfile.
Diffstat (limited to 'Python/formatter_unicode.c')
0 files changed, 0 insertions, 0 deletions