On 12/18/2014 04:16 AM, Mark Summerfield wrote:
> It looks to me that what you are doing is sharing a single core
> between your GUI and your processing. Threading isn't usually a good
> approach to Python concurrency that is CPU-bound.
Except that his code was not CPU-bound to begin with. His re
On Thursday, December 11, 2014 4:53:04 AM UTC, iMath wrote:
> I think the user interface shouldn't be freezed when using
> concurrent.futures.ThreadPoolExecutor here,as it executes asynchronously ,
> but it doesn't meet my expectations,anyone can explain why ? any other
> solutions here to not l
Chris Angelico :
> And I don't remember how Java did things, except that I struggled to
> find basic fundamental primitives like semaphores, and had to use
> synchronized functions/objects instead.
Java now has a diverse set of synchornization facilities, but the
builtin object synchronization pr
On Fri, Dec 12, 2014 at 6:18 PM, Marko Rauhamaa wrote:
> GUI developers have been doing event-driven programming for decades.
> That's an excellent preparation for network programming as well.
> Unfortunately, the minds of a generation of programmers were
> contaminated by the thread craze of the
Michael Torrie :
> An asynchronous API lets you start long-running I/O calls and define a
> function that is automatically called upon completion. In other words
> it's event-driven. Qt may provide everything you need already in an
> asynchronous form.
GUI developers have been doing event-driven
On 12/11/2014 08:20 PM, iMath wrote:
> 在 2014年12月11日星期四UTC+8下午1时25分41秒，Michael Torrie写道：
>> On 12/10/2014 09:52 PM, iMath wrote:
> "when it comes to I/O and GUIs, asynchronous calls are always better than
> threads."
>
> I cannot grasp your meaning here, IMO, asynchronous calls are done by using
在 2014年12月11日星期四UTC+8下午1时25分41秒，Michael Torrie写道：
> On 12/10/2014 09:52 PM, iMath wrote:
> > I think the user interface shouldn't be freezed when using
> > concurrent.futures.ThreadPoolExecutor here,as it executes
> > asynchronously , but it doesn't meet my expectations,anyone can
> > explain why ?
On 12/10/2014 09:52 PM, iMath wrote:
> I think the user interface shouldn't be freezed when using
> concurrent.futures.ThreadPoolExecutor here,as it executes
> asynchronously , but it doesn't meet my expectations,anyone can
> explain why ? any other solutions here to not let user interface
> freeze
I think the user interface shouldn't be freezed when using
concurrent.futures.ThreadPoolExecutor here,as it executes asynchronously ,
but it doesn't meet my expectations,anyone can explain why ? any other
solutions here to not let user interface freezed?
code is here
http://stackoverflow.com/qu
