intellecton/venv/lib/python3.12/site-packages/properdocs/__pycache__/plugins.cpython-312.pyc

Ë
MÀjídã
ó~—dZd
dl
mZ
d
dlZd
dlZd
dlmZ
d
dlmZm	Z	m
Z
mZmZm
Z
mZ
ejdk\r	d
dlmZmZ
nd
dlmZmZ
erd
dlZd
dlmZ
d
d	lmZmZmZmZmZ
er$d
d
lmZ
d
dl m!Z!
d
dl"m#Z#
d
d
l$m%Z%
d
dl&m'Z'
d
dl(m)Z)
er	d
dl*m+Z+m,Z,
ne
Z,e,d«
Z-e
d«
Z.ej^d«
Z0d#d„Z1e
de¬«Z2Gd„dee2«Z3e4d„e3jjD««
Z6e6D]Z7e8e3de7z«
Œd$d„Z9Gd„dee-e.f«Z:Gd„de;ee<e3f«Z=Gd „d!ej|«Z?d%d"„Z@y)&z)Implements the plugin API for ProperDocs.é)
ÚannotationsN)
ÚMutableMapping)Ú
TYPE_CHECKINGÚAnyÚCallableÚGenericÚLiteralÚTypeVarÚoverload)éé
)Ú
EntryPointÚentry_points)
Úutils)ÚConfigÚConfigErrorsÚConfigWarningsÚLegacyConfigÚPlainConfigSchema)
ÚProperDocsConfig)
ÚLiveReloadServer)
ÚFiles)
Ú
Navigation)
ÚPage)
ÚTemplateContext)ÚConcatenateÚ	ParamSpecÚ
PÚ
Tzproperdocs.pluginsc
ó
—iid
œ}|D]u}
t
|
›d�¬«
D]a}t|dd«jd«
r
Π|j||
vr|jj|
›d�«
r
ŒP|||
|j<ŒcŒw|d|d	zS)
z=Return a dict of all installed Plugins as {name: EntryPoint}.)Ú
properdocsÚmkdocsz.plugins)
ÚgroupÚvalueÚzmkdocs.z	.contrib.r"r!)rÚgetattrÚ
startswithÚnamer$)Ú
pluginmapsÚprefixÚplugins   úU/home/antigravity/intellecton/venv/lib/python3.12/site-packages/properdocs/plugins.pyÚget_pluginsr-/s©€àBDÐPRÑ3S€Jàò5ˆÜ"¨F¨8°8Ð)<Ô=ò	5ˆFÜ�v˜w¨Ó+×6Ñ6°yÔAØà�{‰{˜j¨Ñ0Ñ0°V·\±\×5LÑ5LÐPVÈxÐW`ÐMaÔ5bØØ.4ˆJ�vÑ˜vŸ{™{Ò+ñ
	5ð5ð�hÑ *¨\Ñ":Ñ:Ð:óÚ
SomeConfig)
Úboundc
ó¤
—eZ
dZUd
ZeZded<dZded<iZded<d	Z	d
ed<	d#d„Z
d
„Z	d$					d%d„Zd&d„Z
d'd„Z								d(d„Zd)d„Zd*d„Zd+d„Z								d,d„Z								d-d„Zd*d„Zd.d„Z								d/d„Z								d0d„Z								d1d„Zd2d„Zd3d„Z										d4d„Z										d5d „Z										d6d!„Zd7d"„Zy)8Ú
BasePluginzI
    Plugin base class.

    All plugins should subclass this class.
    ztype[SomeConfig]Úconfig_class©rÚ
config_schemer/ÚconfigFÚboolÚsupports_multiple_instancesc
ój—|j›d
|
j›d�}t||f
t|
¬«
«S)z_Eliminates the need to write `config_class = FooConfig` when subclassing BasePlugin[FooConfig].ú
[ú
])
r3)Ú__name__ÚtypeÚdict)Úclsr3r(s   r,Ú__class_getitem__zBasePlugin.__class_getitem__Ps5€à—,‘,�˜q ×!6Ñ!6Ð 7°qÐ9ˆÜ�D˜3˜&¤$°LÔ"AÓBÐBr.c

óÆ—t
|jt«std
|j›d�«
‚
|jtu
r|jj
|_yy)Nz
config_class z6 must be a subclass of `properdocs.config.base.Config`)Ú
issubclassr3rÚ	TypeErrorrÚ_schemar5)
r?s
 r,Ú__init_subclass__zBasePlugin.__init_subclass__Us\€Ü˜#×*Ñ*¬FÔ3ÜØ × 0Ñ 0Ð1Ð1gÐhóð
