As noted in PR #190, unittest's output changes in Python 3.11 and thus needs to be parsed differently. That PR takes care of it if the Spyder environment has the same Python version as the run environment. However, if the version differ, unittest's output is parsed incorrectly.
This can be fixed by using the Python version in the run environment when parsing the output. This information is stored when dependencies are checked. Alternatively, implementing #76 will (probably) also solve the issue as a side-effect
jitseniesen
commented
1 year ago
As noted in PR #190, unittest's output changes in Python 3.11 and thus needs to be parsed differently. That PR takes care of it if the Spyder environment has the same Python version as the run environment. However, if the version differ, unittest's output is parsed incorrectly.
This can be fixed by using the Python version in the run environment when parsing the output. This information is stored when dependencies are checked. Alternatively, implementing #76 will (probably) also solve the issue as a side-effect