Re: [gpsd-dev] Preferred method to install client libraries to python3

[Gary E. Miller]

Yo teyrana!

On Fri, 9 Feb 2018 08:01:45 -0500
teyrana <address@hidden> wrote:

>  A few questions about the install process for python3: which I can't
> seem to find, neither in buld.txt, nor SConstruct.

Look again.

"If 'scons' fails, it is possible that your target system has moved to
Python 3 as its default 'python' interpreter, but you can work around
it by saying "python2 /usr/bin/scons" or something similar."

> Is there an existing method to install the client libraries for
> python3?

Yeah, except for the above, just do the install as build.txt says to.

> If not, have y'all discussed what you'd like to see?

More testing would be good.  We try to write Python in a dialect that
works for Python2 and Python3.

> Options I'm trying:
> 
> 1) create pip package.  Install either locally, or via the pip repo.
> (Already prototyped)

That would be interesting.

> 2) install directly, like the python 2 variant.

That should work fine already.

> 3) link the package at the install directory editable package (I.e.
> "pip3 install -e . ")

Lost me?

> Also, are the .so files necessary for the pyrhon package, or just an
> optimization?

I'm not sure how the *py*so files fit in.  I just looked at the 
other binaries (gpsd, gpsctl, etc.) and they do not use them.  Easy
to delete them and see what happens...

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin

pgp75VgWvlRsa.pgp
Description: OpenPGP digital signature