Azure / Azure/azure-sdk-for-python
Add `azure-mgmt-network` and `azure-communication-email` to conda-forge
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 5.6k
- Forks
- 3.4k
- Ø Merge
- 2 T. 2 Std.
- Gemergte PRs (30 T.)
- 213
Beschreibung
Is your feature request related to a problem? Please describe.
The package azure-mgmt-network has an extremely old version in conda-forge compared to the one in PyPi.
The package azure-communication-email is not available at all in conda-forge. It is available in PyPi.
Describe the solution you'd like
This is very out of the ordinary for azure packages. Normally packages have identical versions in both PyPi and conda-forge.
For example, KeyVault has a modern version in PyPi and conda-forge.
Similarly, Azure Storage Blob has versions in conda-forge and PyPi.
There are many more that are configured correctly, but these two packages are not. I do not know if other packages have a similar issue.
Describe alternatives you've considered
I know that the microsoft anaconda channel has packages labeled by dates (eg the latest is 2025-09-01)
However, these packages just contain multiple real packages inside them. For example here is the one for azure-communication.
The problem with using these is two fold:
- I do not necessarily want to include all of the sub-packages. I may only want
azure-communication-email. Using the date version from themicrosoftchannel does not let me do that - Other packages that use the azure packages rely on the real version numbers (not dates). For example, adlfs requires the
azure-corepackage version >1.35, but the version in themicrosoftchannel has2025.09.01. Conda does not recognize these as the same even though 1.35.0 is inside of 2025.09.01 - Conda gives a
ClobberErrorwhen you install one package standalone and as a sub-package. If you attempt to install most packages, they will automatically installazure-core v1.35.0 as a dependency. But if you installazure-mgmt v2025.09.01, this package no longer containsazure-mgmt-core(not sure why, but it was removed after 2022.12.01). If you then attempt to installazure-mgmt-coremanually it will conflict with the one installed as a dependency. The exact versions technically do not conflict but conda will give aClobberError
Therefore, using the packages from the microsoft channel is not sufficient.
Additionally, using the packages from PyPi is possible but it very problematic because pip does not solve for dependencies, so you are asking for trouble
Additional context
I do not see any reason these packages have not been added to conda-forge, it seems to have been an oversight. hopefully this can be resolved easily because the package is already in PyPi.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, die PyPI- und conda-forge-Einträge für azure-mgmt-network und azure-communication-email zu vergleichen, und lies anschließend das Azure SDK conda-Release-Log unter conda/conda-releaselogs/azure-communication.md. Als erledigt gilt die Aufgabe, wenn beide Pakete mit aktuellen Versionen und Abhängigkeiten, die die beschriebenen Channel-Konflikte vermeiden, über conda-forge verfügbar sind.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, python
- Bereich
- build-system
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 38/100