On Fri, Jan 02, 2015 at 12:39:36PM -0800, Joseph Lee wrote:
> Threads introduce interesting issues. For instance, due to Python's global
> interpreter lock (GIL), only one thread can run at a given time.
I'd like to make a technical correction here. The GIL is not a
*language* requirement, it is
On Fri, Jan 2, 2015 at 3:18 PM, Alan Gauld
wrote:
> On 02/01/15 20:17, Rance Hall wrote:
>
>> I bought myself a pcduino 3 nano development board for Christmas and
>> started picking up python again after a long forced hiatus. The board
>> runs
>> Ubuntu Precise
>>
>
> Snap!(ish), I got an arduin
half Of Rance Hall
> Sent: Friday, January 2, 2015 12:17 PM
> To: tutor
> Subject: [Tutor] threading in python2.7
>
> Each of the lights and sound functions are placed in a "while not
> exitFlag:"
> loop
>
> I think I'm running into some variable scoping issues
Hi,
Answers are below.
-Original Message-
From: Tutor [mailto:tutor-bounces+joseph.lee22590=gmail@python.org] On
Behalf Of Rance Hall
Sent: Friday, January 2, 2015 12:17 PM
To: tutor
Subject: [Tutor] threading in python2.7
Each of the lights and sound functions are placed in a "
On 02/01/15 20:17, Rance Hall wrote:
I bought myself a pcduino 3 nano development board for Christmas and
started picking up python again after a long forced hiatus. The board runs
Ubuntu Precise
Snap!(ish), I got an arduino Uno and RaspberryPi.
As I understand it the pcDuino is just a PC and
I bought myself a pcduino 3 nano development board for Christmas and
started picking up python again after a long forced hiatus. The board runs
Ubuntu Precise
Working with development boards has me navigating the inner working of
python threading and I find myself at a loss.
My current project i