ð×Ѥ<Ñ/Ø #× 0Ñ 0× 8Ñ 8ˆCÕð0r.Nc
óø—|jturt|j|¬
«|_n|j
|¬
«
|_|jj	|
«

|jj«S)zJLoad config from a dict of options. Returns a tuple of (errors, warnings).)
Úconfig_file_path)r3rr5r6Ú	load_dictÚvalidate)ÚselfÚoptionsrGs   r,Úload_configzBasePlugin.load_config]sb€ð×ѤÑ,Ü& t×'9Ñ'9ÐL\Ô]ˆD�Kà×+Ñ+Ð=MÐ+ÓNˆDŒKà�‰×јgÔ&à�{‰{×#Ñ#Ó%Ð%r.c

ó—y
)a¢
        The `startup` event runs once at the very beginning of an `properdocs` 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 `properdocs 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 ProperDocs was invoked with, e.g. "serve" for `properdocs serve`.
            dirty: whether `--dirty` flag was passed.
        Nr4©rJÚcommandÚdirtys   r,Ú
on_startupzBasePlugin.on_startupló�r.c

ó—y
)aå
        The `shutdown` event runs once at the very end of an `properdocs` invocation, before exiting.

        This event is relevant only for support of `properdocs 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 `properdocs 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 ProperDocs.
        Nr4©
rJs
 r,Úon_shutdownzBasePlugin.on_shutdown}rRr.c

ó—|
S)
av
        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
        r4©rJÚserverr6Úbuilders    r,Úon_servezBasePlugin.on_serveŽs	€ð$ˆ
r.c

ó—|
S)
aP

        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
        r4©rJr6s  r,Ú	on_configzBasePlugin.on_config¤s	€ðˆ
r.c


ó—y
)z¶
        The `pre_build` event does not alter any variables. Use this event to call
        pre-build scripts.

        Args:
            config: global configuration object
        Nr4r\s  r,Úon_pre_buildzBasePlugin.on_pre_build²rRr.c


ó—|
S)
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
        r4©rJÚfilesr6s   r,Úon_fileszBasePlugin.on_files»s	€ðˆr.c

ó—|
S)
aQ

        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
        r4©rJÚnavr6rbs    r,Úon_navzBasePlugin.on_navÌs	€ðˆ
r.c

ó—|
S)
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
        r4©rJÚenvr6rbs    r,Úon_envzBasePlugin.on_envÝs	€ð ˆ
r.c


ó—y
)z¸
        The `post_build` event does not alter any variables. Use this event to call
        post-build scripts.

        Args:
            config: global configuration object
        Nr4r\s  r,Ú
on_post_buildzBasePlugin.on_post_buildïrRr.c


ó—y
)aº

        The `build_error` event is called after an exception of any kind
        is caught by ProperDocs during the build process.
        Use this event to clean things up before ProperDocs 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
        Nr4©rJÚerrors  r,Úon_build_errorzBasePlugin.on_build_errorørRr.c

ó—|
S)
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
        r4©rJÚtemplateÚ
template_namer6s    r,Úon_pre_templatezBasePlugin.on_pre_template
s	€ðˆr.c

ó—|
S)
a¿

        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
        r4©rJÚcontextrur6s    r,Úon_template_contextzBasePlugin.on_template_context
ó	€ð ˆr.c

ó—|
S)
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
        r4©rJÚoutput_contentrur6s    r,Úon_post_templatezBasePlugin.on_post_template)
s
€ð"Ðr.c

ó—|
S)
a‡

        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: `properdocs.structure.pages.Page` instance
            config: global configuration object
            files: global files collection

        Returns:
            `properdocs.structure.pages.Page` instance
        r4©rJÚpager6rbs    r,Úon_pre_pagezBasePlugin.on_pre_page>
s	€ðˆr.c


ó—y
)aò
        > DEPRECATED: Instead of this event, prefer one of these alternatives:
        >
        > * Since ProperDocs 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: `properdocs.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.
        Nr4©rJr‚r6s   r,Úon_page_read_sourcezBasePlugin.on_page_read_sourceM
s€ð$r.c

ó—|
S)
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: `properdocs.structure.pages.Page` instance
            config: global configuration object
            files: global files collection

        Returns:
            Markdown source text of page as string
        r4©rJÚmarkdownr‚r6rbs     r,Úon_page_markdownzBasePlugin.on_page_markdowna
