pysnmp should follow lextudio/pysnmp?

[Richard Laager]

At $DAYJOB, I ended up going down a long rabbit hole starting with 
python3-pysnmp4 not being updated for the importlib changes in Python 
3.11. This was an issue for me on Ubuntu 24.04. It seems to NOT be an 
issue on sid (for reasons I do not fully understand), even in a fresh 
chroot, so I'm not filing a Debian bug about it.


So at this point, I'm just writing to point out the PyPI points "pysnmp" 
to: https://github.com/lextudio/pysnmp


The last change on that project is from a month ago, and it has a fix 
for this bug. In other words, it appears to be actively maintained.


I looked on Salsa:
https://salsa.debian.org/python-team/packages/python-pysnmp4/

I see some unreleased changes that reference:
https://github.com/pysnmp/pysnmp

The last change there is from over a year ago, and it does not have a 
fix for this bug.


So, at a glance, it seems like you should follow lextudio/pysnmp like 
PyPI does. Of course, I've only looked at this for an hour, so you might 
have more information. I just wanted to mention lextudio/pysnmp (and 
PyPI referencing it) in case you were not aware.


--
Richard


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Numba 0.61.2 and llvmlite 0.44.0 built with with python 3.13, numpy 2.2, and llvm-19

[Graham Inggs]

Hi

On Mon, 14 Apr 2025 at 06:00, Diane Trout  wrote:
> Upstream mostly supports amd64 and arm64, with unofficial support for
> ppcle64.
>
> https://numba.readthedocs.io/en/stable/user/installing.html
>
> Does this new version work for packages that need numba?
>
> How important are mips64el, ppc64el, and s390x for other people using
> packages dependent on numba?

I've requested removal of the numba binaries (all architectures except
amd64 and arm64) in #1103057 for now, to enable migration.

Regards
Graham