> we're migrating away from pip as a distribution mechanism for this reason
Could you elaborate on what you’re using as a replacement?
Could you elaborate on what you’re using as a replacement?
- clear separation of dev and production dependencies - lock file with the current version of all dependencies for reproducible builds (this is slightly difference than the dependency specification) - no accidental global installs because you forgot to activate a virtual environment - (not sure if supported by pip) allows installing libraries directly from a git repo, which is very useful if you have internal libraries - easier updates
1. curl script that installs dbt for end users
2. zipped snapshots for dbt Cloud, the SaaS hosted version of dbt
Eventually we want to create Docker images from 2, but we’re not there yet.