Hi Peter,
> vanguards on the other hand is an application which I assume relies on
> pytest for it's testsuite.
>
> So I guess the question is whether it is worth keeping this pile of
> pypy modules around to support the testsuite of one application?
I believe the following patch to src:vanguards can be used to use the
Python 3.x testsuite instead:
--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,9 @@ Build-Depends: debhelper (>= 11),
dh-python,
pypy,
pypy-setuptools,
+ python3-pytest <!nocheck>,
+ python3-stem <!nocheck>,
pypy-stem (>= 1.6.0-3.1),
- pypy-pytest,
pypy-ipaddress
Standards-Version: 4.1.5
Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards
--- a/debian/rules
+++ b/debian/rules
@@ -5,3 +5,6 @@
override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
+
+override_dh_auto_test:
+ dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m
pytest $(CURDIR)/tests'
… but I'm not sure the "python3" in the dh_auto_test line is right.
"{interpreter}" there is replaced with pypy). This also assumes that
running PyPy at runtime will have identical behaviour as Python 3.x.
Enjoy...
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] 🍥 chris-lamb.co.uk
`-
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
