On Jan 6, 2008 1:33 PM, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We all have seen from time to time recipes for Python based
> applications fail to install due to .pyc and .pyo left-overs. Recently
> a number of apps such as PyOpenGL and PyGObject[1] started to pop-up
> with problems again, so I took some time with Hisham to understand
> what's going on.
<snip>
> It turns out that even when the Python installation has a
> corresponding .pyc file for every .py one, the execution of a .py file
> can still generate an "updated" .pyc one, which ends up appearing in
> our left-over list.
>
<snip>
> So, in short, for the time being, there's no way to get rid of these
> left-overs completely. I'd like to propose to merge my --optimize=0
> option to Compile, and to clean the .pyc files left-over in the
> sandbox -- at least until a fix comes from the Python guys. Any
> comments?
Won't the files keep being regenerated each time they're run in that
case? Is it possible to generate them sandboxed when they're detected,
so it won't come up again, and so we still get whatever efficiency
gain they're supposed to give? If there's some problem with doing
that, just ignoring them in the sandbox is the next best answer. It
would invalidate the FileHash, but so would running any of that code
as root outside the sandbox, so I don't think that's a killer problem.
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
