summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@gnome.org>2021-07-29 11:22:05 +0100
committerChristoph Reiter <reiter.christoph@gmail.com>2021-09-19 18:10:09 +0000
commit792ab354932aca827f2bb541b6718b5be9bfbeee (patch)
treedd2baa4a9225f8de5509919652f4f0da4fdb80e3
parentdea457c0754550e210ab3cca9da8be1ae52d1d31 (diff)
downloadgobject-introspection-792ab354932aca827f2bb541b6718b5be9bfbeee.tar.gz
Do not error out for unknown scopes
If gobject-introspection adds a new scope that we do not handle, we should definitely not error out. Printing out a critical warning and asking to file an issue should be enough.
-rw-r--r--gi/pygi-closure.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/gi/pygi-closure.c b/gi/pygi-closure.c
index 136eec64..5504f241 100644
--- a/gi/pygi-closure.c
+++ b/gi/pygi-closure.c
@@ -620,8 +620,10 @@ end:
async_free_list = g_slist_prepend (async_free_list, closure);
break;
default:
- g_error ("Invalid scope reached inside %s. Possibly a bad annotation?",
- g_base_info_get_name (closure->info));
+ /* Handle new scopes added by gobject-introspection */
+ g_critical ("Unknown scope reached inside %s. Please file an issue "
+ "at https://gitlab.gnome.org/GNOME/pygobject/issues/new",
+ g_base_info_get_name (closure->info));
}
_invoke_state_clear (&state);