Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16787
| From | Andrey Rakhmatullin <wrar@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: pybuild autopkgtest |
| Date | 2025-03-14 16:20 +0100 |
| Message-ID | <KqeZj-62kp-7@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <KqbRL-60bi-5@gated-at.bofh.it> <KqbRL-60bi-3@gated-at.bofh.it> <Kqcut-60E4-5@gated-at.bofh.it> <KqdTA-61Ex-13@gated-at.bofh.it> <Kqewh-61Tu-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Mar 14, 2025 at 03:24:09PM +0100, PICCA Frederic-Emmanuel wrote: >> Using @builddep@ is mostly not useful for testing Python packages. > >does the python tools provide a way to get the runtime dependencies or the test dependencies of a package ? Runtime sure, and we already use that. Test no, they aren't even specified in an uniform way in the upstream code (it could be e.g. a tests/requirements.txt, one or several lists of deps in tox.ini or a custom pip install line in the CI job definition, or nothing at all if they run tests only locally and manually). >But I am wondering if the best would not be to have something more declarative like the extra_dependencies in order to supersede the full dependencies instead of just adding more dependencies. That makes sense. Or maybe it should get only the B-D annotated with !nocheck if those exist. -- WBR, wRAR
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
pybuild autopkgtest picca <picca@debian.org> - 2025-03-14 12:00 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 12:00 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 12:30 +0100
Re: pybuild autopkgtest Jeroen Ploemen <jcfp@debian.org> - 2025-03-14 12:40 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 12:40 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 13:00 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 13:40 +0100
Re: pybuild autopkgtest Carsten Schoenert <c.schoenert@t-online.de> - 2025-03-14 15:10 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 15:50 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:20 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:50 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 17:20 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:00 +0100
Re: pybuild autopkgtest Andrey Rakhmatullin <wrar@debian.org> - 2025-03-14 16:30 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:50 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 16:40 +0100
Re: pybuild autopkgtest Antonio Terceiro <terceiro@debian.org> - 2025-03-14 17:00 +0100
Re: pybuild autopkgtest PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-03-14 13:10 +0100
csiph-web