On Thursday 15 November 2007, Johannes Meixner wrote: > Think about the "worst case" when the user replaces our Pyhon > with whatever self-compiled Pyhon. > > Are byte-compiled Python .pyc and .pyo files the same for any Python > and/or is any Python sufficiently smart to know when .pyc and/or .pyo > files are outdated (even if the matching .py files are unchanged)?
they`re installed in a versioned directory. python does not do any checking other than timestamp comparison, so it will never read an outdated bytecompiled version. Thats about it. > I wonder why in this case small RPMs seem not to count. So far printing with more than 100MB of data is the bigger factor compared to a couple of mb we could save by not packaging pyc files. > I am no Python expert at all and I would be happy if a Python expert > could provide some background information. if you %fdupe the pyc/pyo files, the overhead is lower. and the parsing overhead is significant for smaller short lived python scripts. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
