[Python-modules-team] Bug#927756: Run provided tests at package built time
Yaroslav Halchenko
debian at onerussian.com
Mon Apr 22 19:30:06 BST 2019
Package: python-github
Version: 1.40-1
Severity: wishlist
It is typical for packages to run their tests batteries at the package build
time. This helps to guarantee their correct operation for the to be uploaded
version on Debian systems.
I have tried
http_proxy=http://127.0.0.1:9/ HOME=/tmp python -m github.tests -v
on my laptop within virtualenv installing github module from within source
package (since github.tests is not shipped ATM, separate issue). And it seems
to pass so it seems to not require network access and doesn't rely on any HOME
configuration.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python-github depends on:
ii python 2.7.16-1
ii python-jwt 1.7.0-2
ii python-requests 2.21.0-1
python-github recommends no packages.
python-github suggests no packages.
-- no debconf information
More information about the Python-modules-team
mailing list