͆hbSrSSKJr SSKrSSKrSSKJrJrJrJ r J r J r J r J r \RS:a SSKJrJr OSSKJrJr \(aSSKrSSKJr SSKJrJrJrJrJr \(a$SS KJr SS KJ r SS K!J"r" SS K#J$r$ SS K%J&r& SSK'J(r( \(a SSK)J*r*J+r+ O\ r+\+"S5r,\ "S5r-\R\"S5r/S"Sjr0\ "S\S9r1"SS\ \15r2\3"S\2Rh55r5\5Hr6\7"\2S\6-5 M S#Sjr8"SS\ \,\-45r9"SS\:\ \;\245r<"SS \Rz5r>S$S!jr?g)%z%Implements the plugin API for MkDocs.) annotationsN) TYPE_CHECKINGAnyCallableGenericLiteralMutableMappingTypeVaroverload) ) EntryPoint entry_points)utils)Config ConfigErrorsConfigWarnings LegacyConfigPlainConfigSchema) MkDocsConfig)LiveReloadServer)Files) Navigation)Page)TemplateContext) Concatenate ParamSpecPTmkdocs.pluginsc[SS9n0nUHCnURU;a"URRS5(aM5X!UR'ME U$)z=Return a dict of all installed Plugins as {name: EntryPoint}.r )groupzmkdocs.contrib.)rnamevalue startswith)plugins pluginmapplugins F/opt/services/DDDS/venv/lib/python3.13/site-packages/mkdocs/plugins.py get_pluginsr*(sV!12GI ;;) # (?(?@Q(R(R !'&++   SomeConfig)boundc\rSrSr%Sr\rS\S'SrS\S'0r S\S 'S r S \S 'S%S jr Sr S&S'Sjjr S(SjrS)SjrS*SjrS+SjrS,SjrS-SjrS.SjrS/SjrS,SjrS0SjrS1SjrS2SjrS3SjrS4SjrS5SjrS6S jrS7S!jrS8S"jrS9S#jr S$r!g): BasePlugin:z= Plugin base class. All plugins should subclass this class. ztype[SomeConfig] config_classr config_schemer,configFboolsupports_multiple_instancescbURSURS3n[X 4[US95$)z_Eliminates the need to write `config_class = FooConfig` when subclassing BasePlugin[FooConfig].[])r1)__name__typedict)clsr1r#s r)__class_getitem__BasePlugin.__class_getitem__Hs3,,q!6!6 7q9D&$L"ABBr+c[UR[5(d[SURS35eUR[LaURR Ulgg)Nz config_class z2 must be a subclass of `mkdocs.config.base.Config`) issubclassr1r TypeErrorr_schemar3)r=s r)__init_subclass__BasePlugin.__init_subclass__Ms_#**F33 0 011cd    < / # 0 0 8 8C  0r+NcUR[La[URUS9UlOURUS9UlURR U5 URR 5$)zJLoad config from a dict of options. Returns a tuple of (errors, warnings).)config_file_path)r1rr3r4 load_dictvalidate)selfoptionsrGs r) load_configBasePlugin.load_configUsb    ,&t'9'9L\]DK++=M+NDK g&{{##%%r+cg)aB The `startup` event runs once at the very beginning of an `mkdocs` invocation. New in MkDocs 1.4. The presence of an `on_startup` method (even if empty) migrates the plugin to the new system where the plugin object is kept across builds within one `mkdocs serve`. Note that for initializing variables, the `__init__` method is still preferred. For initializing per-build variables (and whenever in doubt), use the `on_config` event. Args: command: the command that MkDocs was invoked with, e.g. "serve" for `mkdocs serve`. dirty: whether `--dirty` flag was passed. Nr2rJcommanddirtys r) on_startupBasePlugin.on_startupdr+cg)a The `shutdown` event runs once at the very end of an `mkdocs` invocation, before exiting. This event is relevant only for support of `mkdocs serve`, otherwise within a single build it's undistinguishable from `on_post_build`. New in MkDocs 1.4. The presence of an `on_shutdown` method (even if empty) migrates the plugin to the new system where the plugin object is kept across builds within one `mkdocs serve`. Note the `on_post_build` method is still preferred for cleanups, when possible, as it has a much higher chance of actually triggering. `on_shutdown` is "best effort" because it relies on detecting a graceful shutdown of MkDocs. Nr2rJs r) on_shutdownBasePlugin.on_shutdownurTr+cU$)a The `serve` event is only called when the `serve` command is used during development. It runs only once, after the first build finishes. It is passed the `Server` instance which can be modified before it is activated. For example, additional files or directories could be added to the list of "watched" files for auto-reloading. Args: server: `livereload.Server` instance config: global configuration object builder: a callable which gets passed to each call to `server.watch` Returns: `livereload.Server` instance r2rJserverr4builders r)on_serveBasePlugin.on_serves $ r+cU$)a The `config` event is the first event called on build and is run immediately after the user configuration is loaded and validated. Any alterations to the config should be made here. Args: config: global configuration object Returns: global configuration object r2rJr4s r) on_configBasePlugin.on_configs  r+cg)z The `pre_build` event does not alter any variables. Use this event to call pre-build scripts. Args: config: global configuration object Nr2r`s r) on_pre_buildBasePlugin.on_pre_buildrTr+cU$)a The `files` event is called after the files collection is populated from the `docs_dir`. Use this event to add, remove, or alter files in the collection. Note that Page objects have not yet been associated with the file objects in the collection. Use [Page Events](plugins.md#page-events) to manipulate page specific data. Args: files: global files collection config: global configuration object Returns: global files collection r2rJfilesr4s r)on_filesBasePlugin.on_filess  r+cU$)a  The `nav` event is called after the site navigation is created and can be used to alter the site navigation. Args: nav: global navigation object config: global configuration object files: global files collection Returns: global navigation object r2rJnavr4rhs r)on_navBasePlugin.on_navs  r+cU$)a] The `env` event is called after the Jinja template environment is created and can be used to alter the [Jinja environment](https://jinja.palletsprojects.com/en/latest/api/#jinja2.Environment). Args: env: global Jinja environment config: global configuration object files: global files collection Returns: global Jinja Environment r2rJenvr4rhs r)on_envBasePlugin.on_envs  r+cg)z The `post_build` event does not alter any variables. Use this event to call post-build scripts. Args: config: global configuration object Nr2r`s r) on_post_buildBasePlugin.on_post_buildrTr+cg)ar The `build_error` event is called after an exception of any kind is caught by MkDocs during the build process. Use this event to clean things up before MkDocs terminates. Note that any other events which were scheduled to run after the error will have been skipped. See [Handling Errors](plugins.md#handling-errors) for more details. Args: error: exception raised Nr2rJerrors r)on_build_errorBasePlugin.on_build_errorrTr+cU$)a The `pre_template` event is called immediately after the subject template is loaded and can be used to alter the template. Args: template: a Jinja2 [Template](https://jinja.palletsprojects.com/en/latest/api/#jinja2.Template) object template_name: string filename of template config: global configuration object Returns: a Jinja2 [Template](https://jinja.palletsprojects.com/en/latest/api/#jinja2.Template) object r2rJtemplate template_namer4s r)on_pre_templateBasePlugin.on_pre_templates r+cU$)ao The `template_context` event is called immediately after the context is created for the subject template and can be used to alter the context for that specific template only. Args: context: dict of template context variables template_name: string filename of template config: global configuration object Returns: dict of template context variables r2rJcontextrr4s r)on_template_contextBasePlugin.on_template_context r+cU$)a The `post_template` event is called after the template is rendered, but before it is written to disc and can be used to alter the output of the template. If an empty string is returned, the template is skipped and nothing is is written to disc. Args: output_content: output of rendered template as string template_name: string filename of template config: global configuration object Returns: output of rendered template as string r2rJoutput_contentrr4s r)on_post_templateBasePlugin.on_post_template!s "r+cU$)a7 The `pre_page` event is called before any actions are taken on the subject page and can be used to alter the `Page` instance. Args: page: `mkdocs.structure.pages.Page` instance config: global configuration object files: global files collection Returns: `mkdocs.structure.pages.Page` instance r2rJpager4rhs r) on_pre_pageBasePlugin.on_pre_page6s  r+cg)a > DEPRECATED: Instead of this event, prefer one of these alternatives: > > * Since MkDocs 1.6, instead set `content_bytes`/`content_string` of a `File` inside [`on_files`][]. > * Usually (although it's not an exact alternative), `on_page_markdown` can serve the same purpose. The `on_page_read_source` event can replace the default mechanism to read the contents of a page's source from the filesystem. Args: page: `mkdocs.structure.pages.Page` instance config: global configuration object Returns: The raw source for a page as unicode string. If `None` is returned, the default loading from a file will be performed. Nr2rJrr4s r)on_page_read_sourceBasePlugin.on_page_read_sourceEs$r+cU$)a The `page_markdown` event is called after the page's markdown is loaded from file and can be used to alter the Markdown source text. The meta- data has been stripped off and is available as `page.meta` at this point. Args: markdown: Markdown source text of page as string page: `mkdocs.structure.pages.Page` instance config: global configuration object files: global files collection Returns: Markdown source text of page as string r2rJmarkdownrr4rhs r)on_page_markdownBasePlugin.on_page_markdownYs "r+cU$)a The `page_content` event is called after the Markdown text is rendered to HTML (but before being passed to a template) and can be used to alter the HTML body of the page. Args: html: HTML rendered from Markdown source as string page: `mkdocs.structure.pages.Page` instance config: global configuration object files: global files collection Returns: HTML rendered from Markdown source as string r2rJhtmlrr4rhs r)on_page_contentBasePlugin.on_page_contentls " r+cU$)aq The `page_context` event is called after the context for a page is created and can be used to alter the context for that specific page only. Args: context: dict of template context variables page: `mkdocs.structure.pages.Page` instance config: global configuration object nav: global navigation object Returns: dict of template context variables r2rJrrr4rms r)on_page_contextBasePlugin.on_page_contextrr+cU$)a The `post_page` event is called after the template is rendered, but before it is written to disc and can be used to alter the output of the page. If an empty string is returned, the page is skipped and nothing is written to disc. Args: output: output of rendered template as string page: `mkdocs.structure.pages.Page` instance config: global configuration object Returns: output of rendered template as string r2rJoutputrr4s r) on_post_pageBasePlugin.on_post_pages  r+r4)r1z type[Config]N)rKzdict[str, Any]rG str | Nonereturnz#tuple[ConfigErrors, ConfigWarnings]rPz&Literal['build', 'gh-deploy', 'serve']rQr5rNonerr)r[rr4rr\rrzLiveReloadServer | None)r4rrzMkDocsConfig | Noner4rrr)rhrr4rrz Files | None)rmrr4rrhrrzNavigation | None)rrjinja2.Environmentr4rrhrrzjinja2.Environment | Nonerz Exceptionrr)rjinja2.Templaterstrr4rrzjinja2.Template | None)rrrrr4rrTemplateContext | None)rrrrr4rrr)rrr4rrhrrz Page | Nonerrr4rrr) rrrrr4rrhrrr) rrrrr4rrhrrr) rrrrr4rrmrrr)rrrrr4rrr)"r: __module__ __qualname____firstlineno____doc__rr1__annotations__r3r4r6r>rDrLrRrWr]rardrirnrsrvr{rrrrrrrrr__static_attributes__r2r+r)r/r/:s &2L"1')M$)FJ(--aC 9GK &% &9C & , & " "&6BMU ,  "-9BG "%5AJO "$   '>AKW "&=@JV $!8;EQ * ()-7CLQ &%)3?HM &&48BNU_ $r+r/c#Z# UH!oRS5(dMUSSv M# g7f)on_r Nr%).0ks r) rs#I1\\%5Huqu1s+ +rc^U4SjnU$)a A decorator to set an event priority for an event handler method. Recommended priority values: `100` "first", `50` "early", `0` "default", `-50` "late", `-100` "last". As different plugins discover more precise relations to each other, the values should be further tweaked. Usage example: ```python @plugins.event_priority(-100) # Wishing to run this after all other plugins' `on_files` events. def on_files(self, files, config, **kwargs): ... ``` New in MkDocs 1.4. Recommended shim for backwards compatibility: ```python try: from mkdocs.plugins import event_priority except ImportError: event_priority = lambda priority: lambda f: f # No-op fallback ``` c>TUlU$r)mkdocs_priority) event_methodprioritys r) decorator!event_priority..decorators'/ $r+r2)rrs` r)event_priorityrs6 r+c6\rSrSrSrSSjrS SjrS SjrSrg) CombinedEventia( A descriptor that allows defining multiple event handlers and declaring them under one event's name. Usage example: ```python @plugins.event_priority(100) def _on_page_markdown_1(self, markdown: str, **kwargs): ... @plugins.event_priority(-50) def _on_page_markdown_2(self, markdown: str, **kwargs): ... on_page_markdown = plugins.CombinedEvent(_on_page_markdown_1, _on_page_markdown_2) ``` NOTE: The names of the sub-methods **can't** start with `on_`; instead they can start with `_on_` like in the the above example, or anything else. cXlgrmethods)rJrs r)__init__CombinedEvent.__init__s r+cF[[U5R<S35e)Nz object is not callable)rBr;r:)rJinstanceargskwargss r)__call__CombinedEvent.__call__s 4:..11HIJJr+Nc@^^[UU4SjUR56$)Nc3F># UHoRTT5v M g7fr)__get__)rfrowners r)r(CombinedEvent.__get__..sP[TU]"U0UD6 [Vs0sHo3/_M snUl0Ulgs snfr)superrEVENTSevents_event_origins)rJrrr __class__s r)rPluginCollection.__init__s; $)&)AG1HAR%1H 352Is 6c[U[5(a$URHnURXUS9 M g URUnUS:Xad[ U5S:XaUUR R[[U55S5nU=(d Sn[RSUSUS35 [R"XRSS 9 U(aX0R U'g g ![a g f=f) zRegister a method for an event. plugin_namepage_read_source zBMultiple 'on_page_read_source' handlers can't work (both plugins 'z' and 'z' registered one).c[USS5*$)Nrr)getattr)ms r)2PluginCollection._register_event.. sCTVW8X7Xr+)keyN) isinstancerr_register_eventrlenrgetnextiterlogwarningrinsortrB)rJ event_namemethodrsubrplugin1plugin2s r)r PluginCollection._register_events fm , ,~~$$Z+$N&[[,F//CK14D--11$tF|2DkR%4 &&-YggY>PR LL-X Y2=''/!sC!! C.-C.c">[TU]U5$r)r __getitem__)rJrrs r)rPluginCollection.__getitem__sw"3''r+c>[TU]X5 S[U55H4n[X#S5n[ U5(dM!UR USSXAS9 M6 g)Nc3T# UHoRS5(dMUv M g7f)rNr)rxs r)r/PluginCollection.__setitem__..sHjLL4G11js( (r r)r __setitem__dirrcallabler)rJrr$rrrs r)r PluginCollection.__setitem__sT C'Hc%jHJU5F$$Z^V$MIr+c grr2)rJr#rs r) run_eventPluginCollection.run_event r+c grr2)rJr#itemrs r)rr#rr+c bUSLnURUHnURRUS5Ul[R 5[ R::a&[RSUSURS35 U(a U"U40UD6nOU"S0UD6nUcMUnM SUlU$)a+ Run all registered methods of an event. `item` is the object to be modified or replaced and returned by the event method. If it isn't given the event method creates a new object to be returned. All other keywords are variables for context, but would not generally be modified by the event method. Nrz Running `z` event from plugin ''r2) rrrrrgetEffectiveLevelloggingDEBUGdebug)rJr#rr pass_itemrresults r)rr's$ kk$'F#'#6#6#:#:6;#OD $$&'--7 IdV+@AUAU@VVWXY//)&)!( $ r+c"URSXS9$)Nstartup)rPrQrrOs r)rRPluginCollection.on_startup?s~~i~FFr+c$URS5$)Nshutdownr!rVs r)rWPluginCollection.on_shutdownBs~~j))r+c$URSXUS9$)Nserve)r4r\r!rZs r)r]PluginCollection.on_serveEs~~gvg~NNr+c&URSU5$)Nr4r!r`s r)raPluginCollection.on_configJs~~h//r+c"URSUS9$)N pre_buildrr!r`s r)rdPluginCollection.on_pre_buildMs~~k&~99r+c"URSXS9$)Nrhrr!rgs r)riPluginCollection.on_filesPs~~gu~<r!rs r)r$PluginCollection.on_template_contextds!~~ V  r+c$URSXUS9$)N post_templater>r!rs r)r!PluginCollection.on_post_templateks"~~ ^QW  r+c$URSXUS9$)Npre_pager1r!rs r)rPluginCollection.on_pre_pagers~~j$U~KKr+c"URSXS9$)Nrrr4r!rs r)r$PluginCollection.on_page_read_sourceus~~0t~KKr+c$URSXX4S9$)N page_markdownrr4rhr!rs r)r!PluginCollection.on_page_markdownxs~~ox6~__r+c$URSXX4S9$)N page_contentrNr!rs r)r PluginCollection.on_page_content}s~~ndf~ZZr+c$URSXX4S9$)N page_context)rr4rmr!rs r)r PluginCollection.on_page_contexts~~ng~YYr+c$URSXUS9$)N post_pagerJr!rs r)rPluginCollection.on_post_pages~~k6V~LLr+)rrrrr)rrrzCombinedEvent | Callablerrrr)rrrr/)rrr$r/rr)r#rrr)r#rrrrr)r#rr)r[rr4rr\rrr)r4rrrr)rhrr4rrr)rmrr4rrhrrr)rrrr4rrhrr)rrrrr4rrr)rrrrr4rrr)rrrrr4rrr)rrr4rrhrrrr) rrrrr4rrhrrr) rrrrr4rrhrrr) rrrrr4rrmrrr)rrrrr4rrr)!r:rrrrrrrrr r rrRrWr]rardrirnrsrvr{rrrrrrrrrr __classcell__rs@r)rrs 6 \`'?NX .(N    0G*O&O3?OJRO O 0:=FF;:d'd;>dHTd d  & := GS   ! 58 BN  LL``&*`4@`IN` ` [Z&Z15Z?KZR\Z Z MMr+rc:^\rSrSrSrSU4SjjrSSjrSrU=r$)PrefixedLoggeriz(A logger adapter to prefix log messages.c2>[TU]U05 Xlg)z Initialize the logger adapter. Arguments: prefix: The string to insert in front of every message. logger: The logger instance. N)rrprefix)rJr^loggerrs r)rPrefixedLogger.__init__s $ r+c(URSU3U4$)z~ Process the message. Arguments: msg: The message: kwargs: Remaining arguments. Returns: The processed message. z: r^)rJmsgrs r)processPrefixedLogger.processs++b&..r+rb)r^rr_zlogging.Loggerrr)rcrrzMutableMapping[str, Any]rztuple[str, Any]) r:rrrrrrdrrYrZs@r)r\r\s2  / /r+r\cr[R"SU35n[URSS5SU5$)ao Return a logger for plugins. Arguments: name: The name to use with `logging.getLogger`. Returns: A logger configured to work well in MkDocs, prefixing each message with the plugin package name. Example: ```python from mkdocs.plugins import get_plugin_logger log = get_plugin_logger(__name__) log.info("My plugin message") ``` zmkdocs.plugins..rr)r getLoggerr\split)r#r_s r)get_plugin_loggerrjs8&  7 8F $**S!,Q/ 88r+)rzdict[str, EntryPoint])rfloatrzCallable[[T], T])r#rrr\)@r __future__rrsystypingrrrrrr r r version_infoimportlib.metadatarrimportlib_metadatajinja2.environmentjinja2mkdocsrmkdocs.config.baserrrrrmkdocs.config.defaultsrmkdocs.livereloadrmkdocs.structure.filesrmkdocs.structure.navrmkdocs.structure.pagesrmkdocs.utils.templatesrtyping_extensionsrrrrrhrr*r,r/tuple__dict__rrdelattrrrr<rr LoggerAdapterr\rjr2r+r)rs1+" dddw;;;dd32,/+688I cN CL() \ 0 f$fR Ij11I I A J " DRGAqDMRBYMt^CO<YMx/W**/89r+