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


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

Re: Understanding pybuild

From Dmitry Shachnev <mitya57@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Understanding pybuild
Date 2019-12-20 12:20 +0100
Message-ID <zfnHI-1P2-1@gated-at.bofh.it> (permalink)
References <zf36h-52I-3@gated-at.bofh.it> <zfjkJ-72l-5@gated-at.bofh.it> <zfl3b-88T-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

On Fri, Dec 20, 2019 at 08:19:41AM +0100, Ole Streicher wrote:
> That would formalize it a bit, but still does not solve the underlying
> problem: it requires that I maintain the list of these files manually,
> while upstream already does this (by adding them to the list of data
> files).
>
> And also, the built time tests are with pybuild not done with the files
> (anc compilations) that are finally installed, but the installed files
> (especially Python extensions) are created again from scratch, doubling
> the compile time and introducing another difficile source of error.

I think pybuild just calls setup.py build and then setup.py install.

So it is a question to upstream build system, why are files recompiled during
install.

--
Dmitry Shachnev

Back to linux.debian.maint.python | Previous | Next — Previous 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