> The only strange thing is how this can happen with the Python3 shebang in config_usb_printer.py.
Because it's not being invoked directly but by calling
python config_usb_printer.py
And python is always python2, the question here is who is doing the invokation.
> The only strange thing is how this can happen with the Python3 shebang in config_ usb_printer. py.
Because it's not being invoked directly but by calling usb_printer. py
python config_
And python is always python2, the question here is who is doing the invokation.