Resolution of the library-path mess

[Hal Murray]

>> Do we need a way to check that we are using the right library?

>> I think that means we need the version string or time stamp in both the 
>> library and the code that uses the library with a simple sanity check at 
the
>> top of the uses code.

> It's not normal practice to do this in Python. GPSD never has.

> I think the reason is that when you do have such a mismatch, the Python
> stack trace it generally produces is likely to be more informative than
> a version-mismatch message.

Given the confusion we have had in this area, it seemed like a simple and low 
cost way to avoid what might turn into a long chase.  Sure, if you get a 
messy backtrace you can probably figure out that you have the wrong library.  
But what if it doesn't crash and just gives the wrong answer?

-- 
These are my opinions.  I hate spam.