On Jan 6, 2008 7:46 PM, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> On Jan 5, 2008 10:23 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
> > > 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?
>
> Yes, they will... are you suggesting to just allow the Sandbox to
> overwrite these files?
I was suggesting building them again in a clean sandbox (so they're
not contaminated by the build environment) and slotting them in
place...
>
> > 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?
>
> This doesn't work, unfortunately. I moved the new files from
> PyOpenGL/.SandboxInstall_Root to /Programs/Python and ran Compile
> again, and exactly the same .pyc files appeared.
... but that scuppers that plan anyway.
> > 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.
>
> Since these .pyc files are going to be re-generated again and again at
> both Compile and run time (and Python's FileHash will break anyway),
> I'd just vote to remove these left-overs from the Sandbox, as that'll
> give us a more simple and fast implementation.
That does seem reasonable then.
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
