centersl/mkdocs
1
0
Fork 0
mirror of https://github.com/mkdocs/mkdocs.git synced 2026-03-27 09:58:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

dev guide: remove misleading usage of 'entry_point' wording (#2563)

Browse Source 
closes mkdocs/mkdocs#2558 thx to @hwittenborn
This commit is contained in:
Ultrabug
2021-09-08 08:48:47 +02:00
committed by GitHub
parent 519d2d32c3
commit ba7f63ac81
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/dev-guide/plugins.md
View File

@@ -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={