| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The scanner is chocking on the `__float80` and `__float128` types that
are provided by GCC as extensions to ISO/IEC TS 18661-3:2015:
https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html
Fixes: #384
|
|
|
|
|
| |
meson.source_root() return the root of the main project, but in this
case we want the root of the gobject-introspection (sub)project.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
docs: Remove mention of mailing lists
See merge request GNOME/gobject-introspection!261
|
| |
| |
| |
| | |
We don't use them any more; discussions happen on Discourse.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Fix syntax errors in gir-1.2.rnc
Closes #373
See merge request GNOME/gobject-introspection!256
|
|/
|
|
| |
Closes #373
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Ebassi/pre release
See merge request GNOME/gobject-introspection!260
|
| | |
|
|/
|
|
|
| |
The g_memdup() function has been deprecated, so we should use the new
g_memdup2() function if available.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
tests: Add "signals" test object
See merge request GNOME/gobject-introspection!259
|
|/
|
|
|
|
|
|
| |
It is worth to test marshalling of signal arguments, add
a basic (and barebones) object to add signals and emission
methods to, so bindings can test the signal handlers.
Related: https://gitlab.gnome.org/GNOME/gjs/-/issues/377
|
| |
|
| |
|
|
|
|
|
| |
The latest release (0.800) finds a handful of new problems that need
to be addressed first.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Require Python 3.6
See merge request GNOME/gobject-introspection!253
|
|/
|
|
| |
3.5 is EOL now and we'd like to use newer typing features
|
|\
| |
| |
| |
| | |
Add basic mypy support; Require Python 3.5
See merge request GNOME/gobject-introspection!251
|
| |
| |
| |
| |
| |
| | |
Silence some errors, run mypy in CI
Adding annotations to functions/classes will make mypy check them.
|
| |
| |
| |
| | |
3.4 is long EOL and we don't test it, so don't pretend that we support it.
|
|\ \
| | |
| | |
| | |
| | | |
giscanner: always define PY_SSIZE_T_CLEAN
See merge request GNOME/gobject-introspection!244
|
| | |
| | |
| | |
| | | |
This is required for Python 3.10 and always a good idea anyway.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Don't assume Py_TYPE being a macro
Closes #358
See merge request GNOME/gobject-introspection!243
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
It got changed to a function in Python 3.10. Use the Py_SET_TYPE macro
suggested at https://docs.python.org/3.10/whatsnew/3.10.html instead.
Fixes #358
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
open cleanup: explicit encoding, close fds
See merge request GNOME/gobject-introspection!250
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This means flushing changes and closing the fd. Otherwise this is done
by the GC eventually..
Detected using PYTHONTRACEMALLOC=1 PYTHONDEVMODE=1
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise we'll end up using the locale encoding. While it's usually utf-8,
that's not the case on Windows.
There is one place where a file with filenames is passed, not sure there
so I left it and passed a explicit None.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Remove LibtoolImporter
See merge request GNOME/gobject-introspection!249
|
|/ /
| |
| |
| |
| | |
From what I can see this was used for importing the C ext in an uninstalled
libtool build of g-i. We no longer use libtool, so this is no longer needed.
|
|\ \
| | |
| | |
| | |
| | | |
meson.build: exclude girepo_dep if introspection data is disabled
See merge request GNOME/gobject-introspection!248
|
|/ /
| |
| |
| | |
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
monkey patch distutils.cygwinccompiler.get_msvcr
See merge request GNOME/gobject-introspection!246
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Revert "giscanner: Fix section matching for documentation"
See merge request GNOME/gobject-introspection!241
|
|/
|
|
|
|
|
|
|
| |
This reverts commit de6512b31b614567bf1800406303d1ccfb6d9455.
This was causing naming conflicts when the SECTION documentation
was picked over the class documentation.
See https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/360
|
|
|
|
|
|
|
|
|
| |
os.path.relpath() will throw a ValueError when the two paths that
are fed to it are on different drives, at least when running under
cmd.exe consoles.
Fix this by falling back to the full path when this ValueError is
thrown.
|
|\
| |
| |
| |
| | |
gimarshallingtests: Add more tests for flags
See merge request GNOME/gobject-introspection!235
|
| |
| |
| |
| |
| |
| |
| |
| | |
If g_value_get_enum() or g_value_get_flags() is about to fail with a
precondition check failure, we can improve diagnostics by issuing
a more informative critical warning.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bindings sometimes need to handle flags and enums separately, so
everything that is tested for enums should ideally be tested separately
for flags.
Signed-off-by: Simon McVittie <smcv@debian.org>
|