python-netgear-switch-library 0.0.post331__tar.gz → 0.0.post332__tar.gz

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-netgear-switch-library
-Version: 0.0.post331
+Version: 0.0.post332
 Summary: Python library and CLI to query and control Netgear switches over SNMP, NSDP and HTTP.
 Author-email: Tim Ansell <me@mith.ro>
 License-Expression: Apache-2.0

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/docs/conf.py

@@ -33,10 +33,6 @@ sys.path.insert(0, str(DOCS_DIR / "_ext"))
 sys.path.insert(0, str(REPO_ROOT / "src"))
 
 # Imported after the path is set up, so a bare checkout resolves it too.
-from netgear_switch.capabilities import (  # noqa: E402
-    READ_OPERATIONS,
-    WRITE_OPERATIONS,
-)
 from netgear_switch.protocols.http.endpoints import HTTP_SPECS  # noqa: E402
 
 # -- Project ------------------------------------------------------------------
@@ -89,15 +85,16 @@ exclude_patterns = [
 # link to that file.
 default_role = "literal"
 
-# How many operations the library exposes, counted from the library rather than
-# written into the prose. The hand-written version said "Nine reads and ten
-# writes" while there were in fact ten and eleven: the counts were correct when
-# typed and silently went stale as operations were added, which is exactly the
-# kind of restated fact this documentation generates instead.
+# Counted from the library rather than written into the prose, because a
+# hand-written count goes stale silently: this documentation claimed "Four
+# distinct login schemes and five HTML dialects" when there were five and seven.
+#
+# There is deliberately no count of read or write OPERATIONS here. How many
+# there are is not a useful thing for a reader to know -- the pages that used to
+# open with one are followed immediately by a table naming every operation, so
+# the number told nobody anything the table did not. What matters is that the
+# set is the same on every backend, which is what those pages now say.
 rst_prolog = f"""
-.. |read-count| replace:: {len(READ_OPERATIONS)}
-.. |write-count| replace:: {len(WRITE_OPERATIONS)}
-.. |operation-count| replace:: {len(READ_OPERATIONS) + len(WRITE_OPERATIONS)}
 .. |scheme-count| replace:: {len({s.scheme for s in HTTP_SPECS.values()})}
 .. |dialect-count| replace:: {len({s.html_dialect for s in HTTP_SPECS.values()})}
 """

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/docs/guide/concepts.rst

@@ -57,11 +57,10 @@ A backend is *the protocol an operation travels over*:
        transports; ``CONSOLE`` is a serial line rather than a network backend,
        so it is never registered on a model.
 
-The same |read-count| read operations and |write-count| write operations are implemented on every
-backend a model has. That is deliberate: if SNMP writes are locked down on your
-network, or the web UI is the only port through a firewall, you can pick a
-different protocol and get the same answer. :doc:`../models/support` lists the
-gaps that remain.
+Every read and every write is implemented on every backend a model has. That is
+deliberate: if SNMP writes are locked down on your network, or the web UI is the
+only port through a firewall, you can pick a different protocol and get the same
+answer. :doc:`../models/support` lists the gaps that remain.
 
 Dispatch: exactly one backend, every time
 -----------------------------------------

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/docs/guide/reading.rst

@@ -1,8 +1,8 @@
 Reading a switch
 ================
 
-|read-count| read operations, available on :py:obj:`~netgear_switch.sync_api.SyncSwitch` and :py:obj:`~netgear_switch.aio_api.AsyncSwitch` alike, each
-taking an optional ``backend=``. All return frozen dataclasses from
+Every read below is available on :py:obj:`~netgear_switch.sync_api.SyncSwitch` and :py:obj:`~netgear_switch.aio_api.AsyncSwitch` alike, and each
+takes an optional ``backend=``. They return frozen dataclasses from
 `netgear_switch.models`, identical whichever protocol produced them.
 
 The operations

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/docs/guide/writing.rst

@@ -1,7 +1,7 @@
 Changing a switch
 =================
 
-|write-count| write operations, on :py:obj:`~netgear_switch.sync_api.SyncSwitch` and :py:obj:`~netgear_switch.aio_api.AsyncSwitch` alike. Each takes
+Every write below is on :py:obj:`~netgear_switch.sync_api.SyncSwitch` and :py:obj:`~netgear_switch.aio_api.AsyncSwitch` alike. Each takes
 ``force=`` and ``backend=``, each runs over exactly one protocol, and each
 reads back to confirm what it did.
 

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/docs/index.rst

@@ -75,8 +75,8 @@ follows.
 What this library gives you
 ---------------------------
 
-**The same operations on every protocol a switch speaks.** |read-count| reads and |write-count|
-writes, implemented across SNMP, NSDP, the web UI and the FASTPATH CLI, so the
+**The same operations on every protocol a switch speaks.** Every read and every
+write is implemented across SNMP, NSDP, the web UI and the FASTPATH CLI, so the
 *caller* picks — useful when SNMP writes are locked down, or when the web port
 is all a firewall allows. Reading VLANs over SNMP, HTTP and SSH returns the same
 values, and the tests assert it. Where a gap remains, it is listed in

{python_netgear_switch_library-0.0.post331 → python_netgear_switch_library-0.0.post332}/src/netgear_switch/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.0.post331'
-__version_tuple__ = version_tuple = (0, 0, 'post331')
+__version__ = version = '0.0.post332'
+__version_tuple__ = version_tuple = (0, 0, 'post332')
 
 __commit_id__ = commit_id = None