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
> > > optio
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 le
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 problem
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.
It looks
