Venv conflicts with conda/ not picking up conda packages

Previous discussion on similar topics has been found here and a workaround is kindly provided by the original poster.

However, I would like to continue the discussion along the topics:

  1. Why does crewai install or crewai run has to build its own .venv each time?
  2. Some packages we use for drug R&D has to be installed from conda and not pip. I saw that a few packages are not being picked up in the crewai install process. This means that I have to turn on include-system-site-packages every time.
  3. For some packages, the venv installed a different version than the version in my conda environment, which created issues for some functions. This can be addressed by manually configuring the pyproject.toml. However, it looks like currently uv does not have conda package support (see here) therefore still making it difficult to manage some packages that is only conda installable.