@@ -107,7 +107,6 @@ network configuration or text files.
107
107
108
108
The API examples are [ documented on the web] [ 70 ]
109
109
110
-
111
110
# Why
112
111
113
112
[ ciscoconfparse2] [ 17 ] is a [ Python] [ 10 ] library
@@ -157,6 +156,21 @@ Here's why, it:
157
156
- Intentionally requires a different import statement to minimize confusion between the original and [ ciscoconfparse2] [ 17 ]
158
157
- Vasly improves Cisco IOS diffs
159
158
159
+ ## More Cisco / Arista / Other vendor-specific parsers
160
+
161
+ Years ago, I introduced an alpha-quality feature called ` factory ` , where
162
+ I built vendor-specific syntax parsers to extract values from Cisco and other
163
+ vendor configs.
164
+
165
+ This feature turned out to be a very bad design decision; however, it's also much
166
+ more popular than I imagined.
167
+
168
+ Going forward I strongly discourage people from using ` factory ` features. There
169
+ will be no further development on vendor-specific ` factory ` parsers (such as
170
+ [ ` models_cisco.py ` ] [ 71 ] ).
171
+
172
+ I truly apologize for any disappointment.
173
+
160
174
# Docs, Installation, and Dependencies
161
175
162
176
- The latest copy of the docs are [ archived on the web] [ 15 ]
@@ -296,3 +310,4 @@ The word \"Cisco\" is a registered trademark of [Cisco Systems][27].
296
310
[ 68 ] : https://img.shields.io/badge/%F0%9F%A5%9A-Hatch-4051b5.svg
297
311
[ 69 ] : https://github.com/pypa/hatch
298
312
[ 70 ] : http://www.pennington.net/py/ciscoconfparse2/examples.html
313
+ [ 71 ] : https://github.com/mpenning/ciscoconfparse2/blob/main/ciscoconfparse2/models_cisco.py
0 commit comments