4 ms·
Aider has a big problem when working with python codebase. 1. Its dependencies will conflict with your code requirements. 2. If you don't install it within th
by wanderingmind 3y ago
Aider has a big problem when working with python codebase.
1. Its dependencies will conflict with your code requirements.
2. If you don't install it within the code environment, you can use `aider run` where you can run local commands and pipe their outputs.
3. You will need to use all it's dependencies even in prod environment that can increase the attack surface.
So until they introduce a global binary install, I suggest using Plandex which is based on Go and can work across any environment within the system
- anotherpaulg 3y agoThanks for trying aider, and sorry to hear you had dependency conflicts. You can install aider with pipx to avoid this. There's a FAQ entry that explains how: https://aider.chat/docs/faq.html#how-to-use-pipx-to-avoid-python-package-conflicts https://aider.chat/docs/faq.html#how-to-use-pipx-to-avoid-py... Also, why would you want to install aider in a production environment? It's a development tool, I wouldn't expect anyone to use it in prod. But maybe there's a use case I'm not thinking of?
- stavros 3y agoThis is the correct solution, use pipx to install any Python cli and save yourself a ton of hassle.
- wanderingmind 3y agoThank you, didn't know about pipx possibility. Will give it a shot. I don't want aider in prod environment. Im saying its hard to remove it from prod if we can't isolate it from code dependencies as its hard to maintain multiple requirements.txt for different envs.
- bumbledraven 3y agoThat is a problem with the Python packaging ecosystem in general, not with aider. @BiteCode_Dev wisely advises beginners to use virtual environments to install anything that uses Python: https://www.bitecode.dev/p/back-to-basics-with-pip-and-venv https://www.bitecode.dev/p/back-to-basics-with-pip-and-venv