2382a2e32b
pyparsing 2.3.1/2.4.0 had some changes to grouping of And matches, and as a result we'd report 0 properties and 0 matches, and not really do any checks. With this change we get identical behaviour for pyparsing 2.3.1, 2.4.0, 2.4.2: $ hwdb/parse_hwdb.py hwdb/60-evdev.hwdb: 72 match groups, 94 matches, 262 properties hwdb/60-input-id.hwdb: 3 match groups, 3 matches, 4 properties hwdb/60-keyboard.hwdb: 173 match groups, 256 matches, 872 properties Keycode KBD_LCD_MENU1 unknown Keycode KBD_LCD_MENU4 unknown Keycode KBD_LCD_MENU2 unknown Keycode KBD_LCD_MENU3 unknown hwdb/60-sensor.hwdb: 101 match groups, 120 matches, 105 properties hwdb/70-joystick.hwdb: 2 match groups, 3 matches, 2 properties hwdb/70-mouse.hwdb: 104 match groups, 119 matches, 123 properties hwdb/70-pointingstick.hwdb: 8 match groups, 30 matches, 11 properties hwdb/70-touchpad.hwdb: 6 match groups, 9 matches, 6 properties |
||
---|---|---|
.. | ||
.gitattributes | ||
.gitignore | ||
20-acpi-vendor.hwdb | ||
20-acpi-vendor.hwdb.patch | ||
20-bluetooth-vendor-product.hwdb | ||
20-net-ifname.hwdb | ||
20-OUI.hwdb | ||
20-pci-classes.hwdb | ||
20-pci-vendor-model.hwdb | ||
20-sdio-classes.hwdb | ||
20-sdio-vendor-model.hwdb | ||
20-usb-classes.hwdb | ||
20-usb-vendor-model.hwdb | ||
20-vmbus-class.hwdb | ||
60-evdev.hwdb | ||
60-input-id.hwdb | ||
60-keyboard.hwdb | ||
60-sensor.hwdb | ||
70-joystick.hwdb | ||
70-mouse.hwdb | ||
70-pointingstick.hwdb | ||
70-touchpad.hwdb | ||
acpi-update.py | ||
acpi_id_registry.html | ||
ids_parser.py | ||
ma-large.txt | ||
ma-medium.txt | ||
ma-small.txt | ||
meson.build | ||
parse_hwdb.py | ||
pci.ids | ||
pnp_id_registry.html | ||
sdio.ids | ||
usb.ids |