Closed lacraig2 closed 3 years ago
Could we just rewrite the PyPeripheral to use the pypanda interface instead of linking in a second Python interpreter. @mariusmue do you think that would be a reasonable change?
I already added a pyperipheral compability layer for PyPanda, which allows inclusion from the same python instance as the main analysis script: https://github.com/panda-re/panda/blob/master/panda/python/core/pandare/panda.py#L1605
The "legacy" pyperipheral which embeds a python interpreter is mostly useful when PANDA is run the classic way (i.e., not in library-mode). That being said, I rarely do so these days - so removing it would be fine by me.
In any case, I have no idea where this error may come from, however, I did not test the pyperipheral implementation with Python 3.9.
It's odd. Though it breaks on more than just Python 3.9 (also 3.6). I have issued a PR to close this. Thanks.
This happens when pyperipheral3 is enabled. Not sure why it's just MIPSEL.