|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
[PATCH] WORKAROUND: let gobject.MainLoop() construct its own default contextWorks around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580791
which is present in pygobject < 2.28 --- zeroinstall/support/tasks.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zeroinstall/support/tasks.py b/zeroinstall/support/tasks.py index e03ceaa..f97121f 100644 --- a/zeroinstall/support/tasks.py +++ b/zeroinstall/support/tasks.py @@ -363,7 +363,7 @@ def wait_for_blocker(blocker): wait_for_blocker.loop.quit() Task(quitter(), "quitter") - wait_for_blocker.loop = gobject.MainLoop(gobject.main_context_default()) + wait_for_blocker.loop = gobject.MainLoop() try: debug(_("Entering mainloop, waiting for %s"), blocker) wait_for_blocker.loop.run() -- 1.7.10.2 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Zero-install-devel mailing list Zero-install-devel@... https://lists.sourceforge.net/lists/listinfo/zero-install-devel |
|
|
Re: [PATCH] WORKAROUND: let gobject.MainLoop() construct its own default contextOn 3 June 2012 23:51, Dave Abrahams <dave@...> wrote:
> Works around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580791 > which is present in pygobject < 2.28 The patch seems reasonable, but what triggers this? According to the bug, importing gobject first solves the problem, and we do that right at the start of zeroinstall/__init__.py. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Zero-install-devel mailing list Zero-install-devel@... https://lists.sourceforge.net/lists/listinfo/zero-install-devel |
|
|
Re: [PATCH] WORKAROUND: let gobject.MainLoop() construct its own default contexton Mon Jun 04 2012, Thomas Leonard <talex5-AT-gmail.com> wrote: > On 3 June 2012 23:51, Dave Abrahams <dave@...> wrote: >> Works around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580791 >> which is present in pygobject < 2.28 > > The patch seems reasonable, but what triggers this? According to the > bug, importing gobject first solves the problem, and we do that right > at the start of zeroinstall/__init__.py. What can I tell you? It started failing for me on Windows, and the prior import of gobject didn't save me (Python crashed). I can't explain it any more deeply, I'm afraid. -- Dave Abrahams BoostPro Computing http://www.boostpro.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Zero-install-devel mailing list Zero-install-devel@... https://lists.sourceforge.net/lists/listinfo/zero-install-devel |
|
|
Re: [PATCH] WORKAROUND: let gobject.MainLoop() construct its own default contextOn 4 June 2012 16:48, Dave Abrahams <dave@...> wrote:
> > on Mon Jun 04 2012, Thomas Leonard <talex5-AT-gmail.com> wrote: > >> On 3 June 2012 23:51, Dave Abrahams <dave@...> wrote: >>> Works around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580791 >>> which is present in pygobject < 2.28 >> >> The patch seems reasonable, but what triggers this? According to the >> bug, importing gobject first solves the problem, and we do that right >> at the start of zeroinstall/__init__.py. > > What can I tell you? It started failing for me on Windows, and the > prior import of gobject didn't save me (Python crashed). I can't > explain it any more deeply, I'm afraid. OK, thanks - I've applied the patch. -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Zero-install-devel mailing list Zero-install-devel@... https://lists.sourceforge.net/lists/listinfo/zero-install-devel |
| Free embeddable forum powered by Nabble | Forum Help |