s	€ð"ˆr.c

ó—|
S)
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: `properdocs.structure.pages.Page` instance
            config: global configuration object
            files: global files collection

        Returns:
            HTML rendered from Markdown source as string
        r4©rJÚhtmlr‚r6rbs     r,Úon_page_contentzBasePlugin.on_page_contentt
s	€ð"ˆr.c

ó—|
S)
aÅ

        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: `properdocs.structure.pages.Page` instance
            config: global configuration object
            nav: global navigation object

        Returns:
            dict of template context variables
        r4©rJryr‚r6rfs     r,Úon_page_contextzBasePlugin.on_page_context‡
r{r.c

ó—|
S)
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: `properdocs.structure.pages.Page` instance
            config: global configuration object

        Returns:
            output of rendered template as string
        r4©rJÚoutputr‚r6s    r,Úon_post_pagezBasePlugin.on_post_page™
s	€ðˆ
r.)r3ztype[Config]©
N)rKzdict[str, Any]rGú
str | NoneÚreturnz#tuple[ConfigErrors, ConfigWarnings]©rOz&Literal['build', 'gh-deploy', 'serve']rPr7r˜ÚNone©r˜rš)rXrr6rrYrr˜zLiveReloadServer | None)r6rr˜zProperDocsConfig | None©r6rr˜rš)rbrr6rr˜zFiles | None)rfrr6rrbrr˜zNavigation | None)rjújinja2.Environmentr6rrbrr˜zjinja2.Environment | None©rpÚ	Exceptionr˜rš)rtújinja2.TemplateruÚstrr6rr˜zjinja2.Template | None)ryrrur¡r6rr˜úTemplateContext | None)r~r¡rur¡r6rr˜r—)r‚rr6rrbrr˜zPage | None©r‚rr6rr˜r—)
r‰r¡r‚rr6rrbrr˜r—)
r�r¡r‚rr6rrbrr˜r—)
ryrr‚rr6rrfrr˜r¢)r”r¡r‚rr6rr˜r—) r<Ú
__module__Ú__qualname__Ú__doc__rr3Ú__annotations__r5r6r8r@rErLrQrUrZr]r_rcrgrkrmrqrvrzrrƒr†rŠrŽr‘r•r4r.r,r2r2Bsý
…ñð&2€LÐ"Ó1Ø')€MÐ$Ó)Ø€FˆJÓà(-РÓ-ØaóC
ò
9ðG
K
ð&Ø%ð&Ø9Cð&à	,ó&óó"ð"Ø&ðØ6FðØQYðà	 óó,óóð"ØðØ-=ðØFKðà	óð"Ø%ðØ5EðØNSðà	"óó$ó
ðØ'ðØ>AðØK[ðà	óð"Ø&ðØ=@ðØJZðà	óð$Ø!ðØ8;ðØEUðà	óó*
óð(ØðØ)-ðØ7GðØPUðà	óð&ØðØ%)ðØ3CðØLQðà	óð&Ø&ðØ48ðØBRðØYcðà	óô$r.r2c
#
óJK
—|]}
|
j
d«
s
Œ|
d
d–
—

Œy­w
)Úon_rN©
r')Ú.0Ú
ks  r,ú	<genexpr>r­«
s!èø€ÒI˜°Q·\±\À%Õ5Hˆq��ŒuÑIùs‚#
™
#
r©c

