Registry / devops / all-packages

all-packages

JSON →
library1.0.1pypypiunverified

The `all-packages` library is a utility designed to systematically attempt the installation of every package listed on the Python Package Index (PyPI). As of its last major update (v1.0.1 in January 2022), it aimed to install over 349,000 packages. It operates by creating isolated virtual environments for each package, demonstrating the vast scope of the Python ecosystem. Given its specialized and potentially destructive function, it has a very low release cadence.

devops
pip install all-packages
Install & Compatibility
Where this runs
tested against v1.0.1 · 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
musl
py 3.103.920 runs
installs and imports cleanly · install 0.0s · import 0.000s · 17.8MB
glibc
py 3.103.920 runs
installs and imports cleanly · install 1.6s · import 0.000s · 18MB
16MB installed
● package 16MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

all_packages
This library is primarily used as a command-line tool, not typically imported within Python scripts. Its functionality is exposed via the 'all_packages' command.
The library's main purpose is to execute system-level installations rather than provide importable Python objects for application logic.

After installation, run the `all_packages install` command from your terminal. By default, it creates a subdirectory named `all_packages` in your home directory, where it sets up individual virtual environments for each package it attempts to install. It is highly recommended to run this in an isolated environment or a designated test machine due to the potential for significant system impact.

all_packages install # To specify a custom directory for virtual environments: # all_packages install -d ~/my_pypi_collection
Debug
Known issues
breakingAttempting to install 'all-packages' can severely destabilize your Python environment and operating system. Installing hundreds of thousands of packages will almost certainly lead to irreconcilable dependency conflicts, overwrites of critical system libraries, and potentially render your Python installation unusable.
fix
NEVER run 'all_packages install' in your primary Python environment or on a production system. Always use it within a disposable virtual machine or container, and be prepared for potential system reinstallation. The tool itself tries to mitigate this by using virtual environments, but it's not foolproof for all packages.
affects: All versions
gotchaThe process consumes an immense amount of disk space and time. Installing potentially hundreds of thousands of packages requires terabytes of storage and can take many days or weeks to complete, often failing due to various package-specific installation issues or system resource exhaustion.
fix
Ensure you have a machine with abundant free disk space (e.g., several terabytes) and are prepared for a very long-running operation. Monitor disk usage closely.
affects: All versions
gotchaThis library can expose your system to security risks. By design, it installs *every* package from PyPI, including those that might be malicious (e.g., via typosquatting or abandoned packages). While PyPI has security measures, no system is perfectly immune.
fix
Only use `all-packages` in a completely isolated, air-gapped environment or a virtual machine where any compromise would be contained and easily reversible. Do not handle sensitive data on a system where this has been run.
affects: All versions
Upgrade
Version history
1.0.1latest on PyPI
Audit
Dependencies

No dependency data recorded yet.

Agent activity
51 hits · last 30 days
node
15
claudebot
4
ahrefsbot
3
Amazon
2
amazonbot
1
Resources