Componentpedia / Listings / entrypoints

Last update: 15/05/2026

entrypoints

Discover and load entry points from installed packages

Latest version: 0.4 registry icon
Maintenance score
0
Safety score
0
Popularity score
11
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
De-risk your app now
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
0.4 0 0 0 0 0
0.3 0 0 0 0 0
0.2.3 0 0 0 0 0
0.2.2 0 0 0 0 0
0.2.1 0 0 0 0 0
0.2 0 0 0 0 0
0.1 0 0 0 0 0

Stability
Latest release:

0.4 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant

This package is in maintenance-only mode. New code should use the importlib.metadata module <https://docs.python.org/3/library/importlib.metadata.html>_ in the Python standard library to find and load entry points.

Entry points are a way for Python packages to advertise objects with some common interface. The most common examples are console_scripts entry points, which define shell commands by identifying a Python function to run.

Groups of entry points, such as console_scripts, point to objects with similar interfaces. An application might use a group to find its plugins, or multiple groups if it has different kinds of plugins.

The entrypoints module contains functions to find and load entry points. You can install it from PyPI with pip install entrypoints.

To advertise entry points when distributing a package, see entry_points in the Python Packaging User Guide <https://packaging.python.org/guides/distributing-packages-using-setuptools/#entry-points>_.

The pkg_resources module distributed with setuptools provides a way to discover entrypoints as well, but it contains other functionality unrelated to entrypoint discovery, and it does a lot of work at import time. Merely importing pkg_resources causes it to scan the files of all installed packages. Thus, in environments where a large number of packages are installed, importing pkg_resources can be very slow (several seconds).

By contrast, entrypoints is focused solely on entrypoint discovery and it is faster. Importing entrypoints does not scan anything, and getting a given entrypoint group performs a more focused scan.

When there are multiple versions of the same distribution in different directories on sys.path, entrypoints follows the rule that the first one wins. In most cases, this follows the logic of imports. Similarly, Entrypoints relies on pip to ensure that only one .dist-info or .egg-info directory exists for each installed package. There is no reliable way to pick which of several .dist-info folders accurately relates to the importable modules.