diff options
| author | Emmanuele Bassi <ebassi@gnome.org> | 2021-07-29 11:22:05 +0100 |
|---|---|---|
| committer | Christoph Reiter <reiter.christoph@gmail.com> | 2021-09-19 22:16:45 +0200 |
| commit | b19ccc41340238ce1e60fd702988609e41eafb4a (patch) | |
| tree | fdc2e84028913b9b366d36d10198555aff0c5aa8 | |
| parent | f4350ea8c1a752791517b8093778ede51b11b26c (diff) | |
| download | pygobject-b19ccc41340238ce1e60fd702988609e41eafb4a.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.c | 6 |
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); |