Puresnmp

~~~~~~~~~~~~~

* **[fixed]** Fixed a regression introduced in 1.6.3 (commit 7e559d5d) causing
modified values for ``BUFFER_SIZE`` and ``RETRIES`` to be ignored.

~~~~~~~~~~~~~

* **[fixed]** Version 1.7.0 introduced a regression which caused ``VarBind``
instances to lose the ability to be indexed. This is now fixed.

~~~~~~~~~~~~~

* **[added]** A new function ``bulktable`` is added to all external APIs:

* ``puresnmp.api.raw.bulktable``
* ``puresnmp.api.pythonic.bulktable``
* ``puresnmp.aio.api.raw.bulktable``
* ``puresnmp.aio.api.pythonic.bulktable``

This function returns a pseudo-table (just like the normal ``table``
function) but uses more efficient SNMP "bulk" requests under the hood.

* **[added]** The library now knows how to deal with "T61" string encodings and
supports them if they are returned from a device (or sent to a device).
* **[support]** The ``table`` and ``bulktable`` functions no longer require the
``num_base_nodes`` argument as it was redundant with the OID. Now, if it is
used, it will emit a deprecation warning and will be removed in a future
release.
* **[support]** The ``bulkwalk`` table now also takes an optional timeout
argument.
* **[support]** The default TCP timeout is now set via the module-level
variable ``puresnmp.const.DEFAULT_TIMEOUT``. This can still be overridden by
using the ``timeout`` argument on function calls.
* **[support]** (internal) The X.690 ``tablify`` function now optionally takes
an OID as table "base", which is easier than passing in the number of
base-nodes.
* **[fixed]** The "retries" and "buffer_size" arguments were not properly
handed over to the "transport" layer which is now fixed.
* **[quality]** More automation via GitHub actions (fixed in ``1.7.0.post1``)
* **[quality]** Code cleanup and type hint improvements. But there's still a
lot of work to be done on the typing front.

~~~~~~~~~~~~~

* **[fixed]** ``puresnmp`` is now also Python 3.8 compatible

~~~~~~~~~~~~~

* **[fixed]** Network socket is now properly closed when the maximum number of
retries has reached. This fixes emissions of Python resource warnings.

~~~~~~~~~~~~~

* **[support]** *(1.6.2.post1)* - Type hints for
``puresnmp.x690.types.ObjectIdentifier`` improved

* **[fixed]** Counter32 and Counter64 values no longer increase above max-value
and properly wrap back to ``0`` as defined in `RFC-2578 Section 7.1.6
<https://tools.ietf.org/html/rfc2578#section-7.1.6>`_ and `RFC-2578 Section
7.1.10 <https://tools.ietf.org/html/rfc2578#section-7.1.10>`_.

If a value is more than one unit above the max-value the behaviour is
undefine in that RFC as it assumes monotonically increasing values. As a
design decision I decided to initialise the value using the overflow amount.
So a counter initialised to ``40`` above maximum, will have the value ``40``.