1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • Re: python3-nose removal (or revival ?)

    From Dmitry Shachnev@21:1/5 to Alexandre Detiste on Wed Sep 18 22:50:01 2024
    Hi Alexandre!

    First of all, thanks for your hard work on porting the packages away from
    nose.

    On Wed, Sep 18, 2024 at 12:32:33PM +0200, Alexandre Detiste wrote:
    Hi,

    While fixing/updating more random packages for the python3-nose removal;
    I stumbled on this new fork:

    https://pypi.org/project/pynose/

    Yes, I saw that too. By the way, there is also another fork called nose3, but it seems even less active.

    This fork brings it's own new problems:
    - licensing needs extensive review: https://github.com/mdmintz/pynose/issues/36
    - unit test are gone: https://github.com/mdmintz/pynose/issues/39

    So I am not convinced it's the way to go;
    It still feels like too little, too late.

    I agree.

    Kicking Nose out of Debian (+ Ubuntu) would
    maybe make some projects reconsider their CI pipeline
    to use a better maintained test runner.

    That’s a nice side effect, but not more. I think the primary motivation for removal is maintenance burden, e.g. the fact that nose often breaks with new Python versions.

    If we worked around some of the problems (e.g. replaced 2to3 with fissix),
    I am fine with giving the maintainers (and their upstreams) more time to port away from nose.

    Also, many upstream projects are using Ubuntu LTS releases, and the next such release is only in 1.5 years anyway.

    python3-pika is the first project I found online that did switched to pynose as prefered test runner in upcoming release.

    It looks like it needs [py]nose only for two relatively small functions from nose.twistedtools. I wonder why they didn’t just vendor that code.

    Debian Code Search also hints to:
    - django-cte (it's on the todo list too)

    This one I don’t see why needs nose at all. The test is very simple and just calls init_db() and destroy_db(), this can be definitely done with pure unittest.

    - thunderbird
    https://codesearch.debian.net/search?q=pynose&literal=1&perpkg=1

    We don’t seem to run Python tests during Thunderbird build.

    So for now, I am not convinced that we need to update nose package to pynose upstream. However, if pynose has some patches that help us, we can always cherry-pick them (maybe after updating debian/copyright).

    That said, https://bugs.debian.org/1080224 is not fixed in pynose. Or at
    least the problematic line is still there: https://github.com/mdmintz/pynose/blob/v1.5.2/nose/commands.py#L122

    --
    Dmitry Shachnev

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEq2sdvrA0LydXHe1qsmYUtFL0RrYFAmbrPCUACgkQsmYUtFL0 RraQqg/+JuwjttcDCcjFm7FFg/DANEtbW9Xf4UFeCCahGMEAGAMdAHuO0zjq7bSz MiQ2DNT9o0OuWSAC5i8zlo7rHes7A777BT8dELZIJIHuhMRUNXCmZg+zwDZ+XJ3Z MU4PBEpq123nDv7ykXM02WlvBwHDm9/BMsbBjWfhMH/WV8TC0MdqkrC6adC7HWvp F4BV6R1+n9HbMqj8xmBl3aMgktVl1QMbgmgKWdbw4DJw829hZst5b2xl7WNFT7eV 6VCy8Q05eo2mdUb9F7Fn7H6U4Qz29OaD+9AAzsFRwLG0hYF5PLQLrWRddjRYJ884 iheZw+5JI8vESiWc7hOwuaoh5ZziixaJdJxD90/3fTx94v+PY1bTb1nd5heeal54 hv4Pso2w/LITGW5K5SbNcfPUj2HiBiwSDQwRqpeRVt2jI+DH+8SvDbNU5byCOuOY fM5X6RnrhCs9RnMPyZvA8BU7YCe9v/I/Zrr9ANcD+CEyS4ql1g8Q/5oQ0/nyEsM9 23wXYBVu2YVkFaEkZtD3ACnTLW/Bpq7cGs6CvMzLzixYr7tLxwgyFNzM2ZQUg0sZ ogTCU86n2fFxIApo4IGuTo+h3XXzV0h1liBfC9lNhC5K6T3xuONl21kYEp50myYw qX03aak4ctW/UHU3RKuypYACbA2t4TJNEhLXfKAUhLQwFGJ/jng=
    =zby4
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dmitry Shachnev@21:1/5 to Alexandre Detiste on Thu Feb 20 11:30:01 2025
    Hi all!

    On Wed, Feb 19, 2025 at 11:01:26PM +0100, Alexandre Detiste wrote:
    Hi,

    Here's an update.

    We are down to 2 packages left depending on python3-nose.

    * elasticsearch-curator:
    it depends on python-elastic-transport in the NEW queue, thanks Karsten

    * amp:
    this was still using "numpy.distutils" to build fortran code
    https://numpy.org/doc/2.2/reference/distutils_status_migration.html#moving-to-setuptools

    amp is not in testing and has 2 RC bugs (other than one about nose), so
    I think we do not need to care about it.

    So when python-elastic-transport is accepted and elasticsearch-curator is fixed, we will have no nose reverse-dependencies in testing.

    I have no idea how to fix this, help is appreciated.

    ---

    My proposal would be to keep fissix (= the 2to3 fork)
    & "modernize" for now and remove those two after Trixie is released.

    "modernize" convert Python2 into "six" code,
    it's a bit of a misnomer, pitfall package;
    what people want is "pyupgrade"

    I don't mind if you do this, but in my opinion keeping nose just for one or
    two packages is not worth the effort.

    I would get it removed, and after that someone can package pynose (a fork) if they need it.

    --
    Dmitry Shachnev

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEq2sdvrA0LydXHe1qsmYUtFL0RrYFAme3AfcACgkQsmYUtFL0 RrbCSA/9H+NqH+gdMSDncIn4xa33r71bvsinYFKOEjPkgr3M5Doc/8/wE6uL8fA5 D6OcQ0o9PBSf5c9eETWx3h5W81UzUAwykcEnJbeN3402ZWTHccAWZkVjnZO99NEL 3d4TADIOMhP6F1WJAj4CZMsTNh4PX+ouybXpB9/cHHM9V5Y6MGREQ/JgOnhiWuTH VHfzaykAkTW4SpA8MCrwU+g5/EO7PXqxj2VIYjMC5laLy+0d3lOrsxARobTO3ENc yPFOGkRAYnFsG8eGCxTARJVH2MADcVERn6uSP1H5e9LDdz4bBwmn/zunIUMyfO2p VDx/Il4LH8MP8NX9hPr/aouamybUxj+QU0r8xcXUiY6hluT7GtnSVHK+oKkSJCgL bVqThecfV+iMdEYEQblwN2ZXBxM2OihQ5SyR74/IhvuL84hJGWZwoqxnVKMqkLpf 29NCENjQc229+uXaPKL+of4Ta6KIb0yiFGpwvCaMMHHjh3Fdj8E4tvVP3qsfH8SO RV5JEfjYiOR/gGcK5Dfb2y3UVjebgV5kQXXWvcHr7DCWN0NdAqjUrFN3RRAz6qyY tQkYkmvW/t66HArprpXHBSPxhGLXugNt9Za0xNkXV59JDYVtOoxFTYYDnvcRoQ+o IcvkNHUkoyHWKx+y/9b0RWoYOtY41bI4E5d4DgYUH+nhB/gesNw=
    =HKig
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From thomas@goirand.fr@21:1/5 to All on Thu Feb 20 14:30:03 2025
    CgpPbiBGZWIgMjAsIDIwMjUgMTE6MjEsIERtaXRyeSBTaGFjaG5ldiA8bWl0eWE1N0BkZWJpYW4u b3JnPiB3cm90ZToKCj4gYW1wIGlzIG5vdCBpbiB0ZXN0aW5nIGFuZCBoYXMgMiBSQyBidWdzIChv dGhlciB0aGFuIG9uZSBhYm91dCBub3NlKSwgc28gCgo+IEkgdGhpbmsgd2UgZG8gbm90IG5lZWQg dG8gY2FyZSBhYm91dCBpdC4gCgoKSSB3aXNoIHlvdSB3ZXJlIHJpZ2h0IGJ1dCB0aGF0IGlzIHVu Zm9ydHVuYXRlbHkgbm90IGhvdyBEZWJpYW4gKGFuZCBpbiBmYWN0IERBSykgd29ya3M6IGFsbCBy ZXZlcnNlIGRlcGVuZHMgTVVTVCBiZSBmaXhlZCBzbyBhIHBhY2thZ2UgY2FuIGJlIHJlbW92ZWQu IFRoaXMgaW5jbHVkZXMgU2lkIG9ubHkgcGFja2FnZXMuCgoKQ2hlZXJzLAoKClRob21hcyBHb2ly YW5kICh6aWdvKQoKCg== PGh0bWw+PGJvZHk+PGJyPjxkaXYgZGlyPSJsdHIiPk9uIEZlYiAyMCwgMjAyNSAxMToyMSwgRG1p dHJ5IFNoYWNobmV2ICZsdDttaXR5YTU3QGRlYmlhbi5vcmcmZ3Q7IHdyb3RlOjwvZGl2Pgo8ZGl2 IGRpcj0ibHRyIj4mZ3Q7IGFtcCBpcyBub3QgaW4gdGVzdGluZyBhbmQgaGFzIDIgUkMgYnVncyAo b3RoZXIgdGhhbiBvbmUgYWJvdXQgbm9zZSksIHNvIDwvZGl2Pgo8ZGl2IGRpcj0ibHRyIj4mZ3Q7 IEkgdGhpbmsgd2UgZG8gbm90IG5lZWQgdG8gY2FyZSBhYm91dCBpdC4gPC9kaXY+Cjxicj48ZGl2 IGRpcj0ibHRyIj5JIHdpc2ggeW91IHdlcmUgcmlnaHQgYnV0IHRoYXQgaXMgdW5mb3J0dW5hdGVs eSBub3QgaG93IERlYmlhbiAoYW5kIGluIGZhY3QgREFLKSB3b3JrczogYWxsIHJldmVyc2UgZGVw ZW5kcyBNVVNUIGJlIGZpeGVkIHNvIGEgcGFja2FnZSBjYW4gYmUgcmVtb3ZlZC4gVGhpcyBpbmNs dWRlcyBTaWQgb25seSBwYWNrYWdlcy48L2Rpdj4KPGJyPjxkaXYgZGlyPSJsdHIiPkNoZWVycyw8 L2Rpdj4KPGJyPjxkaXYgZGlyPSJsdHIiPlRob21hcyBHb2lyYW5kICh6aWdvKTwvZGl2Pgo8YnI+ PC9ib2R5PjwvaHRtbD4=

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dmitry Shachnev@21:1/5 to thomas@goirand.fr on Thu Feb 20 14:30:01 2025
    Hi Thomas!

    On Thu, Feb 20, 2025 at 02:19:58PM +0100, thomas@goirand.fr wrote:
    On Feb 20, 2025 11:21, Dmitry Shachnev <mitya57@debian.org> wrote:
    amp is not in testing and has 2 RC bugs (other than one about nose), so
    I think we do not need to care about it.

    I wish you were right but that is unfortunately not how Debian (and in fact DAK) works: all reverse depends MUST be fixed so a package can be removed. This includes Sid only packages.

    The last upload of that package was in 2018.

    We have the maintainer CCed here. Muammar, are you still interested in amp package?

    If the maintainer does not reply, I think it is a candidate for a RoQA bug.

    --
    Dmitry Shachnev

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEq2sdvrA0LydXHe1qsmYUtFL0RrYFAme3LigACgkQsmYUtFL0 RraA6A//c/UHmjnP6jP1oYqic9uAWjVwanmeXrS0l3A7Qpv3p6gOu+MMC4SBv4Hu 9SJTamA/bkEHMXcAHwLuJaBkbrTN+5l0mqnR2duEPg1Kc9Iu5a+YRwRBz6QWm5z0 7LBnw752gCw1yAz5o8TtzmNR6gRIMamcqPRGm4DeW9hVVSJiMSf7PFbU+wmTVwOZ dl0qR+xi3PbG6uWeeE9foSKdxK9Pqk7wbnxA9cVlYSchs31knZJJmC6pUxEVUYpz 0jhjOZBSHUEN02tbkE2sehg97bA4NLVCKEHl/aFu1XkJm+Eg35rmc7V+rpoLxqPr oOe303PXndndH5bwuxwyda33lVwNaXH/+bIk9D0l0aCydYw3uZ2aRXHFC2wLN9TP FF7sKxAwOH+qlMSE4WuCV5qzMZAw3CI4C5uK30SXKiidvCKRlghXsNvNoE6BM9A/ iJMNhDnZ2auyk6c2gzKAiN3Z6WuWsHmXVo6Lyd1S3rHvv0OPD5fJYQkiHKHHfuQg OacdPHJM2KCxJfY6vd+c3Dj2656+w8MUYMRzQ8YyvHlXWJLMlkTi8w1bzSiJLrUv JjVjEr5JFQ6PP1JuKz7zY1W0pccXxpZpcxWnelImerv9dh95AIeTLa3d9GZ9Mbcu mj15CtApesPE+Vgw8AzM4Ac/4hBrmxo+NxLidbvrFDizOrbhHZE=
    =Xnd9
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)