Sure thing. A big part of the workflow that we're developing depends on a variety of tools beyond just python packages. We've got things like dbt, prefect etc in the mix. Being able to specifically set up that set of tools for a project, as well as the right version of Python and sub dependencies like pip would be really helpful. A lot of these tools are easily installed with homebrew but then then issue is that they're global, and if you need version N for Project Y but Version N+1 for Project X then you're out of luck. Also as a sibling comment said i can use those some dependencies to build a container from.
I saw that you can layer environments when you activate, is it possible to have an env build on a another one/require another one? I'm thinking we'd have our standard company env which would have common utilities such as DBT or Gum installed but then we could easily layer over that with project specific dependencies.
You can definitely pin down the specific versions of all your dependencies per environment. And, you can for sure build one environment on top of another, you just have to activate them all (or include them in your project if you take a project based approach)
I saw that you can layer environments when you activate, is it possible to have an env build on a another one/require another one? I'm thinking we'd have our standard company env which would have common utilities such as DBT or Gum installed but then we could easily layer over that with project specific dependencies.