On Tue, 2010-11-16 at 16:29 -0800, RSGames Support wrote:
> Hi,
> I have found something interesting. When I do not call sys.exit(), and just
> call this: reactor.callFromThread(reactor.stop), the program exits properly.
> I was wondering if it was safe to not call sys.exit()? If so I think the
age-
> From: rsga...@inbox.com
> Sent: Tue, 16 Nov 2010 10:00:50 -0800
> To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> Hi,
> Thank you for the suggestion. Unfortunately, I still have this problem
> when I call the reactor.callFromThread
nal Message-
> From: ita...@itamarst.org
> Sent: Mon, 15 Nov 2010 23:12:09 -0500
> To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> On Mon, 2010-11-15 at 19:28 -0800, RSGames Support wrote:
>> Hi,
>> I have created a simpl
On Mon, 2010-11-15 at 19:28 -0800, RSGames Support wrote:
> Hi,
> I have created a simple demo (one .py file) to show the problem without the
> entire application. You can download it here: http://bit.ly/a2TTlT
And, if you switch reactor.stop() with
reactor.callFromThread(reactor.stop) you still
On 03:28 am, rsga...@inbox.com wrote:
>Hi,
>I have created a simple demo (one .py file) to show the problem without
>the entire application. You can download it here: http://bit.ly/a2TTlT
>
>Thank you for any help in advance.
Linux (Ubuntu 9.10)
Python 2.6.4
Twisted tr...@30276
wxPython 2.8.10.1-
To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> Hi,
> I made a mistake in my previous message, this issue is on Windows, Linux
> and Mac. One of my testers gave me incorrect information.
edmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> Hi,
> I think the best way to debug this is to give you all the source code.
> You can find it here: http://bit.ly/doEiEJ
>
> To give you all some background on this project: It is a freeware client
> that uses
ac.
Thank you.
> -Original Message-
> From: ita...@itamarst.org
> Sent: Sun, 14 Nov 2010 14:02:56 -0500
> To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> On Sun, 2010-11-14 at 09:28 -0800, RSGames Support wrote:
>> Hi,
>> Well, I
this problem.
Thank you.
> -Original Message-
> From: ita...@itamarst.org
> Sent: Sun, 14 Nov 2010 14:02:56 -0500
> To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python] wxReactor Issues
>
> On Sun, 2010-11-14 at 09:28 -0800, RSGames Support wrote:
&
On Sun, 2010-11-14 at 09:28 -0800, RSGames Support wrote:
> Hi,
> Well, I close the application (by clicking the X). Then a few seconds later,
> Ubuntu comes up with a dialog asking me if I want to force quit the
> application. gdb reports the following when I force quit: Program terminated
> wi
x27;m almost positive it is because there are
two threads that aren't getting stopped properly.
Thank you.
> -Original Message-
> From: exar...@twistedmatrix.com
> Sent: Sun, 14 Nov 2010 05:29:45 -
> To: twisted-python@twistedmatrix.com
> Subject: Re: [Twisted-Python]
On Sun, 2010-11-14 at 05:29 +, exar...@twistedmatrix.com wrote:
> On 03:56 am, rsga...@inbox.com wrote:
> >Hello,
> >My Twisted Python application with wxReactor crashes every time the
> >user exits the application.
>
> What do you mean when you say "crashes"? A SIGSEGV is probably due to a
On 03:56 am, rsga...@inbox.com wrote:
>Hello,
>My Twisted Python application with wxReactor crashes every time the
>user exits the application.
What do you mean when you say "crashes"? A SIGSEGV is probably due to a
bug in CPython or (more likely) wxPython.
Jean-Paul
>The OnClose event calls a
= stopFromThread
reactor.stop()
When I ran this code in gdb, it did not say the two threads exited like they
should do.
Thank you.
-Ryan
> -Original Message-
> From: ita...@itamarst.org
> Sent: Sat, 13 Nov 2010 23:21:42 -0500
> To: twisted-python@twistedmatrix.com
> Subject: Re:
On Sat, 2010-11-13 at 19:56 -0800, RSGames Support wrote:
> if wxreactor.WxReactor.callFromThread is not None:
> oldStop = wxreactor.WxReactor.stop
> def stopFromThread(self):
> reactor.callFromThread(oldStop)
> wxreactor.WxReactor.stop = stopFromThread
Did you try the patch?
Hello,
My Twisted Python application with wxReactor crashes every time the user exits
the application. The OnClose event calls a method that does reactor.stop().
I've ran this through gdb, and have noticed that this is because 2 threads
aren't getting closed. What I find strange though, that is
16 matches
Mail list logo
