What would be the intended use? If this is for other Debian users, then why not make a Debian package? If it's for yourself, why do you need to automate it?
To be fair, I don't see a point in tools like pipx. Have never used it, and cannot imagine a scenario where I'd want to. It seems like there's always a better way to do what this tool alleges to be able to do... Also, you say that you want it in its own environment: then what difference does it make if it's on Debian or anywhere else? If you are distributing a library, it makes sense to incorporate it into the user's infrastructure. Either you do the integration, or let users decide how to best integrate it. If you provide them with the environment that they *must* use, that's going to be the worst of both worlds: users won't be able to use the library in the environment created by them, nor will this library integrate with the other libraries provided by the system. So, it's hard to imagine why your users would want that. On Sun, Jan 12, 2025 at 12:47 AM Chris Green via Python-list <python-list@python.org> wrote: > > Can one use pipx to wrap the process of creating an independent > environment for a python package as opposed to a runnable application? > > E.g. I want to install and use pksheet but, as it's not available from > the Debian repositories, I'll have to install it from PyPi. So I > should put it in its own environment. Can pipx help me with this? > > -- > Chris Green > · > -- > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
