Add commented out import for DigitalInOut

[xon235]

This seems to be the better way in order to avoid confusion

[tannewt]

How does this avoid confusion? Is there a context for this that I'm missing?

[caternuson]

Is it to go along with these commented out lines?

Adafruit_CircuitPython_PN532/examples/pn532_readwrite_mifare.py

Lines 46 to 52 in b949e87

	# With I2C, we recommend connecting RSTPD_N (reset) to a digital pin for manual
	# harware reset
	#reset_pin = DigitalInOut(board.D6)
	# On Raspberry Pi, you must also connect a pin to P32 "H_Request" for hardware
	# wakeup! this means we don't need to do the I2C clock-stretch thing
	#req_pin = DigitalInOut(board.D12)
	#pn532 = PN532_I2C(i2c, debug=False, reset=reset_pin, req=req_pin)

[xon235]

Is it to go along with these commented out lines?

Adafruit_CircuitPython_PN532/examples/pn532_readwrite_mifare.py

Lines 46 to 52 in b949e87

	# With I2C, we recommend connecting RSTPD_N (reset) to a digital pin for manual
	# harware reset
	#reset_pin = DigitalInOut(board.D6)
	# On Raspberry Pi, you must also connect a pin to P32 "H_Request" for hardware
	# wakeup! this means we don't need to do the I2C clock-stretch thing
	#req_pin = DigitalInOut(board.D12)
	#pn532 = PN532_I2C(i2c, debug=False, reset=reset_pin, req=req_pin)

Yes, since we are letting others choose which connection or feature to choose by uncommenting lines, we might as well include import lines for required imports when uncommenting lines such as line 48, 51 and also 56. Which all requires DigitalInOut.

I first came across this when trying this example using SPI.

[caternuson]

Thanks. Looks good. Hopefully that will be a little more clear and less confusing when trying to use I2C/SPI.