On Wed, Oct 25, 2006 at 09:01:03PM +0200, Ronald Oussoren wrote: > > On Oct 25, 2006, at 8:05 PM, Christopher Blunck wrote: > > > > > > >the trouble here with that %install section is that the python modules > >get bytecompiled and thus turned into native code. i'd prefer for > >that not to happen, so i have written my own install.sh script and i > >provide that to my python setup.py call as follows: > > .pyc and .pyo files aren't native code, they are bytecode files that > work on all platforms. There should therefore be no need to surpress > bytecode compilation.
oh i see... my mistake. :) how do you workaround the "installed (but unpackaged) file(s) found" error related to the .pyo/.pyc files? i noticed it's a python bug as well as a redhat bug. ps - the original reason i went down the rabbit hole of --optimization 0 and --no-compile was that i was trying to get around the installed but unpackaged files error. my thought was that if i could prevent the creation of the .pyc and .pyo files then i could avoid the rpmbuild error. -c -- WeatherNet Observations for station: home Temperature: 54.20F Pressure: 30.02in; Dew Point: 33.22F (45%) Wind: 64 at 3 mph Recorded: 19:04:50 10/25/06 (http://wsdl.wxnet.org/inquiry/binding.wsdl) _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
