[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] Python client bindings
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-users] Python client bindings |
Date: |
Fri, 27 Sep 2013 05:53:39 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Stoyan Haralampiev <address@hidden>:
> And now on the issues I found in *gps.py *that I mentioned. They're about
> variables that get initialized but never updated:
> 1) (line 106) self.status = STATUS_NO_FIX
> 2) (line 110) self.xdop = self.ydop = self.vdop = self.tdop = 0
> self.pdop = self.hdop = self.gdop = 0.0
>
> I remember I had some other issue but I don't remember it right now.
> Basically the above ones made me quite suspicious as to the quality of the
> python bindings and hence my question in the first email.
They're set all right, but in a sneaky way that would be difficult for
you to detect by grepping the code. The nagic is in client.py, in the
unpack method of the gpsjson class.
> Thanks and let me know if you need more details.
If you've detected any actual bugs in the bindings I certainly want to
know about it. You can test them by running xgps and cgps in parallel
and looking for divergences; cgps uses the C client bindings, xgps
uses the Python ones.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [gpsd-users] Python client bindings,
Eric S. Raymond <=