python policy is unclear on whether python programs should be arch all or arch any
Junichi Uekawa
reassign python
retitle 128991 Python policy does not document how to package python programs
thanks
I believe "python policy" lacks documentation on how to package
python programs, (as opposed to modules).
During discussion in debian-devel, it was pointed out that
byte-compiled python code is cross-platform, and thus it should be
architecture: any.
Dirk Eddelbuettel <e...@debian.org> cum veritate scripsit:
> > Wajig should be arch: all, then, and
> > Build-Depends -> Build-Depends-Indep: and
> > binary-arch -> binary-indep.
> Okay, I now read the full thread in the debian-devel archive, and conclude
> that you have not supplied a valid reason for this bug report.
>
> As another point, the python package I looked at which where package as
> "Arch: all" did /not/ ship .pyo/.pyc files and cannot serve as examples.
>
> reportbug is an exception. It compiles it files in the postinst. But before
> we jump to conclusion, I would like to see something well-founded that
> argues either way. I'm not unwilling to change the wajig package; but I have
> not been convinced that postinst compilation is desirable (or feasible).
>
> Hence, I'll close this bug report.
--
dan...@debian.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
--
To UNSUBSCRIBE, email to debian-pyt...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Torsten Landschoff
> During discussion in debian-devel, it was pointed out that
> byte-compiled python code is cross-platform, and thus it should be
> architecture: any.
I think you mean arch: all. Any means a rebuild for each architecture.
More interestingly the python policy should mention how to handle
byte-compiled code. My packages are building them on installation
and I think this is the way how it should be. I am not sure if the
same .pyc file runs on all systems...
Greetings
Torsten