| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
Fixes #10523
|
|
Primarily interesting to me because it is then available for the python
module's install_sources method.
Based on the new feature in install_headers.
|
|
If there isn't a preexisting dependency on python, append one. It's
almost assuredly needed, so just do the right thing out of the box.
|
|
Apparently Azure provides 64-bit python2 when we try to test 32-bit, and
that breaks everything on the 32-bit test runner.
I don't understand the environment setup, and that runner is
disappearing soon anyway. Hopefully this shuts up the known breakage.
|
|
If a version of python is installed for testing against, we should
assume it's actually important to test against it.
|
|
Perhaps when this test case was originally created, project tests could
not use a matrix of options? This is certainly possible today, so don't
write special unittest handling for this instead.
This adds proper visibility into what gets run and what doesn't. Now we
know which python executables got tested and which got skipped.
|
|
|
|
Signed-off-by: Filipe Laíns <lains@riseup.net>
|
|
- default to python site-packages
- subdir to site-packages/subdir
- arbitrary install_dir
|
|
Fixes: #9038
|
|
This reverts commit 566383c727219fc20cf1c90c0fe7dae4bcac5c96.
|
|
Fixes: #9038
|
|
performed by running "pyupgrade --py36-plus" and committing the results
|
|
before this, tests were being skipped on Ubuntu 20.04 with Anaconda Python
Now, all 5 tests success
|
|
|
|
|
|
|
|
|
|
|
|
This mirrors the modules keyword argument that some dependencies (such
as qt and llvm) take. This allows an easier method to determine if
modules are installed.
|
|
Currently find_installation is silent, which is pretty annoying. Let's
log it.
|
|
This doesn't touch everything as it's just based on the python3 module
tests, ported to the python module. It's still better than the one very
basic test in the unit test module.
|
|
The tests are only run via unit tests, so that's where they should be.
|
|
|
|
With contributions from Håvard Graff
|
