# Venv conflicts with conda/ not picking up conda packages

**URL:** <https://community.crewai.com/t/venv-conflicts-with-conda-not-picking-up-conda-packages/1775>\
**Category:** CrewAI Community Support\
**Tags:** crewai\
**Created:** [December 2, 2024, 4:36pm UTC](https://community.crewai.com/t/venv-conflicts-with-conda-not-picking-up-conda-packages/1775 "2024-12-02T16:36:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![camole](https://sea1.discourse-cdn.com/flex025/user_avatar/community.crewai.com/camole/32/1244_2.png) [@camole](https://community.crewai.com/u/camole)\
**Post date:** [December 2, 2024, 4:36pm UTC](https://community.crewai.com/t/venv-conflicts-with-conda-not-picking-up-conda-packages/1775/1 "2024-12-02T16:36:45Z")

</div>

Previous discussion on similar topics has been found [here](https://community.crewai.com/t/default-crewai-virtual-environment-conflict-with-conda/1116/1) 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](https://github.com/astral-sh/uv/issues/1703)) therefore still making it difficult to manage some packages that is only conda installable.