Bug 293438 - net-mgmt/py-napalm: update to 5.1.0
Summary: net-mgmt/py-napalm: update to 5.1.0
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kai Knoblich
URL: https://github.com/napalm-automation/...
Keywords:
Depends on: 293458
Blocks:
  Show dependency treegraph
 
Reported: 2026-02-25 10:22 UTC by Nick Hilliard
Modified: 2026-02-26 09:36 UTC (History)
0 users

See Also:
kai: maintainer-feedback+


Attachments
Update net-mgmt/py-napalm from 5.0.0 to 5.1.0 (2.21 KB, patch)
2026-02-25 10:22 UTC, Nick Hilliard
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Hilliard 2026-02-25 10:22:52 UTC
Created attachment 268344 [details]
Update net-mgmt/py-napalm from 5.0.0 to 5.1.0

Also adds a new dependency on py-setuptools.
Comment 1 Kai Knoblich freebsd_committer freebsd_triage 2026-02-26 08:57:52 UTC
(In reply to Nick Hilliard from comment #0)

Hi Nick,

thank you for the patch, which LGTM.

I have one question: Is there a specific reason why py-junos-eznc was omitted?  

In the requirements.txt, the version requirement for py-junos-eznc is ">=2.7.4" and the net-mgmt/py-junos-eznc port needs to be updated as well.

I took a closer look at your patch and have already checked a few things.

As far as I can see, py-junos-eznc >= 2.7.4 is needed for Python 3.13+, where "telnetlib" is no longer available, and py-junos-eznc >= 2.7.4 ships "telnetlib" as vendored module. (Whether the use of telnet still makes sense today is another story...)

- Results of test suite of py-napalm with current junos-eznc 2.7.0 in the ports tree:

> [...]
>../../../../../../../usr/local/lib/python3.11/site-packages/jnpr/junos/transport/tty_telnet.py:2
>  /usr/local/lib/python3.11/site-packages/jnpr/junos/transport/tty_telnet.py:2: DeprecationWarning: 'telnetlib' is deprecated and slated for removal in Python 3.13
>    import telnetlib
> [...]
> === 524 passed, 80 skipped, 4 warnings in 2.83s ===


- Results of test suite of py-napalm with latest junos-eznc 2.7.6:

> === 524 passed, 80 skipped, 3 warnings in 2.85s ===


Regardless of these facts, I'd like to take this opportunity to update py-junos-eznc and py-ncclient together with py-napalm in order to obtain a up-to-date status of all components.

I'll create the corresponding bugs in a few minutes and link them to this bug.
Comment 2 Nick Hilliard 2026-02-26 09:15:37 UTC
> I have one question: Is there a specific reason why py-junos-eznc was omitted?  

yeah, once you start updating py package dependencies, things rapidly spiral out of control. There were a lot of other py dependencies which I skipped over due to lack of time.

The root problem I ran into was that the napalm integration in py-salt was stack-dumping unless py-setuptools was installed. The patch I uploaded to this PR passed the "wfm" test, including logging into some junos boxes.
Comment 3 Kai Knoblich freebsd_committer freebsd_triage 2026-02-26 09:36:37 UTC
(In reply to Nick Hilliard from comment #2)

All right, thanks for the additional info. No problem with regard to the Python dependencies - it's indeed like going down a rabbit hole.

The bugs for updating py-ncclient and py-junos-eznc are now available and the latter one is linked with this bug.

As soon as I receive feedback from the maintainer or the timeout is reached, I'll commit everything in one go.