On Nov 7, 2007 8:43 PM, Giambattista Bloisi <[EMAIL PROTECTED]> wrote:
> Hi Hisham,
> I checked and I have these files too in my Python installation
> (recently I got Python 2.5-r2 binary package):
>
> [EMAIL PROTECTED] /Programs/Python/Current/lib/python2.5]ls -ls py_compile.py*
> 8 -rw-r--r-- 1 root root 5518 2007-02-22 23:08 py_compile.py
> 8 -rw-r--r-- 1 root root 6632 2007-02-22 23:09 py_compile.pyc
> 8 -rw-r--r-- 1 root root 6632 2007-02-22 23:09 py_compile.pyo
>
> Anyway after doing:
>
> cd /Programs/Python/Current/lib/python2.5
> python -c "import py_compile"
> python -O -c "import py_compile"
>
> "Compile PyGTK" fails again.
>
> Instead after a "RemoveProgram PyGTK 2.10.6", "Compile PyGTK" succeeds
> even if repeated.
>
> The same behavior for "PyGObject": Compile gives no sandbox errors only
> after removing the already installed package.
>
> So I think that there should be some other factors that force Python to
> regenerate py_compile.py* objects.
Did you choose to remove the existing package when re-Compiling? The
recurring errors you got after py_compile.{pyc,pyo} were already
present may have been caused by stale entries in
/Programs/PyGTK/2.10.6/.SandboxInstall_Root.
In any case, I'm committing a change to SandboxInstall so that this
directory is always cleared before the sandbox is called.
-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