ó‡—ˆf
d
„}
|
S)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 properdocs.plugins import event_priority
    except ImportError:
        event_priority = lambda priority: lambda f: f  # No-op fallback
    ```
    c

ó•
—‰
|_|Sr–)
Úmkdocs_priority)Úevent_methodÚprioritys €r,Ú	decoratorz!event_priority.<locals>.decoratorÍ
sø€Ø'/ˆÔ$ØÐr.r4)r²r³s` r,Úevent_priorityr´²
sø€ô6ðÐr.c
ó(—eZ
dZd
Zdd„Zdd„Zdd„
Zy)	Ú
CombinedEventa`
    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.
    c

ó—|
|_yr–)
Úmethods)rJr¸s  r,Ú__init__zCombinedEvent.__init__ê
s	€Øˆ�r.c
óD—t
t|«
j›d
�«
‚
)Nz object is not callable)rCr=r<)rJÚinstanceÚargsÚkwargss    r,Ú__call__zCombinedEvent.__call__î
s €Üœ4 ›:×.Ñ.Ð1Ð1HÐIÓJÐJr.Nc
ó>‡
‡—t
ˆ
ˆfd
„|jD«ŽS)Nc
3
óB•K
—|]}
|
j
‰‰«–
—

Œy­w
r–)
Ú__get__)r«Ú
fr»Úowners  €€r,r­z(CombinedEvent.__get__.<locals>.<genexpr>ò
søèø€ÒP¸a˜qŸy™y¨°5×9ÑPùsƒ
)r¶r¸)rJr»rÃs ``r,rÁzCombinedEvent.__get__ñ
sù€ÜÔPÀ4Ç<Á<ÔPÐQÐQr.)r¸z Callable[Concatenate[Any, P], T])r»r2r¼zP.argsr½zP.kwargsr˜rr–)r<r¤r¥r¦r¹r¾rÁr4r.r,r¶r¶Ô
s„ñó*
ó
K
ô
R
r.r¶c
ó¤
‡—eZ
dZUd
Zded<dˆf
d„Z	d							d d„Zd!ˆf
d„Zd"ˆf
d„Ze	d#d„«Z
e	d$d	„«Z
dd%d
„Z
d&d„Zdd„Z								d'd
„Z
d(d„Zd)d„Zd*d„Zd+d„Zd,d„Zd)d„Zd-d„Z								d.d„Z								d/d„Z								d0d„Zd1d„Zd2d„Z										d3d„Z										d4d„Z										d5d„Zd6d„Zˆx
ZS)7ÚPluginCollectionzì
    A collection of plugins.

    In addition to being a dict of Plugin instances, each event method is registered
    upon being added. All registered methods for a given event can then be run in order
    by calling `run_event`.
    r—Ú_current_pluginc

óp•
—t
‰|�|
i|¤
Ž

tD�cic]}|g“Œc}|_i|_yc
c}wr–)Úsuperr¹ÚEVENTSÚeventsÚ_event_origins)rJr¼r½r¬Ú	__class__s    €r,r¹zPluginCollection.__init__s9ø€Ü
‰Ñ˜$Ð) &Ò)ÜAGÖ1H¸A°!°R±%Ò1HˆŒØ35ˆÕùò2I
s™
3c
óÊ
—t
|t«r&|jD]}|j|
||¬
«
Œy
|j|
}|
dk(r^t|«
dk(rP|jjtt|«
«
d«}|x
s
d}tjd|›d|›d�«

tj||d„¬	«
|r	||j|<y
y
#t$r
Yy
wxYw
)zRegister a method for an event.©
Úplugin_nameÚpage_read_sourceé
ú	<unknown>zBMultiple 'on_page_read_source' handlers can't work (both plugins 'z' and 'z' registered one).c

ó—t
|d
d«S)Nr°r)
r&)
Ú
ms
 r,ú<lambda>z2PluginCollection._register_event.<locals>.<lambda>s€¼À
ÐCTÐVWÓ8XÐ7X€r.)
ÚkeyN)Ú
isinstancer¶r¸Ú_register_eventrÊÚlenrËÚgetÚnextÚiterÚlogÚwarningrÚinsortrC)rJÚ
event_nameÚmethodrÏÚsubrÊÚplugin1Úplugin2s        r,rØz PluginCollection._register_eventsð€ô�fœmÔ,Ø—~‘~ò

O
�Ø×$Ñ$ Z°À+Ð$ÕNñ

O
ð—[‘[ Ñ,ˆFØÐ/Ò/´C¸³KÀ1Ò4DØ×-Ñ-×1Ñ1´$´t¸F³|Ó2DÀkÓR�Ø%Ò4¨�Ü—‘ð
&Ø&- Y¨g°g°YÐ>Pð
R
ôô
�L‰L˜ Ñ-XÕYÙðØ2=�D×'Ñ'¨Ò/ðøô!ò
Ùð
úsÃCÃ	C"Ã!
C"c
ó"•
—t‰|�|
«
Sr–)rÈÚ__getitem__)rJrÖrÌs  €r,ræzPluginCollection.__getitem__sø€Ü‰wÑ" 3Ó'Ð'r.c
ó´•
—t‰|�|
|«
d
„t|«
D«D]2}t||d«}t	|«
s
Œ|j|dd||
¬«
Œ4y)Nc
3
óDK
—|]}
|
j
d«
s
Œ|
–
—

Œy
­w
)r©Nrª)r«Ú
xs  r,r­z/PluginCollection.__setitem__.<locals>.<genexpr>"sèø€ÒH °A·L±LÀÕ4Gœ1ÑHùs‚ 
™ 
rrÎ)rÈÚ__setitem__Údirr&ÚcallablerØ)rJrÖr$ràrárÌs     €r,rêzPluginCollection.__setitem__s]ø€Ü
‰Ñ˜C Ô'áH¤c¨%£jÔHò	N
ˆJܘU J°Ó5ˆFܘÕØ×$Ñ$ Z°
° ^°VÈÐ$ÕMñ	N
r.c
ó—yr–r4)rJr(r½s   r,Ú	run_eventzPluginCollection.run_event's€Ø58r.c
ó—yr–r4)rJr(Úitemr½s    r,rîzPluginCollection.run_event*s€Ø<?r.c
óN
—|d
u
}|j|
D]‡}|jj|d«|_tj«tjkr&tjd|
›d|j›d�«

|r
||f
i|¤
Ž
}n|di|¤
Ž
}|€
Œ†|}Œ‰d
|_|S)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.
        NrÒz	Running `z` event from plugin 'ú
'r4)	rÊrËrÚrÆrÝÚgetEffectiveLevelÚloggingÚDEBUGÚdebug)rJr(rðr½Ú	pass_itemráÚresults       r,rîzPluginCollection.run_event-s³€ð Ð$ˆ	Ø—k‘k $Ñ'ò
	ˆFØ#'×#6Ñ#6×#:Ñ#:¸6À;Ó#OˆDÔ Ü×$Ñ$Ó&¬'¯-©-Ò7Ü—	‘	˜I d VÐ+@À×AUÑAUÐ@VÐVWÐXÔYÙÙ Ñ/¨Ñ/‘áÑ) &Ñ)�àÑ!Ø‘ð
	ð $ˆÔ؈r.c

ó*—|j
d
|
|¬«S)NÚstartup)rOrP©
rîrNs   r,rQzPluginCollection.on_startupEs€Ø�~‰~˜i°Àˆ~ÓFÐFr.c

ó$—|j
d
«
S)NÚshutdownrûrTs
 r,rUzPluginCollection.on_shutdownHs€Ø�~‰~˜jÓ)Ð)r.c
ó,—|j
d
|
||¬«S)NÚserve)r6rYrûrWs    r,rZzPluginCollection.on_serveKs€ð�~‰~˜g v°fÀgˆ~ÓNÐNr.c
ó&—|j
d
|
«S)Nr6rûr\s  r,r]zPluginCollection.on_configPs€Ø�~‰~˜h¨Ó/Ð/r.c


ó(—|j
d
|
¬«S)NÚ	pre_build©
r6rûr\s  r,r_zPluginCollection.on_pre_buildSs€Ø�~‰~˜k°&ˆ~Ó9Ð9r.c

ó*—|j
d
|
|¬«S)Nrbr
rûras   r,rczPluginCollection.on_filesVs€Ø�~‰~˜g u°Vˆ~Ó<Ð<r.c
ó,—|j
d
|
||¬«S)Nrf©r6rbrûres    r,rgzPluginCollection.on_navYó€Ø�~‰~˜e S°¸uˆ~ÓEÐEr.c
ó,—|j
d
|
||¬«S)Nrjr
rûris    r,rkzPluginCollection.on_env\r
r.c


ó(—|j
d
|
¬«S)NÚ
post_buildr
rûr\s  r,rmzPluginCollection.on_post_build_s€Ø�~‰~˜l°6ˆ~Ó:Ð:r.c


ó(—|j
d
|
¬«S)NÚbuild_error)
rprûros  r,rqzPluginCollection.on_build_errorbs€Ø�~‰~˜m°5ˆ~Ó9Ð9r.c
ó,—|j
d
|
||¬«S)NÚpre_template©rur6rûrss    r,rvz PluginCollection.on_pre_templatees€ð�~‰~˜n¨hÀmÐ\bˆ~ÓcÐcr.c
ó,—|j
d
|
||¬«S)NÚtemplate_contextr
rûrxs    r,rzz$PluginCollection.on_template_contextjs#€ð�~‰~Ø °}ÈVðó
ð	
r.c
ó,—|j
d
|
||¬«S)NÚ
post_templater
rûr}s    r,rz!PluginCollection.on_post_templateqs$€ð�~‰~Ø˜^¸=ÐQWðó
ð	
r.c
ó,—|j
d
|
||¬«S)NÚpre_pager
rûr�s    r,rƒzPluginCollection.on_pre_pagexs€Ø�~‰~˜j¨$°vÀUˆ~ÓKÐKr.c

ó*—|j
d
|
|¬«S)NrЩr‚r6rûr…s   r,r†z$PluginCollection.on_page_read_source{s€Ø�~‰~Ð0°tÀFˆ~ÓKÐKr.c
ó.—|j
d
|
|||¬«S)NÚ
page_markdown©r‚r6rbrûrˆs     r,rŠz!PluginCollection.on_page_markdown~s€ð�~‰~˜o¨x¸dÈ6ÐY^ˆ~Ó_Ð_r.c
ó.—|j
d
|
|||¬«S)NÚpage_contentr
rûrŒs     r,rŽz PluginCollection.on_page_contentƒs€ð�~‰~˜n¨d¸ÀfÐTYˆ~ÓZÐZr.c
ó.—|j
d
|
|||¬«S)NÚpage_context)r‚r6rfrûr�s     r,r‘z PluginCollection.on_page_contextˆs€ð�~‰~˜n¨g¸DÈÐUXˆ~ÓYÐYr.c
ó,—|j
d
|
||¬«S)NÚ	post_pager
rûr“s    r,r•zPluginCollection.on_post_page�s€Ø�~‰~˜k¨6¸ÀVˆ~ÓLÐLr.r›r–)ràr¡rázCombinedEvent | CallablerÏr—r˜rš)rÖr¡r˜r2)rÖr¡r$r2r˜rš)r(r¡r˜r)r(r¡rðrr˜r)r(r¡r™)rXrr6rrYrr˜r)r6rr˜rrœ)rbrr6rr˜r)rfrr6rrbrr˜r)rjr�r6rrbrrž)rtr rur¡r6rr˜r )ryrrur¡r6rr˜r)r~r¡rur¡r6rr˜r¡)r‚rr6rrbrr˜rr£)
r‰r¡r‚rr6rrbrr˜r¡)
r�r¡r‚rr6rrbrr˜r¡)
ryrr‚rr6rrfrr˜r)r”r¡r‚rr6rr˜r¡)r<r¤r¥r¦r§r¹rØrærêrrîrQrUrZr]r_rcrgrkrmrqrvrzrrƒr†rŠrŽr‘r•Ú
__classcell__©
rÌs
@r,rÅrÅõ
sè
ø…ñð Óõ6ð\
`
ðØðØ'?ðØNXðà	
óõ.
(õN
ðÚ8óØ8à
Ú?óØ?ôó0
G
ó
*ðO
Ø&ðO
Ø3CðO
ØNVðO
à	óO
ó

0ó
:ó
=ó
F
ó
F
ó
;ó
:ðd
Ø'ðd
Ø;>ðd
ØHXðd
à	ód
ð

Ø&ð
Ø:=ð
ØGWð
à	ó
ð
Ø!ð
Ø58ð
ØBRð
à	ó
ó
L
ó
L
ð`
Øð`
Ø&*ð`
Ø4Dð`
ØMRð`
à	ó`
ð
[
Øð[
Ø"&ð[
Ø0@ð[
ØINð[
à	ó[
ð
Z
Ø&ðZ
Ø15ðZ
Ø?OðZ
ØV`ðZ
à	óZ
÷

M
r.rÅc
ó,‡—eZ
dZd
Zdˆf
d„Zdd„Zˆx
ZS)ÚPrefixedLoggerz(A logger adapter to prefix log messages.c
ó4•
—t‰|�|i«
|
|_y
)z±
        Initialize the logger adapter.

        Arguments:
            prefix: The string to insert in front of every message.
            logger: The logger instance.
        N)rÈr¹r*)rJr*ÚloggerrÌs   €r,r¹zPrefixedLogger.__init__”sø€ô	‰Ñ˜ Ô$؈�r.c
ó(—|j›d
|
›�|fS)z¶