[pygobject/unknown-scope] Do not error out for unknown scopes




commit 1ff67e900ee5dd2af98a7834f63965b977892de1
Author: Emmanuele Bassi <ebassi gnome org>
Date:   Thu Jul 29 11:22:05 2021 +0100

    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.

 gi/pygi-closure.c | 6 ++++--
 1 file 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);


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]