Publish mssql-python as a conda-forge package
維護者通常 1 天內回覆
@sumitmsft 已經在處理了。
開始於 2026年5月19日。
評估
這個 Issue 還沒有評估資料。
描述
Is your feature request related to a problem? Please describe.
Many data science and machine learning workflows rely on conda as the primary package and environment manager. Currently, mssql-python is only available via PyPI, which creates friction for conda-based projects. When a project's dependency tree is managed through conda (e.g. using conda-forge), mixing pip-installed packages can cause environment inconsistencies, dependency conflicts, and reproducibility issues - particularly in regulated or enterprise environments where environment lockfiles and auditable builds are required.
Describe the solution you'd like
It would be great if mssql-python would be available as a conda package on the conda-forge channel (or an alternative channel). This would allow users to install it via conda install -c conda-forge mssql-python. This involves submitting a feedstock recipe to the conda-forge/staged-recipes repository. The recipe would define the package metadata, source (pointing to the PyPI release or source tarball), build requirements, and runtime dependencies - following the standard conda-forge contribution process. Ideally the conda package would be kept in sync with PyPI releases so that both channels remain up to date.
Describe alternatives you've considered
- Using pip inside a conda environment: this is the current workaround, but it undermines the integrity of conda environment solves and is discouraged in environments where full conda-managed reproducibility is required.
- Self-hosting a conda package: it is possible to build a local conda package from the PyPI source using conda build. However, this places a maintenance burden on end-users and is not a scalable or shareable solution.
Additional context
The conda-forge contribution process is well-documented and community-supported. The grayskull tool can auto-generate an initial feedstock recipe directly from the PyPI package metadata, which significantly reduces the effort required: grayskull pypi mssql-python. Many comparable database drivers (e.g. pyodbc, psycopg2) are already available on conda-forge.
- 主要語言
- Python
- 星號
- 478
- 分支
- 62
- 平均合併
- 3 天 1 小時
- 30 天內合併 PR
- 27
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoft/mssql-python 的其他 Issue
-
area: bulk-copy
難度 2/5 1-3 小時 新手友好度 70/100
microsoft/mssql-python#843 · 1 則留言 ·
維護者通常 1 天內回覆
-
macOS: encrypted connections fail after Homebrew moved the `openssl` alias to `openssl@4`可能已有人在做 @bewithgaurav 於 14 天前認領。 未關閉area: packaging-platform bug triage needed
難度 4/5 3-5 天 新手友好度 55/100
microsoft/mssql-python#826 · 2 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
bulkcopy PyCore login is closed by SQL Server 2019 while ODBC and Go clients succeed (1.14.0)可能重新可做 @bewithgaurav 於 34 天前認領，目前沒有進行中的 PR。 未關閉area: bulk-copy bug triage done
microsoft/mssql-python#750 · 4 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Announcement: mssql-python is coming to Django through mssql-django 2.0可能重新可做 @bewithgaurav 於 41 天前認領，目前沒有進行中的 PR。 未關閉announcement
microsoft/mssql-python#748 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Connection pool can briefly exceed max_size when pooling is disabled under load可能已有人在做 @bewithgaurav 於 23 天前認領。 未關閉area: connectivity-auth bug triage done under development
難度 4/5 3-5 天 新手友好度 62/100
microsoft/mssql-python#746 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 microsoft/mssql-python 的全部 Issue
相似的 Issue
-
Agentic
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
Imbad0202/academic-research-skills#979 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
reflex-dev/reflex#7561 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1-3 小時 新手友好度 62/100
prometheus-community/ansible#906 · 2 則留言 ·