linter warnings since pylint 3.2.0

[Bastian-Krause]

Since pylint version 3.2.0 was released, our CI fails with these errors in the linting step (warnings emitted on current master 9e0562e):

************* Module labgrid.util.yaml
labgrid/util/yaml.py:87:18: E0606: Possibly using variable 'items' before assignment (possibly-used-before-assignment)

We should probably raise a TypeError in an else clause.

************* Module labgrid.util.dict
labgrid/util/dict.py:39:33: E1133: Non-iterable value attr.fields(cls) is used in an iterating context (not-an-iterable)

Seems to be related to pylint-dev/pylint#9626 (attr's pyi). Should be fixed in the next pylint release.

************* Module labgrid.util.agents.network_interface
labgrid/util/agents/network_interface.py:98:23: E0606: Possibly using variable 'nm' before assignment (possibly-used-before-assignment)

Probably caused by..

labgrid/labgrid/util/agents/network_interface.py

Lines 291 to 295 in 9e0562e

	if getattr(NM.Client, '__gtype__', None):
	# hide this from sphinx autodoc
	bl = BackgroundLoop()
	bl.start()
	nm = bl.block_on(NM.Client.new, None)

@jluebbe How should we fix this?

************* Module labgrid.remote.common
labgrid/remote/common.py:178:24: E1135: Value 'fields' doesn't support membership test (unsupported-membership-test)

Might also be related to pylint-dev/pylint#9626 ?

************* Module labgrid.remote.client
labgrid/remote/client.py:1215:27: E0606: Possibly using variable 'data' before assignment (possibly-used-before-assignment)

I guess we should add an else clause raising an exception here as well?

labgrid/remote/client.py:1327:29: E0606: Possibly using variable 'data' before assignment (possibly-used-before-assignment)

Same here.

************* Module labgrid.driver.mqtt
labgrid/driver/mqtt.py:46:23: E0606: Possibly using variable 'status' before assignment (possibly-used-before-assignment)

Same here.

[aparcar]

I tried to fix the simple stuff over here #1423