Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Brian May Newsgroups: linux.debian.maint.python Subject: Re: dh-python (pybuild + dh_py*) documentation Date: Wed, 28 Oct 2015 22:50:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Oct 28 21:45:09 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.699 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Organization: Debian Content-Type: text/plain X-Mailing-List: archive/latest/13130 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87611q4qic.fsf@prune.linuxpenguins.xyz Approved: robomod@news.nic.it Lines: 27 Sender: robomod@news.nic.it X-Original-Date: Thu, 29 Oct 2015 08:44:43 +1100 X-Original-Message-ID: <87611q4qic.fsf@prune.linuxpenguins.xyz> X-Original-References: <20151026113605.GW15907@sar0.p1otr.com> <5630BEB9.3060604@debian.org> Xref: csiph.com linux.debian.maint.python:7817 Matthias Klose writes: > I'd like to see a section with examples too, maybe even referencing particular > packages, which show good practice for a given use case, or which demonstrate > some feature. Examples of how to override dh_auto_test to run custom tests would be good. It seems to be the most frequent thing I need to override. Also examples of how to replace javascript files and have them redirected to the packaged files (e.g. libjs-jquery) - this also seems to be a common problem. The other common problem I have is Django applications that put template files under the python directory - which triggers a lintian warning about putting the files under /usr/lib instead of /usr/share (image-file-in-usr-lib). Not sure if we care about this even or if fixing this could be another example. As a side note, been thinking of requesting another lintian check - for python3-* packages that Depends on ${python:Depends} instead of ${python3:Depends} - seems to be a common problem I encounter. (apologies if any of these have already been done, don't have time to check now.) -- Brian May