I'll elaborate on the venv thing later when I have more time to type.
We know you have /home/pi/.local/bin in your path at the front and at the back. Keeping both is not a problem, but if what you run is in that path, then it'll never need the second one. Unless you have something that you want to run from something in between them and it is also found in the ~/.local/bin. In that case you'd use the full path the executable so it would take it from ~/.local/bin or you'd remove ~/.local/bin from the front and leave the one at the back. But this is all how standard paths work.
For now, please post the contents of /home/pi/Documents/HVAC/run_dutycycles.sh
I need to take a look at it because the way I understood it is that you're not activating the venv and things work. But whatever is in that script or how it is calling python could explain that.
I'll check back later today.
We know you have /home/pi/.local/bin in your path at the front and at the back. Keeping both is not a problem, but if what you run is in that path, then it'll never need the second one. Unless you have something that you want to run from something in between them and it is also found in the ~/.local/bin. In that case you'd use the full path the executable so it would take it from ~/.local/bin or you'd remove ~/.local/bin from the front and leave the one at the back. But this is all how standard paths work.
For now, please post the contents of /home/pi/Documents/HVAC/run_dutycycles.sh
I need to take a look at it because the way I understood it is that you're not activating the venv and things work. But whatever is in that script or how it is calling python could explain that.
I'll check back later today.
Statistics: Posted by memjr — Thu Aug 01, 2024 1:20 pm
