Why This Matters
The first setup step sets the tone for the rest of the experience. If installation is messy, everything after it gets harder. If it is clean, you get to the part that actually matters much faster.This page covers two install paths:
uv if you want the shortest route, and pip if you prefer a standard virtual environment workflow.How To Install Bindu
You can install Bindu withuv or pip. uv is the recommended path.
Using uv (Recommended)
Recommended Path
uv is the shortest way to add Bindu and keep dependency management simple.Standard Path
If your workflow already uses
pip and virtual environments, that still works fine.The Setup Flow
Use pip
If you want a traditional virtual environment setup, create one first and then install Bindu.
Contributing
If you want to work on Bindu itself, set up the development environment from the repository.git clonegets the source locallycd Bindumoves into the repositoryuv syncinstalls the development dependenciespre-commit run --all-filesruns the configured code-quality checks
See our Contributing Guidelines for more details.
Practical Notes
When should I use uv?
When should I use uv?
Use
uv if you want the recommended path and a shorter setup flow:When should I use pip?
When should I use pip?
Use
pip if your local workflow already depends on a standard Python virtual environment.What should I do if pip fails?
What should I do if pip fails?
Update
pip first and try again:How do I set up the repo for development?
How do I set up the repo for development?
Clone the repository, sync dependencies, and run the pre-commit checks:
Related
- /bindu/introduction/what-is-bindu
- /bindu/introduction/join-the-internet-agents
- https://github.com/getbindu/Bindu/blob/main/.github/contributing.md