Files
intellecton/venv/lib/python3.12/site-packages/mkdocs/__pycache__/plugins.cpython-312.pyc
T

384 lines
32 KiB
Plaintext
Raw Normal View History

Ë
j±bãóvdZddlmZddlZddlZddlmZmZmZm Z m
Z
m Z m Z m
Z
ejdk\r ddlmZmZnddlmZmZerddlZddlmZddlmZmZmZmZmZer$dd lmZdd
lm Z dd l!m"Z"dd l#m$Z$dd
l%m&Z&ddl'm(Z(er ddl)m*Z*m+Z+ne Z+e+d«Z,e d«Z-ej\d«Z/d"dZ0e de¬«Z1Gdde e1«Z2e3de2jhD««Z5e5D]Z6e7e2de6z«Œd#dZ8Gdde e,e-f«Z9Gdde:e e;e2f«Z<Gdd ejz«Z>d$d!„Z?y)%z%Implements the plugin API for MkDocs.é)Ú annotationsN)Ú
TYPE_CHECKINGÚAnyÚCallableÚGenericÚLiteralÚMutableMappingÚTypeVarÚoverload)éé
)Ú
EntryPointÚ entry_points)Úutils)ÚConfigÚ ConfigErrorsÚConfigWarningsÚ LegacyConfigÚPlainConfigSchema)Ú MkDocsConfig)ÚLiveReloadServer)ÚFiles)Ú
Navigation)ÚPage)ÚTemplateContext)Ú ConcatenateÚ ParamSpecÚmkdocs.pluginscó¢td¬«}i}|D];}|j|vr|jjd«rŒ-|||j<Œ=|S)z=Return a dict of all installed Plugins as {name: EntryPoint}.r )Úgroupzmkdocs.contrib.)rÚnameÚvalueÚ
startswith)ÚpluginsÚ pluginmapÚplugins úQ/home/antigravity/intellecton/venv/lib/python3.12/site-packages/mkdocs/plugins.pyÚ get_pluginsr*(sZäÐ!1Ô2€Gð€IØòØ ;‰;˜)Ñ ¯ © ×(?Ñ(?Ð@QÔ(RØ à!'ˆ &—+ð  ÐóÚ
SomeConfig)Úboundcó¤eZdZUdZeZded<dZded<iZded<d Z d
ed < d#d Z
d
Z d$ d%dZ d&dZ
d'dZ d(dZd)dZd*dZd+dZ d,dZ d-dZd*dZd.dZ d/dZ d0dZ d1dZd2dZd3dZ d4dZ 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|jd|jd}t||ft|¬««S)z_Eliminates the need to write `config_class = FooConfig` when subclassing BasePlugin[FooConfig].ú])r0)Ú__name__ÚtypeÚdict)Úclsr0r#s r)Ú__class_getitem__zBasePlugin.__class_getitem__Hs5à—,,˜×!6Ñ!6Ð 7°qÐ9ˆÜD˜3˜&¤$°LÔ"AÓBr+cóÆt|jt«std|jd«|jtur|jj
|_yy)Nz
config_class z2 must be a subclass of `mkdocs.config.base.Config`)Ú
issubclassr0rÚ TypeErrorrÚ_schemar2)r<s r)Ú__init_subclass__zBasePlugin.__init_subclass__Ms\ܘ#×*¬FÔØ × 0Ñ 0Ð1Ð1cÐð
ð × Ñ ¤<Ñ /Ø #× 0Ñ 0× 8Ñ 8ˆ ð 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)r0rr2r3Ú load_dictÚvalidate)ÚselfÚoptionsrDs r)Ú load_configzBasePlugin.load_configUsbð × Ñ ¤ Ñ & t×'9Ñ'9ÐL\Ô]ˆD×+Ð=MÐNˆDŒKà ×јgÔ{‰{×%r+cóy)a
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.
Nr1©rGÚcommandÚdirtys r)Ú
on_startupzBasePlugin.on_startupdór+cóy)
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.
Nr1©rGs r)Ú on_shutdownzBasePlugin.on_shutdownurOr+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
r1©rGÚserverr3Ú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
r1©rGr3s r)Ú on_configzBasePlugin.on_configœs ðˆ
r+cóy)
The `pre_build` event does not alter any variables. Use this event to call
pre-build scripts.
Args:
config: global configuration object
Nr1rYs r)Ú on_pre_buildzBasePlugin.on_pre_buildªrOr+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
r1©rGÚfilesr3s 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
r1©rGÚnavr3r_s 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
r1©rGÚenvr3r_s 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
Nr1rYs r)Ú
on_post_buildzBasePlugin.on_post_buildçrOr+cóy)
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
Nr1©rGÚerrors r)Úon_build_errorzBasePlugin.on_build_errorðrOr+có|S)
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
r1©rGÚtemplateÚ
template_namer3s 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
r1©rGÚcontextrrr3s 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
r1©rGÚoutput_contentrrr3s 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: `mkdocs.structure.pages.Page` instance
config: global configuration object
files: global files collection
Returns:
`mkdocs.structure.pages.Page` instance
r1©rGÚpager3r_s r)Ú on_pre_pagezBasePlugin.on_pre_page6s ðˆ r+cóy)
> 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.
Nr1©rGrr3s r)Úon_page_read_sourcezBasePlugin.on_page_read_sourceEsð$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: `mkdocs.structure.pages.Page` instance
config: global configuration object
files: global files collection
Returns:
Markdown source text of page as string
r1©rGÚmarkdownrr3r_s r)Úon_page_markdownzBasePlugin.on_page_markdownYs ð"ˆr+có|S)
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
r1©rGÚhtmlrr3r_s r)Úon_page_contentzBasePlugin.on_page_contentls ð"ˆ r+có|S)
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
r1©rGrvrr3rcs r)Úon_page_contextzBasePlugin.on_page_contextrxr+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: `mkdocs.structure.pages.Page` instance
config: global configuration object
Returns:
output of rendered template as string
r1©rGÚoutputrr3s r)Ú on_post_pagezBasePlugin.on_post_pages ðˆ
r+)r0z type[Config]©N)rHzdict[str, Any]rDú
str | NoneÚreturnz#tuple[ConfigErrors, ConfigWarnings]©rLz&Literal['build', 'gh-deploy', 'serve']rMr4r•ÚNone©r•r—)rUrr3rrVrr•zLiveReloadServer | None)r3rr•zMkDocsConfig | None©r3rr•r—)r_rr3rr•z Files | None)rcrr3rr_rr•zNavigation | None)rgújinja2.Environmentr3rr_rr•zjinja2.Environment | None©rmÚ Exceptionr•r—)rqújinja2.TemplaterrÚstrr3rr•zjinja2.Template | None)rvrrrr3rr•úTemplateContext | None)r{rrr3rr•r”)rrr3rr_rr•z Page | None©rrr3rr•r”)
r†rrr3rr_rr•r”)
rrr3rr_rr•r”)
rvrrrr3rrcrr•)rrrr3rr•r”) r9Ú
__module__Ú __qualname__Ú__doc__rr0Ú__annotations__r2r3r5r=rBrIrNrRrWrZr\r`rdrhrjrnrsrwr|r€r‡rrr1r+r)r/r/:ñð &2€LÐ1Ø')€MЀFˆà(-РÓCò
GKð  &Ø9Cð &à ,ó  ó" ð"ØØ6BðØMUðà óó, ó óð"ØðØ-9ðØBGðà óð"ØØ5AðØJOðà "óó$ ó
 ðØØ>AðØKWðà óð"ØØ=@ðØJVðà óð$ØØ8;ðØEQðà óó*
óð(ØðØ)-ðØ7CðØLQðà óð&ØðØ%)ðØ3?ðØHMðà óð&ØØ48ðØBNðØU_ðà óô$r+r/c#óJK|]}|jd«sŒ|ddŒy­w)Úon_r r%)Ú.0Úks r)ú <genexpr>rª£s!èø€Ò°Q·\±\À%Õ5HˆqŒuÑIùs#
#cóˆfd}|S)
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ó|_|Sr“)Úmkdocs_priority)Ú event_methodÚprioritys €r)Ú decoratorz!event_priority.<locals>.decoratorÅsø€Ø'/ˆ ÔÐr+r1)s` r)Úevent_priorityr±ªsø€ô6ð Ðr+có(eZdZdZddZddZddZy) Ú
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)rGs r)Ú__init__zCombinedEvent.__init__âs ؈ r+cóDtt|«jd«)Nz object is not callable)r@r:r9)rGÚinstanceÚargsÚkwargss r)Ú__call__zCombinedEvent.__call__æs Üœ4 1Ð1HÐJr+Ncó>tˆˆfd|jD«ŽS)Nc3óBK|]}|j«Œy­wr“)Ú__get__)Úfr¸Úowners €€r)z(CombinedEvent.__get__.<locals>.<genexpr>êsøèø€ÒP¸a˜qŸy™y¨°5×Pùsƒ))rGr¸s ``r)zCombinedEvent.__get__ésù€ÜÔPÀ4Ç<Á<ÔQr+)z Callable[Concatenate[Any, P], T])r¸r/zP.argsrºzP.kwargsr•rr“)r9r1r+r)Ìsñó*óKôRr+cóeZdZUdZded<dˆfd Z d d dZd!ˆfd Zd"ˆfd Ze d#d«Z
e d$d „«Z
dd%d
Z
d&d Z dd Z d'd
Z
d(dZd)dZd*dZd+dZd,dZd)dZd-dZ d.dZ d/dZ d0dZd1dZd2dZ d3dZd4dZ d5dZd6dZˆxZS)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ópt||i|¤ŽtDcic]}|gŒc}|_i|_ycc}wr“)Úsuperr¶ÚEVENTSÚeventsÚ_event_origins)rGÚ __class__s €r)zPluginCollection.__init__øs9ø€Ü
ј) )ÜAGÖ1H¸A°!°R±%Ò1HˆŒ Ø35ˆÕùò2Is
3cóÊt|t«r&|jD]}|j|||¬«Œy
|j|}|dk(r^t |«dk(rP|j jtt|««d«}|xsd}tjd|d|d«tj||d¬ «|r ||j |<y
y
#t$rYy
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|dd« S)Nr­r)Úgetattr)Úms r)ú<lambda>z2PluginCollection._register_event.<locals>.<lambda>
s¼ÀÐCTÐVWÓ8XÐ7X€r+)ÚkeyN)Ú
isinstancer³Ú_register_eventrÇÚlenrÈÚgetÚnextÚiterÚlogÚwarningrÚinsortr@)rGÚ
event_nameÚmethodrÌÚsubrÇÚplugin1Úplugin2s r)z PluginCollection._register_eventýô fœmÔ —~‘~ò
OØ×$ Z°À+Ð
Oð—[‘[ Ñ,ˆFØÐ/´C¸³KÀ1Ò4DØ×1´$´t¸F³|Ó2DÀkÓRØÜ ð&Ø&- Y¨g°g°YÐ>PðRôô
L‰L˜ Ñ-XÕ ðØ2=D×ÒøôÙðúsÃCà C"Ã!C"có"t||«Sr“)Ú __getitem__)rGs €r)zPluginCollection.__getitem__sø€Ü‰wÑ" 'r+có´t|||«dt|«D«D]2}t||d«}t |«sŒ|j |dd||¬«Œ4y)Nc3óDK|]}|jd«sŒ|Œy­w)Nr§)Úxs r)z/PluginCollection.__setitem__.<locals>.<genexpr>sèø€ÒH °A·L±LÀÕ4Gœ1ÑHùs  r )Ú __setitem__ÚdirrÑÚcallablerÖ)rGr$s €r)zPluginCollection.__setitem__s]ø€Ü
јC ÔH¤c¨%£jÔ NˆJܘU J°Ó5ˆFÜ˜ÕØ×$ Z°° ^°VÈÐ Nr+c óyr“r1)rGr#s r)Ú run_eventzPluginCollection.run_eventóà r+c óyr“r1)rGr#Úitemrºs r)zPluginCollection.run_event#r+c óN|du}|j|D]‡}|jj|d«|_tj «t jkr&tjd|d|jd«|r
||fi|¤Ž}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 'ú'r1) rÇÚgetEffectiveLevelÚloggingÚDEBUGÚdebug)rGr#Ú pass_itemrßÚresults r)zPluginCollection.run_event'ð Ð$ˆ Ø—kk 
ˆFØ#'×#6Ñ#6×#:Ñ#:¸6À;Ó#Oˆ Ü×&¬'¯-©-Ò ˜I d VÐ+@À×AUÑAUÐ@VÐVWÐÙ ÑÑ/‘áÑ) &Ñ)àÑð
ðÔØˆ r+có*|jd||¬«S)startup)rLrM©rKs r)rNzPluginCollection.on_startup?sØ~‰~˜ÀˆFr+có$|jd«S)shutdownrúrQs r)rRzPluginCollection.on_shutdownBsØ~‰~˜)r+có,|jd|||¬«S)serve)r3rVrTs r)rWzPluginCollection.on_serveEsð~‰~˜g v°fÀgˆNr+có&|jd|«S)Nr3rYs r)rZzPluginCollection.on_configJsØ~‰~˜Ó/r+có(|jd|¬«S)NÚ pre_build©r3rYs r)r\zPluginCollection.on_pre_buildMsØ~‰~˜k°&ˆ9r+có*|jd||¬«S)Nr_rr^s r)r`zPluginCollection.on_filesPsØ~‰~˜g u°Vˆ<r+có,|jd|||¬«S)Nrc©r3r_rbs r)rdzPluginCollection.on_navSóØ~‰~˜e ¸uˆEr+có,|jd|||¬«S)Nrgrrfs r)rhzPluginCollection.on_envVrr+có(|jd|¬«S)
post_buildrrYs r)rjzPluginCollection.on_post_buildYsØ~‰~˜l°6ˆ:r+có(|jd|¬«S) build_error)rmrls r)rnzPluginCollection.on_build_error\sØ~‰~˜m°5ˆ9r+có,|jd|||¬«S) pre_template©rrr3rps r)rsz PluginCollection.on_pre_template_sð~‰~˜n¨hÀmÐ\bˆcr+có,|jd|||¬«S)template_contextrrus r)rwz$PluginCollection.on_template_contextds#ð~‰~Ø  °}ÈVðó
ð
r+có,|jd|||¬«S)
post_templaterrzs r)r|z!PluginCollection.on_post_templateks$ð~‰~Ø ˜^¸=ÐQWðó
ð
r+có,|jd|||¬«S)pre_pagerr~s r)r€zPluginCollection.on_pre_pagersØ~‰~˜j¨$°vÀUˆKr+có*|jd||¬«S)NrÍ©rr3rs r)z$PluginCollection.on_page_read_sourceusØ~‰~Ð0°tÀFˆKr+có.|jd||||¬«S)
page_markdown©rr3r_r…s r)r‡z!PluginCollection.on_page_markdownxsð~‰~˜o¨x¸dÈ6ÐY^ˆ_r+có.|jd||||¬«S) page_contentrr‰s r)rz PluginCollection.on_page_content}sØ~‰~˜n¨d¸ÀfÐTYˆZr+có.|jd||||¬«S) page_context)rr3rcrs r)z PluginCollection.on_page_context€sð~‰~˜n¨g¸ÐUXˆYr+có,|jd|||¬«S)NÚ post_pagerrs r)rzPluginCollection.on_post_page…sØ~‰~˜k¨6¸ÀVˆ~ÓLr+r˜r“)zCombinedEvent | CallablerÌr”r•r—)r•r/)r$r/r•r—)r#r•r)r#rr•r)r#r)rUrr3rrVrr•r)r3rr•rr™)r_rr3rr•r)rcrr3rr_rr•r)rgr3rr_rr)rqrrrr3rr•r)rvrrrr3rr•r)r{rrr3rr•)rrr3rr_rr•rr )
r†rrr3rr_rr•)
rrr3rr_rr•)
rvrrrr3rrcrr•r)rrrr3rr•)r9r rNrRrWrZr\r`rdrhrjrnrsrwr|r€r‡rr’Ú
__classcell__©s@r)íø…ñð Óõ \`ðØðØ'?ðØNXðà
óõ.Nðò óð ðò óð ôó0GóOØOØ3?ðOØJRðOà óOó
FóFódØdØ;>ðdØHTðdà ódð

Ø
Ø:=ð
ØGSð
à ó
ð
Ø
Ø58ð
ØBNð
à ó
óLóLð`Øð`Ø&*ð`Ø4@ð`ØINð`à ó`ó
[ðZØZØ15ðZØ?KðZØR\ðZà óZ÷
Mr+có,eZdZdZdˆfd ZddZˆxZS)ÚPrefixedLoggerz(A logger adapter to prefix log messages.có4t||i«||_y)
Initialize the logger adapter.
Arguments:
prefix: The string to insert in front of every message.
logger: The logger instance.
N)Úprefix)rGr%ÚloggerrÉs €r)zPrefixedLogger.__init__Œsø€ô ј Ôˆ r+có(|jd||fS)
Process the message.
Arguments:
msg: The message: