| Age | Commit message (Collapse) | Author |
|---|
|
We check to see if a test extension exists, and if so add its path to
sys.path... immediately before unconditionally importing it, obviously.
This raises the question: why bother checking? Can it ever fail? What if
it does fail, do we simply not add path entries and then expect the rest
of the test file to work??? The whole thing seems silly and useless.
In fact it can fail, if the python interpreter and/or standard library
is broken. This is the case for the initial release of PyPy 3.11, in
which `'*tachyon*'` fails to glob correctly (and `'tachyon*'` would
work, funnily enough -- this is valid too for our use case although
still just as pointless).
Delete the useless check. It's technically correct to delete it, and it
*also* works around the PyPy breakage as a bonus.
Closes: https://github.com/mesonbuild/meson/issues/14307
|
|
Since CPython 3.8 .pyd files no longer look in PATH for loading libraries,
but require the DLL directory to be explicitely added via os.add_dll_directory().
This resulted in those tests failing with 3.8+ on Windows.
Add the DLL build directory with os.add_dll_directory() to fix them.
This was never noticed in CI because it only uses Python 3.7 and the
MSYS2 CPython still used the old behaviour until now.
|
|
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 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.
|
