Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13649
| From | Stuart Prescott <stuart@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: .egg-info for entry points during dh_auto_test |
| Date | 2021-10-22 09:20 +0200 |
| Message-ID | <DaX0l-4oH-5@gated-at.bofh.it> (permalink) |
| References | <DaLVf-606-7@gated-at.bofh.it> <DaTJ7-2d4-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Michael I wrestled with something similar some years ago with translate-toolkit, which has a set of tests that run the binaries it ships but these (entry-points) binaries are not generated until after installation. The pybuild/debhelper sequence is to build, test then install; upstream's view is to build, install then test, and so that is what I faked for that package, overriding the normal test invocation, and running the tests in an execute_after_dh_install step: https://sources.debian.org/src/translate-toolkit/unstable/debian/rules/#L59 I help the test suite find the binaries in debian/translate-toolkit/usr/bin and pybuild points the test harness at the modules in the normal place in .pybuild/. That's pretty ugly, but it has worked out ok for this package. A related problem is the PEP517 builders go from source to wheel and then install the wheel; the entry_points and scripts only appear after installation, and so once again, testing most probably lives after 'install' not before. Given that entry_points, plugin registration, PEP517 are all pointing us towards build/install/test as the paradigm rather than build/test/install, do we need to look for an additional dh step to be added to our normal sequence to help us with what is becoming a common task? regards Stuart -- Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net Debian Developer http://www.debian.org/ stuart@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
.egg-info for entry points during dh_auto_test Michael Fladischer <michael@fladi.at> - 2021-10-21 21:30 +0200
Re: .egg-info for entry points during dh_auto_test Stefano Rivera <stefanor@debian.org> - 2021-10-22 05:50 +0200
Re: .egg-info for entry points during dh_auto_test Stuart Prescott <stuart@debian.org> - 2021-10-22 09:20 +0200
Re: .egg-info for entry points during dh_auto_test Michael Fladischer <michael@fladi.at> - 2021-10-22 16:30 +0200
Re: .egg-info for entry points during dh_auto_test Thomas Goirand <zigo@debian.org> - 2021-10-22 23:30 +0200
Re: .egg-info for entry points during dh_auto_test Dmitry Shachnev <mitya57@debian.org> - 2021-10-30 22:10 +0200
Re: .egg-info for entry points during dh_auto_test Michael Fladischer <michael@fladi.at> - 2021-10-31 14:50 +0100
Re: .egg-info for entry points during dh_auto_test Dmitry Shachnev <mitya57@debian.org> - 2021-10-31 15:20 +0100
csiph-web