Arnaud Fontaine wrote: > It could me useful IMHO if you have for instance a setup.cfg which > looks like this : > > [install_lib] > compile = 1 > optimize = 1 > > I don't understand really why if you remove *.pyc, you don't > remove *.pyo too. Could you clarify this point for me ?
Someone submitted a bug stating that calling "python setup.py clean" leaves an unpredictable set of .pyc files lying around. This could be reproduced, and therefore we clean them now. I have not yet seen a test case that lets .pyo files lying around. For example, I looked at the package python-weblib-1.3.3. Its setup.cfg contains [install] compile = 1 optimize = 1 I don't know if that's the same as your case, but anyway. Running clean leaves a file ./pyweblib/__init__.pyc but there is no file ./pyweblib/__init__.pyo or anything like that. So before we go around deleting .pyo files, we at least need to see some .pyo files that need deleting in the first place. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
