That’s an Ubuntu thing. They prefer you use apt to install deps, but you don’t absolutely need to. The PROPER way to work around this is starting a localized python virtual environment for your project directory. That is essentially sandboxing a python environment that only installs dependencies into the project directory and doesn’t alter your system globally.
Lots of instructions on the steps to do this out there that should get you going in just a few minutes.
OK thanks. I will look into that. The fact that they are installed in a “sandbox”… will that prevent them from being accessible to the decluttarr script?
I don’t understand a bit of this, but I got everything installed and running. Seems I have to ‘activate’ the venv and run the script from within it. Not sure how this works with the script auto running itself periodically, but I guess I will find out! Thanks for pointing me in the right direction.
I haven’t looked at the particulars of this applications, but if you path the python binary you use to run the application, it should use the environment that’s with it, without being activated. Activate just prepends the path for that venv to every command you give from then on when you’re working in a shell. And as noted in there, make sure you specify /bin/bash as your shell in cronjobs since it uses sh by default so you might run into issues in that context.
A virtual environment is just a copy of the python and pip binaries. When you activate the venv, the venv dirs temporarily get added to your path, so your regular python alias points to the binary in the venv (run which python with venv active to verify). Pip will install modules to a subdir of your venv.
It basically works like npm and the node_modules dir.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
That’s an Ubuntu thing. They prefer you use apt to install deps, but you don’t absolutely need to. The PROPER way to work around this is starting a localized python virtual environment for your project directory. That is essentially sandboxing a python environment that only installs dependencies into the project directory and doesn’t alter your system globally.
Lots of instructions on the steps to do this out there that should get you going in just a few minutes.
OK thanks. I will look into that. The fact that they are installed in a “sandbox”… will that prevent them from being accessible to the decluttarr script?
This happens inside whatever directory you have Decluttar in, and then the local venv runs decluttar
I don’t understand a bit of this, but I got everything installed and running. Seems I have to ‘activate’ the venv and run the script from within it. Not sure how this works with the script auto running itself periodically, but I guess I will find out! Thanks for pointing me in the right direction.
https://stackoverflow.com/questions/3287038/cron-and-virtualenv
I haven’t looked at the particulars of this applications, but if you path the python binary you use to run the application, it should use the environment that’s with it, without being activated. Activate just prepends the path for that venv to every command you give from then on when you’re working in a shell. And as noted in there, make sure you specify /bin/bash as your shell in cronjobs since it uses sh by default so you might run into issues in that context.
A virtual environment is just a copy of the python and pip binaries. When you activate the venv, the venv dirs temporarily get added to your path, so your regular python alias points to the binary in the venv (run
which pythonwith venv active to verify). Pip will install modules to a subdir of your venv. It basically works like npm and the node_modules dir.On second read, maybe you already knew that.