On Jul 11, 2012, at 4:48 AM, [email protected] wrote: > Message: 1 > Date: Tue, 10 Jul 2012 19:31:09 -0500 > From: Chris Hare <[email protected]> > To: [email protected] > Subject: Re: [Tutor] advice on global variables > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > > On Jul 10, 2012, at 6:24 PM, Alan Gauld wrote: > >> On 11/07/12 00:16, Alan Gauld wrote: >> >>>> One thought was a RAM based SQLite database, but that seems >>>> like a lot of work. I dunno, maybe that is the option. >>> >>> is definitely the best option where the "global" needs to be shared >>> across different programs as well as different modules in a single >> >> I meant to add its also the right technique where the 'global' value has to >> persist between different execution cycles of the program. (Or indeed any >> kind of value needs to persist across execution cycles!) >> > > Thanks Alan -- I am thinking I am just gonna go with the RAM based SQLite > database ?.
Another option you might want to consider is the y_serial module [1] as it's a lot less work and allows you to **keep** thinking in python :>) Take care, Don [1] http://yserial.sourceforge.net/
_______________________________________________ Tutor maillist - [email protected] To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
