Skip to content

Support Alternative Package Managers (Conda/UV) in Python Virtual Environments #4317

Open

Description

@SarahAsad23

Task Summary

Currently, package installation within Python Virtual Environments is handled exclusively through pip. However, some users rely on alternative package managers such as Conda or UV for better dependency resolution, performance, or compatibility with specific libraries.

To improve flexibility and usability, the system should allow users to select their preferred package manager (pip, Conda, or UV) when configuring a Python Virtual Environment. Based on the selected option, the environment setup and dependency installation process should use the corresponding package manager while maintaining compatibility with the system’s execution requirements.

Priority

P2 – Medium

Task Type

  • Code Implementation
  • Documentation
  • Refactor / Cleanup
  • Testing / QA
  • DevOps / Deployment

Activity

  1. added theissue type on Mar 18, 2026
  2. Yicong-Huang commented on Apr 21, 2026

    @Yicong-Huang
    Contributor

    I am hesitate to allow users to choose their own env and package managing tools. It simply adds complexity to our end.

    I strongly suggest we keep with pip for simplicity for now. I've heard UV is pretty good, but still under testing (haven't released their 1.0 version). Conda is a bit heavy.

  3. SarahAsad23 commented on Apr 21, 2026

    @SarahAsad23
    ContributorAuthor

    I agree with you, It does introduce complexity. One of our collaborators in the scientific community uses Conda for package installation to meet certain GPU specific requirements, which is why this feature was requested. We have not yet discussed the idea in depth.

  4. Yicong-Huang commented on Apr 22, 2026

    @Yicong-Huang
    Contributor

    conda is env + package management. pyenv + pip should be able to support the same experience. But after some research they each have different coverage:

    • pip installs from PyPI and focuses on Python packages.
    • conda installs from conda channels and can provide Python, C/C++ libs, runtimes, CUDA-related pieces, and other non-Python dependencies together.

    But on python libraries, many more packages are pip/PyPI-only than conda-only. PyPI is the larger ecosystem, and even Anaconda’s own docs say you may need pip when a package or version is not available in conda channels.

    With those understanding, and since we are targeting data science, I think we might need a solution with conda + pip. Note that this is different from letting users to choose alternative, but we offer conda + pip bundle as the only solution.

  5. chenlica commented on Apr 22, 2026

    @chenlica
    Contributor

    @SarahAsad23 Please confirm you are clear about the plan and agree with it.

  6. SarahAsad23 commented on Apr 22, 2026

    @SarahAsad23
    ContributorAuthor

    I agree with this idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions