Re: Python libmm problems

2017-09-15 Thread Aleksander Morgado
>> > Though this is coming together nicely now, I don't need the script to run >> > forever once it's done its stuff. Is there a way send a HUP/TERM to itself? >> >> You can always quit the GLib main loop and exit cleanly. >> > > Oh yeah, sorry that was probably a bit of an obvious questio

Re: Python libmm problems

2017-09-15 Thread Colin Helliwell
> On 15 September 2017 at 16:46 Aleksander Morgado > wrote: > > > > > > Though this is coming together nicely now, I don't need the script to run > > forever once it's done its stuff. Is there a way send a HUP/TERM to itself? > > You can always quit the GLib main loop and exit cleanly. > O

Re: Python libmm problems

2017-09-15 Thread Aleksander Morgado
> > Though this is coming together nicely now, I don't need the script to run > forever once it's done its stuff. Is there a way send a HUP/TERM to itself? You can always quit the GLib main loop and exit cleanly. -- Aleksander https://aleksander.es __

Re: Python libmm problems

2017-09-15 Thread Colin Helliwell
> On 14 September 2017 at 17:11 Dan Williams wrote: > > On Thu, 2017-09-14 at 15:35 +0100, Colin Helliwell wrote: > .. > > Thanks Dan. I've persevered with GLib, and made a bit of progress. > > On top of your suggestion - instead of the start-up "modems = > > manager.get_objects()" etc, I've ho

Re: Python libmm problems

2017-09-14 Thread Colin Helliwell
> On 14 September 2017 at 17:11 Dan Williams wrote: > > On Thu, 2017-09-14 at 15:35 +0100, Colin Helliwell wrote: > .. > > Thanks Dan. I've persevered with GLib, and made a bit of progress. > > On top of your suggestion - instead of the start-up "modems = > > manager.get_objects()" etc, I've ho

Re: Python libmm problems

2017-09-14 Thread Dan Williams
On Thu, 2017-09-14 at 15:35 +0100, Colin Helliwell wrote: > > On 13 September 2017 at 19:39 Dan Williams wrote: > > > > ... > > > > The two major patterns for doing all of this are (a) threads and > > (b) > > event-driven programming. GLib is an example of (b), and it really > > does remove the

Re: Python libmm problems

2017-09-14 Thread Colin Helliwell
> On 13 September 2017 at 19:39 Dan Williams wrote: > ... > > The two major patterns for doing all of this are (a) threads and (b) > event-driven programming. GLib is an example of (b), and it really > does remove the error-prone issues of lock management, concurrent data > access, and deadlock

Re: Python libmm problems

2017-09-13 Thread Dan Williams
On Wed, 2017-09-13 at 18:41 +0100, Colin Helliwell wrote: > > On 13 September 2017 at 17:57 Dan Williams wrote: > > > > On Wed, 2017-09-13 at 17:23 +0100, colin.helliw...@ln-systems.com > > wrote: > > > > > I'm trying to write some python to get the operator id off the > > > modem. > > > Due to

Re: Python libmm problems

2017-09-13 Thread Colin Helliwell
> On 13 September 2017 at 17:57 Dan Williams wrote: > > On Wed, 2017-09-13 at 17:23 +0100, colin.helliw...@ln-systems.com > wrote: > > > I'm trying to write some python to get the operator id off the > > modem. > > Due to limited knowledge of such things, I'm *not* using any > > notifcation > >

Re: Python libmm problems

2017-09-13 Thread Dan Williams
On Wed, 2017-09-13 at 17:23 +0100, colin.helliw...@ln-systems.com wrote: > I'm trying to write some python to get the operator id off the > modem.  > Due to limited knowledge of such things, I'm *not* using any > notifcation > callbacks etc, but simply trying to poll things. > I've wrapped the func

Python libmm problems

2017-09-13 Thread colin.helliwell
I'm trying to write some python to get the operator id off the modem. Due to limited knowledge of such things, I'm *not* using any notifcation callbacks etc, but simply trying to poll things. I've wrapped the functionality into a class (thinking to thus be able to easily contain the modem's object