[EMAIL PROTECTED] (Jérôme Marant) writes:
> Bastian Kleineidam <[EMAIL PROTECTED]> writes:
>
> > >I recently created a debian file for my project (see
> > >http://subterfugue.org),
> > >and discovered just now why including .pyc and .pyo files directly doesn't
> > >work optimally.
> > Where is th
Bastian Kleineidam <[EMAIL PROTECTED]> writes:
> >I recently created a debian file for my project (see http://subterfugue.org),
> >and discovered just now why including .pyc and .pyo files directly doesn't
> >work optimally.
> Where is the problem? Python bytecode should be platform
> independent!
Bastian Kleineidam <[EMAIL PROTECTED]> writes:
> >I recently created a debian file for my project (see http://subterfugue.org),
> >and discovered just now why including .pyc and .pyo files directly doesn't
> >work optimally.
> Where is the problem? Python bytecode should be platform
> independent!
>I recently created a debian file for my project (see http://subterfugue.org),
>and discovered just now why including .pyc and .pyo files directly doesn't
>work optimally.
Where is the problem? Python bytecode should be platform
independent! So it is safe to include .pyc and .pyo files. There is no
Hi,
I recently created a debian file for my project (see http://subterfugue.org),
and discovered just now why including .pyc and .pyo files directly doesn't
work optimally.
Looking at other packages which contain python code, it looks like there are
several slightly different variations on how th
5 matches
Mail list logo
