Bug#1018453: pysph: build-depends on python3-nose or uses it for autopkgtest

Antonio Valentino antonio.valentino at tiscali.it
Mon Aug 29 07:44:23 BST 2022


Dear Dmitry,

On Sun, 28 Aug 2022 21:44:23 +0300 Dmitry Shachnev <mitya57 at debian.org> 
wrote:
> Source: pysph
> Version: 1.0~b1-2
> User: python-modules-team at lists.alioth.debian.org
> Usertags: nose-rm
> 
> Dear Maintainer,
> 
> Your package still uses nose [1], which is an obsolete testing framework for
> Python, dead and unmaintained since 2015 [2][3].
> 
> If you received this bug report, it means that your package either has a
> build-dependency on python3-nose or uses that package in debian/tests/control.
> If that is not the case, please reply and CC me explicitly.
> 
> Please port your package to one of the alternatives: nose2 [4], pytest [5]
> or unittest from Python standard library [6].
> 
> There is a script called nose2pytest [7] which can assist with migrating from
> nose to pytest.
> 
> This mass bug filing was discussed on debian-devel in [8].
> 
> [1]: https://tracker.debian.org/pkg/nose
> [2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad
> [3]: https://pypi.org/project/nose/#history
> [4]: https://docs.nose2.io/en/latest/
> [5]: https://docs.pytest.org/en/latest/
> [6]: https://docs.python.org/3/library/unittest.html
> [7]: https://github.com/pytest-dev/nose2pytest
> [8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html
> 
> --
> Dmitry Shachnev

even if "apt rdepends python3-nose" indicates a dependency of pysph form 
nose, it is not the case for the current version of the package (the one 
in unstable, 1.0~b1-2).

The previous version of the package (1.0~b0~20191115.gite3d5e10-4), 
currently only in stable, have this dependency.

pysph is not in testing currently.

The migration of pysph 1.0~b1-2 to testing is blocked by #1010961 and 
#1015009 (ROM to remove old binary packages for [ppc64 s390x] from 
unstable).

I do not think that there is nothing that I can do at the moment apart 
for waiting the closure of #1010961 and #1015009 and the migration to 
testing.

Please let me know how to proceed.


kind regards
-- 
Antonio Valentino



More information about the debian-science-maintainers mailing list