Le 23/01/19 à 13:11, Neal Becker a écrit :
dieter wrote:
Vincent Vande Vyvre writes:
.
To load external C/C++ shared objects, the dynamic lickage loader
(ldd) is used. "ldd" does not look at Pthon's "sys.path".
Unless configured differently, it looks at standard places
(such as "/usr/l
dieter wrote:
> Vincent Vande Vyvre writes:
>> I am working on a python3 binding of a C++ lib. This lib is installed
>> in my system but the latest version of this lib introduce several
>> incompatibilities. So I need to update my python binding.
>>
>> I'm working into a virtual environment (py37
Vincent Vande Vyvre writes:
> I am working on a python3 binding of a C++ lib. This lib is installed
> in my system but the latest version of this lib introduce several
> incompatibilities. So I need to update my python binding.
>
> I'm working into a virtual environment (py370_venv) python-3.7.0 i
(Resend because the previous message was incomplete)
Hi,
I am working on a python3 binding of a C++ lib. This lib is installed in
my system but the latest version of this lib introduce several
incompatibilities. So I need to update my python binding.
I'm working into a virtual environment (
I'm working into a virtual environment (py370_venv) python-3.7.0 is
installed into .localpythons/lib/python3.7
So, the paths are:
# python-3.7.0
~/.localpythons/lib/python3.7/
# my binding python -> libexiv2
~/.localpythons/lib/python3.7/site-packages/pyexiv2/*.py
~/.localpythons/lib/python3.7/s
