David Siroky wrote:
> When I "compile" my python files with "python -OO " into pyo files
> then they still contain absolute paths of the source files which is
> undesirable for me. How can I deal with that?
Use the script compileall.py (in Lib) to compile all the files. This
script has an opt
David Siroky <[EMAIL PROTECTED]> writes:
> Hi!
>
> When I "compile" my python files with "python -OO " into pyo files
> then they still contain absolute paths of the source files which is
> undesirable for me. How can I deal with that?
Are you trying to save space? In 2.4 and later each cod
V Sat, 09 Jul 2005 11:48:51 -0700, ncf napsal(a):
> Python is compiling the files with absolute paths because it is much
> faster to load a file when you know where it is, than to have to find
> it and then load it.
>
> I'm guessing you're wondering this so you can distribute it compiled or
> suc
V Sat, 09 Jul 2005 10:22:06 -0400, Peter Hansen napsal(a):
> David Siroky wrote:
>> When I "compile" my python files with "python -OO " into pyo files
>> then they still contain absolute paths of the source files which is
>> undesirable for me. How can I deal with that?
>
> Don't do that?
>
Python is compiling the files with absolute paths because it is much
faster to load a file when you know where it is, than to have to find
it and then load it.
I'm guessing you're wondering this so you can distribute it compiled or
such? If so, I wouldn't do that in the first place. Python's compi
David Siroky wrote:
> When I "compile" my python files with "python -OO " into pyo files
> then they still contain absolute paths of the source files which is
> undesirable for me. How can I deal with that?
Don't do that?
Delete the pyo files?
Stop using Python?
I could guess at a few more
