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
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!
[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
Rob Tillotson <[EMAIL PROTECTED]> writes:
> Then we have no choice, all Python packages will have to depend on a
> specific version of Python and be installed under that version's
> library, no matter how the .pycs are supplied.
Okay, but I'm thinking that not all .pycs should necessarily go in
/
4 matches
Mail list logo