aa84c55bef
In a couple of python module tests, we try to test things that rely on the default python being the same one we look up in the python module. This is unsolvable for the deprecated python3 module, as it actually uses the in-process version of python for everything. For the python module, we could actually look up the default system python instead of the one we are running with, but then we wouldn't be testing the functionality of that alternative python... and also the install manifest tests would see files installed for the wrong version of python, and report a combination of missing+extra files... Solve both tests by just skipping the parts we cannot check. |
||
|---|---|---|
| .. | ||
| 1 basic | ||
| 2 extmodule | ||
| 3 cython | ||
| 4 custom target depends extmodule | ||
| 5 modules kwarg | ||
| 6 failing subproject | ||
| 7 install path | ||
| 8 different python versions | ||