Packaging a python module when already using cmake buildsystem

Hi, I'm trying to package a newly added python component of our tool https://tracker.debian.org/pkg/armnn. It has a setup.py and uses SetupTools and DistUtils so I was hoping to add "--with Python3" and hope that a lot of magic would be done by pybuild. However as I'm already using cmake as the

Packaging a python module when already using cmake buildsystem

Hi, I'm trying to package a newly added python component of our tool https://tracker.debian.org/pkg/armnn. It has a setup.py and uses SetupTools and DistUtils so I was hoping to add --with Python3 and hope that a lot of magic would be done by pybuild. However as I'm already using cmake as the b

Re: Packaging a python module when already using cmake buildsystem

> > It has a setup.py and uses SetupTools and DistUtils so I was hoping to > > add --with Python3 and hope that a lot of magic would be done by pybuild. > > However as I'm already using cmake as the build system I can't stick > > pybuild in there. > > We use both pybuild and cmake for a couple of

Update PYTHONPATH after install

Hi, My understanding of Debian policy means python3 modules should be installed in /usr/lib/python3/dist-packages/ Once the package installs there how is the PYTHONPATH meant to be updated so that user can import the module into the python3 interpreter? As the PYTHONPATH would normally look in

Multiple package versions in PPA

Hi, I've added a python package called python3-pyarmnn to Debian (https://tracker.debian.org/pkg/armnn) but also have it pushed to a Ubuntu Launchpad PPA (https://launchpad.net/~armnn/+archive/ubuntu/ppa/+packages). When I push new versions of the packaging it seems to overwrite the previous,