Challenges with Installing Python Packages in Virtual Environments

You seem to be doing all the right things but it's clear there’s some confusion with how virtual environments work. Typically, after activating a virtual environment, running `pip install -e .` will install the package directly in that venv's local `site-packages`, not in `pyenv`'s global `shims/` directory. If they’re seeing shims trying to go to `/opt/pyenv/shims`, it might mean they aren’t activating the environment properly or are somehow bypassing it. They should see a noticeable change in their prompt after activating—like it showing the environment name. If you're still struggling, consider setting up a requirements file or using a tool like Poetry, which can help manage dependencies and virtual environments more seamlessly. It’s worth investing some time in teaching the team how to properly use these tools; it'll pay off in the long run.

It sounds like you’re running into a common issue with global package installations. First off, you definitely want to avoid installing packages globally in environments where users don’t have admin rights. The best practice here would be to use a virtual environment that encapsulates the dependencies needed for the project without messing with global paths. Make sure the developers activate the virtual environment before running any install commands. They can do this by going to the project root and using the `.venv/bin/activate` script. This ensures that the packages install correctly within their environment without needing write access to any global folders. If they keep hitting issues, double-check that the paths to the virtual environment are set correctly and that they’re not inadvertently trying to run commands from outside their activated environment.