Using a specific python environment in the aider shell

[ferrants]

Issue

Hi! Thanks for Aider, cool project!

I'm trying to use aider with a python project and if if it suggests I need a package or if it tries to run, it uses the same environment that aider is installed in, the one in ~/.local/bin. If I explicitly tell it to activate the local virtualenv, it does that and uses it as I'd expect it to, but I'm wondering if there's something wrong I'm doing with aider that is getting me in this situation. I end up doing /run . ./my_env/bin/activate; pytest tests/ or saying "activate the my_env virtualenv and install that package.

Is there a good way to specify the environment that the aider uses in a /run command or when it proposes a shell command?

Thanks in advance!

Version and model info

No response

[paul-gauthier]

Thanks for trying aider and filing this issue.

No matter which aider you run, it should use the active shell environment for /run commands.

What OS and shell? What version of aider?

[ferrants]

it should use the active shell environment for /run commands.

I think this is my issue or what i need to sort out better. I have aider installed via aider-install and i don't want aider installed in the same env as my app because aider won't be deployed to my prod env.

On linux, aider 0.70.0

[github-actions]

I'm labeling this issue as stale because it has been open for 2 weeks with no activity. If there are no additional comments, I will close it in 7 days.

Note: A bot script made these updates to the issue.