Groups > linux.debian.maint.python > #11971

Python module packages that don't bytecompile on installation?

Path	csiph.com!weretis.net!feeder7.news.weretis.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod
From	Paul Wise <pabs@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Python module packages that don't bytecompile on installation?
Date	Sat, 02 Nov 2019 04:30:01 +0100
Message-ID	<yXSgV-18y-1@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-python-request@lists.debian.org Sat Nov 2 03:23:07 2019
Old-Return-Path	<pabs@debian.org>
X-Amavis-Spam-Status	No, score=-12.663 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, SARE_MSGID_LONG40=0.637] autolearn=ham autolearn_force=no
Organization	Debian
Content-Type	multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-fxLKGeI4xw/G7JWd58d1"
MIME-Version	1.0
User-Agent	Evolution 3.34.1-2+b1
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/17536
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/4b0d37a23b7e605d68d079b56c7d45a64f188a20.camel@debian.org
Approved	robomod@news.nic.it
Lines	67
Sender	robomod@news.nic.it
X-Original-Date	Sat, 02 Nov 2019 11:22:46 +0800
X-Original-Message-ID	<4b0d37a23b7e605d68d079b56c7d45a64f188a20.camel@debian.org>
Xref	csiph.com linux.debian.maint.python:11971

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi all,

I run adequate on my system, which means I notice when Python module
packages don't bytecompile when they are installed. So far I've just
been ignoring the warnings that adequate prints.

https://salsa.debian.org/debian/adequate

In addition I noticed:

 * some Python modules on my system weren't bytecompiled but did
   bytecompile when I reinstalled them (blinker for example)
 * many of the Python modules on my system don't bytecompile their test
   directories (django for example)
 * relatively few packages I have installed don't bytecompile when I
   ignore test paths (lib2to3, tk, uno, distutils)

Some questions:

Should all module packages bytecompile?

Should all module packages bytecompile all their directories?

What are the downsides when module packages don't bytecompile?

What are the downsides when module packages do bytecompile?

Do we need a lintian complaint about this issue?

Do we need any improvements in how module packages bytecompile?
For example using triggers instead of postinst scriptlets.

Any other thoughts?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Python module packages that don't bytecompile on installation? Paul Wise <pabs@debian.org> - 2019-11-02 04:30 +0100
  Re: Python module packages that don't bytecompile on installation? Matthias Klose <doko@debian.org> - 2019-11-02 11:10 +0100
    Re: Python module packages that don't bytecompile on installation? Paul Wise <pabs@debian.org> - 2019-11-03 02:30 +0100
      Re: Python module packages that don't bytecompile on installation? Matthias Klose <doko@debian.org> - 2019-11-03 10:30 +0100
      Re: Python module packages that don't bytecompile on installation? Ansgar <ansgar@43-1.org> - 2019-11-04 09:10 +0100

csiph-web