Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Understanding pybuild

Path csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod
From Ole Streicher <olebole@debian.org>
Newsgroups linux.debian.maint.python
Subject Understanding pybuild
Date Thu, 19 Dec 2019 13:30:01 +0100
Message-ID <zf36h-52I-3@gated-at.bofh.it> (permalink)
X-Mailbox-Line From debian-python-request@lists.debian.org Thu Dec 19 12:27:08 2019
Old-Return-Path <news@liska.ath.cx>
X-Amavis-Spam-Status No, score=-6.351 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.25, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -5.5
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version 1.0
Content-Type text/plain
Lines 30
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17762
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/87tv5w34aj.fsf@orrococo
Approved robomod@news.nic.it
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Thu, 19 Dec 2019 13:09:40 +0100
X-Original-Message-ID <87tv5w34aj.fsf@orrococo>
Xref csiph.com linux.debian.maint.python:12159

Show key headers only | View raw


Hi,

I am currently updating scikit-image (skimage) to its newest version,
and I have some difficulties to understand how pybuild works (for
setup.py packages):

1. first, dh_auto_build calls "python3.X setup.py build" to create the
packages (Python files and compiled extensions) in
..pybuild/cpython3_3.X/. This however does not include the copying of any
data files.

2. dh_auto_test then tries runs the tests in .pybuild. If the test need
data files installed, they must be copied manually (right?).

3. dh_auto_install finally calls "python3.X setup.py install ..." to
install the complete packages (Python files, extensions, and data files)
from their original place to debian/tmp/. This includes a re-compilation
of the extensions.

What I do not understand now is: what is the purpose of step 1? Except
for the tests, these files seem to be unused. And for the tests, they
are not complete, since the data files are missing.

And what is the canonical way to get the data files copied to
..pybuild/...? They are already marked as such in setup.py. Doing this
manually by the Debian maintainer seems a constant source of error.

Best

Ole

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


Thread

Understanding pybuild Ole Streicher <olebole@debian.org> - 2019-12-19 13:30 +0100
  Re: Understanding pybuild Dmitry Shachnev <mitya57@debian.org> - 2019-12-20 06:50 +0100
    Re: Understanding pybuild Ole Streicher <olebole@debian.org> - 2019-12-20 08:40 +0100
      Re: Understanding pybuild Dmitry Shachnev <mitya57@debian.org> - 2019-12-20 12:20 +0100

csiph-web