| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Python 3.8 no longer uses PATH for searching DLLs so we have to
add them manually.
Note that unlike PATH add_dll_directory() has no defined order,
so if there are two same DLLs in PATH we might get a random one.
This only makes sure that 'setup.py test' and 'pytest' continue working.
If you include pygobject manually you have to call os.add_dll_directory()
yourself with the location of the DLLs you ship.
|
| |
|
|
|
|
| |
If it triggers it creates a blocking GUI dialog without any helpful output.
I can't reproduce the cause on my local machine, just on the CI server, so
jsut disable this for now.
|
| |
|
|
|
|
|
| |
gtk4 calls get_dbus_object_path() on the default app and glib leaves
invalid GApplication instances as default in various places. It's hard
to track where a new default instances gets set, so just disable a11y
in the test suite for now.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This was required for Python 2 where Python didn't import our built modules
in the build dir because there is no __init__.py. In Python 3 this just works.
Tested with setup.py/pytest/meson
|
| | |
|
| |
|
|
|
| |
Otherwise we get "Couldn't register with accessibility bus" warnings which break the
tests.
|
| |
|
|
|
|
|
| |
This contains the minimum changes needed to get the tests to pass using our
docker image which contains a build gtk master from today.
This also makes the gtk4 CI job fatal so we don't regress in this area.
|
| |
|
|
|
|
|
| |
In case tests are run on a headless system without xvfb then the gtk
import will succeed but it will crash in the first gdk/gtk test.
Error out early instead.
|
| |
|
|
|
| |
The Ubuntu 18.10 theme has css errors which make the gtk tests
fail.
|
| | |
|
| |
|
|
|
|
|
|
| |
It imports the modules directly and puts them in sys.modules under the full
name. gi._gi_cairo was missing which made it import the system version
(because the gi package is registered as a namespace package).
Handle gi._gi_cairo there as well.
|
| | |
|
| | |
|
| | |
|
|
|
pytest will just import the files passed to it and try to run tests.
Since we need to run some setup code convert the tests directory to
a Python package and do the initialization in __init__.py. This makes
the init code (env vars, typelib search path, dbus) always run when
something from the package gets imported.
python3 setup.py build_tests # build pygobject and tests
py.test-3 tests/test_gi.py # run tests in test_gi.py only
|
