From ba7f63ac8172e97d04d2ea2ed30b793e9ec9f98f Mon Sep 17 00:00:00 2001 From: Ultrabug Date: Wed, 8 Sep 2021 08:48:47 +0200 Subject: [PATCH] dev guide: remove misleading usage of 'entry_point' wording (#2563) closes mkdocs/mkdocs#2558 thx to @hwittenborn --- docs/dev-guide/plugins.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/dev-guide/plugins.md b/docs/dev-guide/plugins.md index de5437a4..79ed2979 100644 --- a/docs/dev-guide/plugins.md +++ b/docs/dev-guide/plugins.md @@ -441,7 +441,7 @@ class MyPlugin(BasePlugin): ### Entry Point Plugins need to be packaged as Python libraries (distributed on PyPI separate -from MkDocs) and each must register as a Plugin via a setuptools entry_point. +from MkDocs) and each must register as a Plugin via a setuptools `entry_points`. Add the following to your `setup.py` script: ```python @@ -457,7 +457,7 @@ The `pluginname` would be the name used by users (in the config file) and (`from path.to.some_plugin import SomePluginClass`) where `SomePluginClass` is a subclass of [BasePlugin] which defines the plugin behavior. Naturally, multiple Plugin classes could exist in the same module. Simply define each as a separate -entry_point. +entry point. ```python entry_points={