Re: Signals and Slots - Summerfield - what exactly is a signal?

On Sun, 6 Aug 2017 03:18 am, Michael Torrie wrote: > Forgive Steven for his off-topic reply. I assume he's trying to goad you > into having a more specific subject line. He knows darn well what PyQt, > even if he has no experience with it. Pardon me, I said: "I don't know what Qt signals are."

Re: Signals and Slots - Summerfield - what exactly is a signal?

On 08/05/2017 08:28 AM, veek wrote: > At a certain point beyond the general stuff, questions about PyQt might be better suited to the PyQt mailing list, hosted by the company that maintains PyQt: https://www.riverbankcomputing.com/mailman/listinfo/pyqt -- https://mail.python.org/mailman/listi

Re: Signals and Slots - Summerfield - what exactly is a signal?

On 08/05/2017 12:19 PM, Marko Rauhamaa wrote: > I would express it as just saying that the Qt developers appropriated > the word "signal" for what is simply a callback. I'd say a slot is a callback. A signal is the designation of something that will trigger callbacks. > Years back I took a brief

Re: Signals and Slots - Summerfield - what exactly is a signal?

Le 05/08/17 à 16:28, veek a écrit : 1. What exactly is a signal. In hardware, an interrupt can be viewed as a signal and the voltage on a pin will suddenly jump to +5V as an indicator that an interrupt has occurred. With Qt signals - if a widget-c++ code has to 'signal' an event - what does it do

Re: Signals and Slots - Summerfield - what exactly is a signal?

Michael Torrie : > Basically a signal emission is a call to the main loop that indicates > that an event has occurred, and then the main loop sees if there are > any registered callbacks that want to be notified of this event, and > if so it calls them, letting them execute. This is how event-driv

Re: Signals and Slots - Summerfield - what exactly is a signal?

Forgive Steven for his off-topic reply. I assume he's trying to goad you into having a more specific subject line. He knows darn well what PyQt, even if he has no experience with it. And of course, as always you will want to post a complete, working example that we can see and comment on, rather

Re: Signals and Slots - Summerfield - what exactly is a signal?

Steve D'Aprano wrote: > On Sun, 6 Aug 2017 12:28 am, veek wrote: > >> 1. What exactly is a signal. In hardware, an interrupt can be viewed as a >> signal and the voltage on a pin will suddenly jump to +5V as an indicator >> that an interrupt has occurred. With Qt signals - if a widget-c++ code >>

Re: Signals and Slots - Summerfield - what exactly is a signal?

On Sun, 6 Aug 2017 12:28 am, veek wrote: > 1. What exactly is a signal. In hardware, an interrupt can be viewed as a > signal and the voltage on a pin will suddenly jump to +5V as an indicator > that an interrupt has occurred. With Qt signals - if a widget-c++ code has > to 'signal' an event - wha

Re: Signals and Threads in Python 3.5 or so

On Mon, Oct 10, 2016 at 12:05 AM, dieter wrote: > Dan Stromberg writes: >> I have a program http://stromberg.dnsalias.org/~dstromberg/looper/ >> that I use and maintain. >> >> It's like GNU parallel or similar - yet another "run n processes, m at >> a time" implementation. Interestingly, I've on

Re: Signals and Threads in Python 3.5 or so

Dan Stromberg writes: > I have a program http://stromberg.dnsalias.org/~dstromberg/looper/ > that I use and maintain. > > It's like GNU parallel or similar - yet another "run n processes, m at > a time" implementation. Interestingly, I've only used/tested it on > Linux, but it's under a Microsoft

Re: Signals and Threads in Python 3.5 or so

Dan Stromberg : > That bug is: if you control-C the top-level process, all the > subprocesses are left running. Sorry, don't have a solution for your particular Python situation. > I've been thinking about making it catch SIGINT, SIGTERM and SIGHUP, > and having it SIGKILL its active subprocesses

Re: Signals and Threads in Python 3.5 or so

Dan Stromberg writes: > That bug is: if you control-C the top-level process, all the > subprocesses are left running. Are you setting the daemon flag? -- https://mail.python.org/mailman/listinfo/python-list

Re: Signals and Threads in Python 3.5 or so

On Mon, Oct 10, 2016 at 10:52 AM, Dan Stromberg wrote: > That bug is: if you control-C the top-level process, all the > subprocesses are left running. > > I've been thinking about making it catch SIGINT, SIGTERM and SIGHUP, > and having it SIGKILL its active subprocesses upon receiving one of > th

Re: Signals/Slots support in Python

On Thu, 01 May 2008 08:44:27 -0600, Scott SA wrote: > Did you review this? > > > from what I understand is originally based upon this: > > > and subsequently integrated into this: >

Re: Signals/Slots support in Python

On 5/1/08, Brian Vanderburg II ([EMAIL PROTECTED]) wrote: >I don't know if any such support is already built in, so I ended up >making my own simple signals/slots like mechanism. If anyone is >interested then here it is, along with a simple test. It can connect to >normal functions as well as

RE: Signals

lp you can offer, its greatly appreciated. Rob -Original Message- From: Carsten Haese [mailto:[EMAIL PROTECTED] Sent: 18 April 2007 13:43 To: Robert Rawlins - Think Blue Cc: python-list@python.org Subject: Re: Signals On Wed, 2007-04-18 at 08:39 +0100, Robert Rawlins - Think Blue wrote: &

Re: Signals

On Wed, 2007-04-18 at 08:39 +0100, Robert Rawlins - Think Blue wrote: > Hello Chaps, > > > > I posted about this the other day but I’m still struggling to get any > form of result from it. Basically I have the following piece of code, > and according to its API is produces singals when particul

Re: Signals and threads again

On Fri, 13 Oct 2006 11:37:46 -0700 Mitko Haralanov <[EMAIL PROTECTED]> wrote: > The problem that I am experiencing is that when SIGINT is sent to the > program, it gets delivered to the child processes (the fork'ed ones) > but the main thread's signal handler is never invoked. > > I know that Pyt

Re: signals (again)

I found a good solution to this problem in Richard Steven's _Network_Programming_. It seems like everything shows up in Steven's books! Rather than pausing, you do a blocking read on a pipe. You only write to the pipe from within the signal handler. However, this brings up the better question:

Re: signals (again)

"bill" <[EMAIL PROTECTED]> writes: > I see this (or similar) question occasionally looking back through the > archive, but haven't yet seen a definitive answer, so I'm going to ask > it again. > > Consider the following: > > while True: > do_something_to_files_in_directory(fd) > fcntl(fd,

Re: signals (again)

How does that help? I interpret "use asynchronous calls" to mean "use fcntl to set an FN_NOTIFY on the directory in order to be alerted when something needs to be done." But the method of doing that which I outlined above has a critical section in which the incoming signal will not be noticed.

Re: signals (again)

"bill" <[EMAIL PROTECTED]> writes: > What's the pythonic thing to do here? How can I > guarantee timely response to the creation of a file in the directory > referenced by fd? Use asynchronous calls and/or a separate thread. -- http://mail.python.org/mailman/listinfo/python-list

Re: Signals and system

"T Koster" wrote: > Currently, I am using system (os.system) to run wget. The mechanism is > in a loop, so that it will try all the mirrors while wget is exiting > with a non-zero exit status. This is working fine as long as the user > feels there is no need to interrupt it. any reason you cann

Re: Signals and system

# [EMAIL PROTECTED] / 2005-04-10 20:55:05 +1000: > Hi folks, > > My python program needs to download a number of files. Each file comes > as a list of mirrors of that file. > > Currently, I am using system (os.system) to run wget. The mechanism is > in a loop, so that it will try all the mirr