Install & Compatibility
Where this runs
tested against v3.0.2 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 0.000s · 17.8MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 1.5s · import 0.000s · 18MB
16MB installed
● package 16MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
azure
✓ import azure
✗ from azure_nspkg import ...
`azure-nspkg` does not expose direct symbols; its purpose is to enable the `azure` top-level namespace for other Azure SDKs.
This example shows that after installing `azure-nspkg`, the top-level `azure` namespace becomes available, allowing imports from sub-packages like `azure.storage.blob`. However, for modern Azure SDKs, installing `azure-nspkg` explicitly is almost never required as the individual SDK packages (e.g., `azure-storage-blob`) handle namespace provision themselves.
# This package primarily exists to ensure the 'azure' namespace is available.
# It does not provide direct functionality itself and is generally not needed.
# Modern Azure SDKs (e.g., azure-storage-blob) typically manage their own namespaces.
# To demonstrate its effect (though usually not necessary to install explicitly):
# 1. pip install azure-nspkg
# 2. pip install azure-storage-blob # (or any other azure-* SDK)
try:
import azure
print(f"Successfully imported top-level 'azure' namespace.")
# Note: azure.__version__ might not be available or meaningful for this package.
# You would typically then import from a specific Azure SDK:
# from azure.storage.blob import BlobClient
print("You can now import specific Azure SDK modules (e.g., azure.storage.blob).")
except ImportError:
print("Failed to import 'azure' namespace. This package or other azure-* SDKs might be missing.")
Debug
Known issues
deprecatedThe `azure-nspkg` package is a legacy component and is generally not required for modern Azure SDKs (versions 2.0.0+). Its functionality is superseded by explicit namespace declarations within individual Azure client libraries.fixFor new projects, install specific client libraries (e.g., `pip install azure-storage-blob`, `pip install azure-identity`) directly. These libraries manage their own namespaces and dependencies without needing `azure-nspkg`.
affects: All versions
gotchaInstalling `azure-nspkg` alone does not provide any Azure SDK functionality or client objects. It merely provides the top-level `azure` namespace, which by itself is inert.fixTo use Azure services, you must install the specific client library for that service (e.g., `pip install azure-keyvault-secrets` for Key Vault Secrets, `pip install azure-eventhub` for Event Hubs).
affects: All versions
breakingMixing very old Azure SDKs that implicitly relied on `azure-nspkg` (e.g., `azure-storage` before v0.36) with newer SDKs that use explicit namespace packages (e.g., `azure-storage-blob`) can lead to import conflicts or unexpected behavior due to different ways of managing the `azure` namespace.fixEnsure all Azure SDKs in your project are up-to-date and installed via their individual, modern package names (e.g., `azure-storage-blob` instead of `azure-storage`). Prefer a single, consistent set of modern SDKs to avoid namespace collisions.
affects: < 2.0.0 (old SDKs) when mixed with modern SDKs
Upgrade
Version history
3.0.2latest on PyPI · released Oct 2, 2018
Audit
Dependencies
No dependency data recorded yet.