"Mick" wrote: >> This will be gone. You should _not_ use threads at all. I will >> integrate a notifier loop allowing select, timer and stepping. >> > Yes, well.. I dont'mind being the first ot say that I will need some very > well documented examples on how *not* to use threading.. Its taken me long > enough to get to this stage ;-) > > Just to be sure.. we are talking about removing this feature right? > > class main_thread_name(threading.Thread):
Yes and no. You can still use threads, but you shouldn't. You need a _very_ good reason why. What will removed is the bad hack how to start processes from threads, that is a very bad hack. About not using threads: there will be a doc how to create a plugin like yours without threads. The cdbackup plugin will be such an example. What you do is waiting for an event (child dies). Why use a thread? Better use a callback: "call this function if that child dies". Dischi -- I just got lost in thought... It was unfamiliar territory. ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
