[kde-freebsd] Re: ports/155435: [PATCH] devel/kdebindings4-python-pykdeuic4 leaves .pyo files after deinstall
Jason E. Hale
bsdkaffee at gmail.com
Fri Mar 11 08:30:17 CET 2011
The following reply was made to PR ports/155435; it has been noted by GNATS.
From: "Jason E. Hale" <bsdkaffee at gmail.com>
To: Raphael Kubo da Costa <kubito at gmail.com>
Cc: bug-followup at freebsd.org
Subject: Re: ports/155435: [PATCH] devel/kdebindings4-python-pykdeuic4 leaves .pyo files after deinstall
Date: Fri, 11 Mar 2011 02:25:01 -0500
On Thursday, March 10, 2011 20:10:48 Raphael Kubo da Costa wrote:
> Jason E.Hale <bsdkaffee at gmail.com> writes:
> > The .pyo files are generated when the Python module is used.
> Can you elaborate?
> The PYTHON_INSTALL macro only seems to "byte-compile" the passed .py
> file into a .pyc file without passing "-O" to the python interpreter, so
> a ".pyo" should not have been generated at all. And even if it were,
> there seems to be no CMake command to install it.
Right. It works as it was intended; generate the .pyc file and install the
.py and .pyc files. Somehow the .pyo files are being generated at runtime. I
have not figured out what is causing that. I only discovered it because I was
switching from Python 2.6.x to Python 2.7.x and was looking at all the
leftovers in the site-packages directory.
I simply got to the bottom of why the .pyo files were not being installed in
the first place since just about every other Python application in the ports
tree installs them. That is why I patched the PYTHON_INSTALL macro to also
install the optimized byte-compiled code.
More information about the kde-freebsd