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

Re: Compiled bytecode installed, because test suite was run

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Piotr Ożarowski <piotr@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Compiled bytecode installed, because test suite was run
Date	Tue, 12 Apr 2016 09:00:03 +0200
Message-ID	<rn0sP-2QN-21@gated-at.bofh.it> (permalink)
References	<rmXEB-pr-3@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Tue Apr 12 06:52:15 2016
Old-Return-Path	<piotr@ozarowski.pl>
X-Amavis-Spam-Status	No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_FROM_MX=-3.1; rate: -6.1
Mail-Followup-To	debian-python@lists.debian.org
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Disposition	inline
Content-Transfer-Encoding	8bit
X-Operating-System	Debian GNU/Linux (4.3.0-0.bpo.1-amd64)
User-Agent	Mutt/1.5.23 (2014-03-12)
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13744
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20160412065156.GF2764@sar0.p1otr.com
Approved	robomod@news.nic.it
Lines	31
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Tue, 12 Apr 2016 08:51:56 +0200
X-Original-Message-ID	<20160412065156.GF2764@sar0.p1otr.com>
X-Original-References	<857fg31o56.fsf@benfinney.id.au>
Xref	csiph.com linux.debian.maint.python:8417

Show key headers only | View raw

[Ben Finney, 2016-04-12]
> I am packaging a code base, which has a test suite. The compiled byte
> code from the test suite run, is being collected when Pybuild discovers
> the resulting Python packages.
> 
> As far as I can determine, these steps are occurring:
> 
> * Pybuild runs the upstream test suite
> * which imports the Python packages
> * which creates the compiled bytecode files
> * which remain in the package directories
> * which are scooped up by Pybuild for installation

* which should be removed by dh_python3

> * which leads to Lintian correctly complaining
>   “package-installs-python-pycache-dir”.
> 
> How do I convince Pybuild to run the tests as part of the package build
> (as normal), but clean up the compiled files *after* the tests and
> *before* gathering the installed files?

does your package name start with python3- or do you have
${python3:Depends} in Depends?

(yeah, something dh_python* should be more verbose about, will be fixed
soon)
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Thread

Compiled bytecode installed, because test suite was run Ben Finney <ben+debian@benfinney.id.au> - 2016-04-12 06:00 +0200
  Re: Compiled bytecode installed, because test suite was run Piotr Ożarowski <piotr@debian.org> - 2016-04-12 09:00 +0200
    Re: Compiled bytecode installed, because test suite was run Ben Finney <ben+debian@benfinney.id.au> - 2016-04-12 09:40 +0200
      Re: Compiled bytecode installed, because test suite was run Piotr Ożarowski <piotr@debian.org> - 2016-04-12 10:00 +0200
    Re: Compiled bytecode installed, because test suite was run Ben Finney <ben+debian@benfinney.id.au> - 2016-04-13 03:00 +0200
      Re: Compiled bytecode installed, because test suite was run Piotr Ożarowski <piotr@debian.org> - 2016-04-13 11:10 +0200
        Re: Compiled bytecode installed, because test suite was run Piotr Ożarowski <piotr@debian.org> - 2016-04-13 11:50 +0200
        Re: Compiled bytecode installed, because test suite was run Ben Finney <ben+debian@benfinney.id.au> - 2016-04-13 12:50 +0200
          Re: Compiled bytecode installed, because test suite was run Piotr Ożarowski <piotr@debian.org> - 2016-04-13 14:00 +0200

csiph-web