[pyclutter] Do not initialize Clutter on import



commit 1c51264334209458b2b0b9500d3cf6375da6b6c6
Author: Emmanuele Bassi <ebassi gnome org>
Date:   Thu Apr 30 12:59:25 2015 +0100

    Do not initialize Clutter on import
    
    It's a stupid thing to do, that we mutuated from pygtk. It was a stupid
    convenience then, it's even more stupid now. We have a bunch of API that
    is supposed to be called before initializing Clutter, but how can we
    call it, if Clutter is initialized on import?

 gi/overrides/Clutter.py |    7 -------
 1 files changed, 0 insertions(+), 7 deletions(-)
---
diff --git a/gi/overrides/Clutter.py b/gi/overrides/Clutter.py
index 2967202..e9076a8 100644
--- a/gi/overrides/Clutter.py
+++ b/gi/overrides/Clutter.py
@@ -1294,10 +1294,3 @@ def main_quit(*args, **kwargs):
     Clutter.main_quit()
 
 __all__.append('main_quit')
-
-
-# Initialize Clutter directly on import
-initialized, argv = Clutter.init(sys.argv)
-sys.argv = argv
-if not initialized:
-    raise RuntimeError("Could not initialize Cluttter")


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