How to expose packages built with this tool on PYTHONPATH

[Eric Riff]

Hi Team,

I've recently started looking into this tool. It is really interesting. I've read the docs but some points are still unclear to me.

I've used cookiecutter with the debianized-pypi-mold template to repackage numpy as a deb package.
Once I got the deb package, I installed it. It ended up on the /opt/venvs/numpy folder as the docs say it would. But this is not one of the default paths where python looks for packages (I'm guessing this is by design).
I'm wondering how are we supposed to expose these packages to python. Are we expected to set PYTHONPATH accordingly? Or source the activate sctipts from the venvs? If we're supposed to do the later, would it work if I install multiple python packages this way?
Maybe use one of those rules that create a simlink to expose packaged executables in PATH?
Looking for some guidance here.

Thanks for the amazing tool.

Eric.

[Jyrki Pulliainen]

Hello! Thanks for your question. What you describe is actually not possible with dh-virtualenv. The package that is built is meant to be a self-contained Python virtualenv, not as such a library that gets installed. While it is entirely possible that it could work, it is however not guaranteed nor supported. If you want to take the advantage of dh-virtualenv I recommend packaging your whole application with it, not just a dependency.

On Sat 5. Mar 2022 at 2.00, Eric Riff ***@***.***> wrote: Hi Team, I've recently started looking into this tool. It is really interesting. I've read the docs but some points are still unclear to me. I've used cookiecutter with the debianized-pypi-mold template to repackage numpy as a deb package. Once I got the deb package, I installed it. It ended up on the /opt/venvs/numpy folder as the docs say it would. But this is not one of the default paths where python looks for packages (I'm guessing this is by design). I'm wondering how are we supposed to expose these packages to python. Are we expected to set PYTHONPATH accordingly? Or source the activate sctipts from the venvs? If we're supposed to do the later, would it work if I install multiple python packages this way? Maybe use one of those rules <https://github.com/spotify/dh-virtualenv/blob/master/doc/howtos.rst#making-executables-available> that create a simlink to expose packaged executables in PATH? Looking for some guidance here. Thanks for the amazing tool. Eric. — Reply to this email directly, view it on GitHub <#345>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPRSE5VSAWUXVTIKSZ4DDU6KP2TANCNFSM5P63GTNA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- - Jyrki

[Eric Riff]

I see. Thanks!