1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
|
.. include:: /includes/_links.rst
Upgrade to 6.x/7.x Releases
===========================
.. toctree::
:maxdepth: 2
This article provides information on how to upgrade to the latest 6.x/7.x
releases from old releases such as 4.x and 5.x.
.. note::
If you have been using PySNMP packages with ``-lextudio`` postfix, now
is the time to remove them and switch to the official PySNMP packages,
which are maintained by LeXtudio Inc. as well.
We already deprecated the ``-lextudio`` packages so users must migrate
to the official packages as soon as possible.
Commercial Support for Migration
--------------------------------
.. important::
**LeXtudio Inc. offers commercial support services** specifically to help organizations
migrate from legacy 4.4.x releases to the latest versions. Professional assistance
can significantly reduce migration time, ensure compatibility, and avoid common pitfalls.
If you're managing critical infrastructure using older PySNMP releases, consider
reaching out for expert guidance through the migration process.
For more information on commercial support options, please visit `Support Options`_.
Upgrade to 5.x Releases
-----------------------
While working on 4.x releases, Ilya actually kept a master branch with some
experimental changes and planned to release as 5.0. However, this plan
wasn't finished and irrelevant to what you see today the 5.x releases from
other maintainers and their forks.
While various 5.0 releases were published by different maintainers, you
only see a single release by LeXtudio Inc., which is 5.1.0, on PyPI for
the official PySNMP project.
.. important::
We only published 5.1.0 release, and we are not planning to publish any
more 5.x releases. The 5.1.0 release was published to ensure smooth
transition for users who are still using the 4.x releases.
We consider the 5.1.0 release as a stepping stone to the 6.x releases,
so please don't stay with them for long.
You should next attempt to upgrade to 6.0.13 release and see if things
work as expected.
Note that you must use Python <3.12, as release 5.1.0 is not compatible
with Python 3.12.
.. important::
Each release has its own end-of-life date, so please check the table on
`this lifecycle page`_ for more details.
Upgrade to 6.0 Releases
-----------------------
The 6.0 release is the first major release upgrade by LeXtudio Inc., after
the team took over the project and attempted twice internally to modernize
the code base. This release introduced the following changes:
* New changes required by Python 3.12 were applied, such as completely free
of asyncore.
* Unit test coverage is further improved.
* New sync API based on asyncio is added to enable synchronous I/O
operations and easy migration from 4.x/5.0 releases.
* The API surface was adjusted slightly to make it more aligned with other
SNMP implementations.
* Upon better time synchronization in 5.0 release, more changes are
included in 6.0 release to make the engine fully compliant with RFC3414.
* Documentation is significantly improved to cover the new features and
changes.
* Continuous collaboration with downstream projects.
PySMI 1.3 and 1.4 releases introduced some changes that are not fully
compatible with PySMI 1.2. So we decided to keep PySNMP 6.0 with PySMI 1.2.
.. important::
We only published 6.0.13 release, and we are not planning to publish any
more 6.0 releases. The 6.0.13 release was published to ensure smooth
transition for users who are still using the 4.x/5.x releases.
We consider the 6.0.13 release as a stepping stone to the 6.1 releases,
so please don't stay with them for long.
You should first attempt to upgrade to 6.1.3 release and see if things
work as expected.
.. important::
Each release has its own end-of-life date, so please check the table on
`this lifecycle page`_ for more details.
Upgrade to 6.1 Releases
-----------------------
We released PySNMP 6.1 release to support users who prefer PySMI 1.3 and
above. Ilya's changes for 4.4.13 release were merged as well.
.. important::
We only published releases >=6.1.3, and we are not planning to publish
many more 6.1 releases. Those releases were published to ensure smooth
transition for users who are still using the 4.x/5.x/6.0 releases.
We consider those releases as a stepping stone to the 6.2 releases,
so please don't stay with them for long.
.. important::
Each release has its own end-of-life date, so please check the table on
`this lifecycle page`_ for more details.
Upgrade to 6.2 Releases
-----------------------
The new sync API was added in 6.0 releases to enable synchronous I/O
operations and easy migration from 4.x/5.x releases. The new API was based
on asyncio and was compatible with Python 3.8 and later.
We were hoping the new sync API would be stable enough to meet the quality
expectation, but it turned out to be the opposite. So we decided to remove
it from 6.2 release.
Alternatively, several options are there,
* You might copy the sync wrappers from 6.1 release and use
them in your code if you still need them.
- You might use other packages like
`pysnmp-sync-adapter <https://pypi.org/project/pysnmp-sync-adapter>`_,
which contains sync wrappers.
However, we are not maintaining those and will provide no support on them.
.. important::
We published releases >=6.2.2, and we are not planning to publish any
older 6.2 releases. The new 6.2 releases were published to ensure smooth
transition for users who are still using the 4.x/5.x/6.0/6.1 releases.
.. important::
Each release has its own end-of-life date, so please check the table on
`this lifecycle page`_ for more details.
Upgrade to 7.0 Releases
-----------------------
The goals are
- Execute code base cleanup to meet PEP 8 requirements.
- Cherry-pick more patches from Ilya's old master branch for his planned
5.0 release.
Breaking changes are
- Many fields and methods are renamed to meet PEP 8 requirements.
- Many types are moved to the newly introduced v3arch module.
- New types are introduced in v1arch module to simplify v1 and v2c operations.
.. important::
Each release has its own end-of-life date, so please check the table on
`this lifecycle page`_ for more details.
Upgrade to 7.1 Releases
-----------------------
The goals are
- Adapt to async DNS queries.
- Rework on GET NEXT and GET BULK related API surface.
- Apply more PEP 8 required changes.
Breaking changes are
- Transport type construction API is completely changed to support
async DNS queries. For example, to create transport targets now users
need to write ``await UdpTransportTarget.create()`` instead of
``UdpTransportTarget()``.
- ``next_cmd`` and ``bulk_cmd`` parameters and return types are revised.
- ``walk_cmd`` and ``bulk_walk_cmd`` are updated accordingly.
- Dropped Python 3.8 support.
- Due to method name changes to meet PEP 8, old names are marked as
deprecated. While most of them are still working due to the compatibility
layer, you should switch to the new names as soon as possible. **The
compatibility layer will be removed in the next major release, 8.0.**
Related Resources
-----------------
- `Support Options`_
- :doc:`/troubleshooting`
- :doc:`/examples/index`
- :doc:`/docs/api-reference`
|
