L18n is used in Python projects. Internationalization for pytz timezones and territories It has 2 direct runtime dependencies. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Internationalization for pytz timezones and territories
l18n declares 2 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, l18n can pull in further packages through its dependency tree. PyDeps resolves the entire chain from PyPI and deps.dev so you can see every transitive (nested) dependency of l18n, expand any node on demand, and understand the full set of code that ships when you run pip install l18n.
PyDeps checks l18n and every package in its dependency tree against the OSV vulnerability database in real time. For each CVE you can see the severity, the affected version ranges, and the first fixed version, so you know exactly which l18n version is safe to install before you ship.
l18n is distributed under the MIT License. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole l18n install, not just the top-level package.
Install from PyPI with pip install l18n. For offline or air-gapped environments, PyDeps can download l18n together with every resolved dependency as wheel files in a single bundle, matched to your target Python version and operating system.
Switch to the dependents view to see the reverse dependencies of l18n — the PyPI packages that list l18n as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.