Saravanan666/pypi-org huggingface dataset:
Package: pelican-injector
Injector: A Plugin for PelicanInjector is a plugin for thePelicanstatic site generator that allows users to inject custom code before or after specific HTML tags, without modifying your theme.InstallationThis plugin can be installed via:python -m pip install pelican-injectorAs long as you have not explicitly added aPLUGINSsetting to your Pelican settings file, then the newly-installed plugin should be automatically detected and enabled. Otherwise, you must addinjectorto your existingPLUGINSlist. For more information, please see theHow to Use Pluginsdocumentation.SettingsTo configure the plugin, set theINJECTOR_ITEMSvariable in your
Pelican settings file. This should be a list of tuples, each with two
or three elements, according to this table:Tuple ElementDescriptionFirstName of the HTML tag where you want to inject your codeSecondThe code you want to injectThird (optional)Specifies where to inject the code: 'before' or 'after'. If not provided, it defaults to 'after'INJECTOR_ITEMS=[('head','<script>...</script>','after'),('body','<div>...</div>','before'),//addmoretagsandcodeasneeded]In the following example, a script logging "Hello, world!" to the console is
injected into the<head>tag of each page, and a style block is injected
before the<body>tag.INJECTOR_ITEMS=[('head','<script>console.log("Hello, world!");</script>'),('body','<style>.custom-style { color: red; }</style>','before'),]INJECTOR_IN_PAGES=TrueINJECTOR_IN_ARTICLES=FalseContributingContributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting onexisting issues.To start contributing to this plugin, review theContributing to Pelicandocumentation, beginning with theContributing Codesection.LicenseThis project is licensed under theMIT license.ContactIf you have any questions or feedback, please open an issue on GitHub.
Package: pelican-jinja-filters
Jinja Filtersis a plugin forPelican,
a static site generator written in Python.Jinja Filtersprovides a selection of functions (calledfilters) for
templates to use when building your website. They are packaged for Pelican, but
may prove useful for other projects that make use ofJinja2.InstallationThe easiest way to installJinja Filtersis through the use of Pip. This
will also install the required dependencies (currentlypelicanandtitlecase) automatically.pipinstallpelican-jinja-filtersAsJinja Filtersis a namespace plugin, assuming you are using Pelican 4.5
(or newer)andonlyother namespace plugins,Jinja Filterswill be
automatically be loaded by Pelican. And that’s it!If you are using an older version of Pelican, or non-namespace plugins, you may
need to addJinja Filtersto yourpelicanconf.py:PLUGINS=[# others..."pelican.plugins.jinja_filters",]The filters are now available for use in your templates.Jinja Filterssupports Pelican from version 3 on.UsageAt present, the plugin includes the following filters:datetime– allows you to change to format displayed for a datetime
object. Optionally supply adatetime format stringto get a custom format.article_date– a specialized version ofdatetimethat returns
datetimes as wanted for article dates; specificallyFriday, November 4, 2020.breaking_spaces– replaces non-breaking spaces (HTML code&nbsp;)
with normal spaces.titlecase– Titlecases the supplied string.datetime_from_period– take theperiodprovided on period archive
pages, and turn it into a proper datetime.datetime object (likely to feed to
another filter)merge_date_url– given a datetime (on the left) and a supplied URL,
“apply” the date to it. Envisioned in particular forYEAR_ARCHIVE_URL,MONTH_ARCHIVE_URL, andDAY_ARCHIVE_URL.For example, within your theme templates, you might have code like:<spanclass="published">Article Published{{article.date|article_date}}</span>gives:Article Published Friday, November 4, 2020Or with your own date format:<spanclass="published">Article Published{{article.date|datetime('%b %d, %Y')}}</span>gives:Article Published Nov 04, 2020Filters can also be chained, or applied in sequence. For example to remove
breaking spaces and then titlecase a category name, you might have code like:<ahref="{{SITEURL-}}/{{-article.category.url}}">{{article.category|breaking_spaces|titlecase}}</a>On a Monthly Archive page, you might have the following to link “up” to the
Yearly Archive page:<ahref="{{SITEURL-}}/{{-period|datetime_from_period|merge_date_url(YEAR_ARCHIVE_URL)}}">{{period|datetime_from_period|datetime('%Y')}}</a>which might give:<a href="https://blog.minchin.ca/posts/2017/>2017</a>ContributingContributions are most welcome! SeeContributingfor more details.To set up a development environment:Fork the project on GitHub, and then clone your fork.Set up and activate a virtual environment.Haveinvokeon your system path or install it into your virtual
environment.Runinvoke setup.For more details, seeContributing.LicenseJinja Filtersis under the MIT License. See attachedLicense.txtfor
full license text.
Package: pelican-jsfiddle
Easily embed JSFiddle in your Pelican articles.InstallationTo install pelican-jsfiddle, simply install it from PyPI:$pipinstallpelican-jsfiddleThen enabled it in your pelicanconf.pyPLUGINS=[# ...'pelican_jsfiddle',# ...]UsageIn your article or page, you simply need to add a line to embed your JSFiddle...jsfiddle::FIDDLE_IDWhich will result in:<divclass="jsfiddle"><iframeallowfullscreen="allowfullscreen"frameborder="0"height="300"src="http://jsfiddle.net/<FIDDLE_ID>/embedded/js,resources,html,css,result/light/"width="100%"></iframe></div>Additional argumentsYou can also specify a width, height, tabs and skin...jsfiddle::if1live/V2P28:width:100%:height:300:tabs:js,resources,html,css,result:skin:lightWhich will result in:<divclass="jsfiddle"><iframeallowfullscreen="allowfullscreen"frameborder="0"height="300"src="http://jsfiddle.net/if1live/V2P28/embedded/js,resources,html,css,result/light/"width="100%"></iframe></div>
Package: pelican-jupyter-reader
pelican-jupyter-reader: A Plugin for PelicanThisPelicanplugin provides a Jupyter Notebook (i.e.*.ipynb) reader.
The plugin intends to allow users to simply drop Jupyter notebooks in their
Pelican content directory and have the notebooks rendered (beautifully) in a Pelican
static website.InstallationThis plugin can be installed via:pip install pelican-jupyter-readerQuickstartAdd the plugin topelicanconf.py:# ...frompelican.pluginsimportpelican_jupyter_readerPLUGINS=[pelican_jupyter_reader]# ...ProvidePelican post
metadataas
a top-level object with keypelicanin the Jupyter notebook metadata:{"pelican":{"date":"2020-04-10","title":"this is a title","tags":"thats, awesome","category":"yeah","slug":"my-super-post","authors":"Alexis Metaireau, Conan Doyle","summary":"Short version for index and feeds"},"kernelspec":{"display_name":"Python 3","language":"python","name":"python3"},//...the rest of the notebook JSON follows.Drop your Jupyter notebook in the Pelican content directory, build your site,
and deploy!  :rocket:ExampleThedemo/directory has a simple post with corresponding configuration inpelicanconf.py. The demo site is deployedhere.NotesThe Jupyter nbconvert configuration forpreprocessorsand theHTMLExporterare exposed in your Pelican config,pelicanconf.py.  This
means you can manipulate notebooks with utilities provided bynbconvert.For example, to use thebasictemplate for theHTMLExporter, you could add
the following to yourpelicanconf.py:fromtraitlets.configimportConfigNBCONVERT_CONFIG=Config()NBCONVERT_CONFIG.HTMLExporter.template='basic'To strip empty cells from the notebook before publishing, you might add this
option topelicanconf.py:# ...NBCONVERT_CONFIG.RegexRemovePreprocessor.patterns=['\\s*\\Z']Othernbconvertconfiguration options can be foundhere.
Package: pelican-link-bugs
Automatically link bug/issue references in content to a tracker.By default it will link pull-requests and issues for github
in the following formats:* I should reiview PR mozilla/bedrock#1.
* Don't forget to watch issue twbs/bootstrap#2.It will also link to Mozilla’s bugzilla instance:Need a laugh? Read bug 765645.You can easily replace these or add to them with a setting:BUG_TRACKERS={# key is the regexr'issue +(?P<bug_repo>[a-z1-9-_/]+)#(?P<bug_id>\d+)':# value is URL template with keywoard substitutions'https://github.com/{bug_repo}/issue/{bug_id}',}You can also importBUG_TRACKERSfrompelican_bugsand modify it.
If you need to alter how the links look, you can setBUG_LINK_TEMPLATE.
The link template can usebug_urlandbug_textkeywords:# default templateBUG_LINK_TEMPLATE='<a href="{bug_url}">{bug_text}</a>'
Package: pelican-linkclass
Link Class: A Plugin for PelicanThis Pelican plugin allows you to set the class attribute of<a>elements
(generated in Markdown by[ext](link)) according to whether the link is
external (i.e., starts withhttp://orhttps://) or internal to the
Pelican-generated site.For now, this plugin only works with Markdown. It has been tested with version
3.0+ of the Python-Markdown module and may not work with previous versions.InstallationThis pluginis available as a packageat PyPI and can be installed via:python -m pip install pelican-linkclassConfigurationIn order to avoid clashes with already-defined classes in the user CSS
style sheets, it is possible to specify the name of the classes that will
be used. They can be specified in the Pelican setting file with theLINKCLASSvariable, which must be defined as a list of tuples, like this:'LINKCLASS'=(('EXTERNAL_CLASS','name-of-the-class-for-external-links'),('INTERNAL_CLASS','name-of-the-class-for-internal-links'))The default values forEXTERNAL_CLASSandINTERNAL_CLASSare,
respectively,'external'and'internal'.Styling HyperlinksOne of the possible uses of this plugins is for styling. Suppose that we
have the following Markdown content in your article:This is an [internal](internal) link and this is an
[external](http://external.com) link.If the default configuration variable values are used, then one possible
CSS setting could be:a.external:before{content:url('../images/external-link.png');margin-right:0.2em;}(The fileexternal-link.pngis also distributed with this plugin. To use it,
copy it to the appropriate place in your web site source tree, for instance
intheme/static/images/.)Then, the result will look like the following:Note that this plugin also works with reference-style links, as in the
following example:This is an [internal][internal] link and this is an
[external][external] link.

 [internal]:internal[external]:http://external.comContributingContributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting onexisting issues.To start contributing to this plugin, review theContributing to Pelicandocumentation, beginning with theContributing Codesection.AcknowledgmentsMany thanks toYuliya Bagriyfor setting up the package forPyPI, toLucas Cimonfor fixing the issues withpytest, and toJustin Mayerfor helping with migration of this plugin under the Pelican Plugins organization.AuthorCopyright © 2015, 2017, 2019, 2021-2023 Rafael Laboissière (rafael@laboissiere.net)LicenseThis project is released under the terms of the GNU Affero Public License, version 3 or later.
Package: pelican-linkedin-profile
Extract a LinkedIn profile and allow the use of his informations in Pelican’s pagesInstallationTo install pelican-linkedin, simply install it from PyPI:$pipinstallpelican-linkedin-profileConfigurationEnable the plugin in your pelicanconf.pyPLUGINS=[# ...'pelican-linkedin-profile',# ...]Add mandatory settings containing your LinkedIn Api Keys.LINKEDIN_USER_TOKEN='XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'LINKEDIN_USER_SECRET='XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'LINKEDIN_CONSUMER_KEY='XXXXXXXXXXXXXX'LINKEDIN_CONSUMER_SECRET='XXXXXXXXXXXXXXXX'LINKEDIN_RETURN_URL='http://example.com/'Available dataformattedName:The member’s name, formatted based on language.headline:The member’s headline.summary:A long-form text area describing the member’s professional profile.pictureUrl:A URL to the member’s formatted profile picture, if one has been provided.emailAddress:The LinkedIn member’s primary email address.primaryTwitterAccount:The primary Twitter account associated with the member.publicProfileUrl:The URL to the member’s public profile on LinkedIn.phoneNumbers:A list of phone number objects containing those fields : phoneNumber, phoneType (home, work or mobile.)skills:A list of skill’s namelanguages:A list of language’s nameeducations:A list of eduction objects containing those fields : startDate, endDate, degree, schoolName, fieldOfStudypositions:A list of position objects containing those fields : startDate, endDate, title, company, summary, isCurrent. A company object contains those fields : industry, size, type, nameUsageIn your templates you will have access to a linkedin_profile variable as below.<div><h2>{{ linkedin_profile.formattedName }}</h2><p>{{ linkedin_profile.headline }}</p></div>LicenseGPLv2license.
Package: pelican-manager
Pelican manager[![Build Status](https://travis-ci.org/xiaojieluo/pelican-manager.svg?branch=master)](https://travis-ci.org/xiaojieluo/pelican-manager)
[![codecov](https://codecov.io/gh/xiaojieluo/pelican-manager/branch/master/graph/badge.svg)](https://codecov.io/gh/xiaojieluo/pelican-manager)## 0.2.1
修复在后台设置 debug 值不正确的错误
当文章中不存在 Status 元数据时， 默认为 published.## 0.2 (2018-02-03)
- 当 metadata 不存在时， 在文章中插入 metadata
- 读取 pelicanconf.py 的 ARTICLE_PATH 变量作为文章存放的位置。
- 将 pelican_manager 配置存入 pelicanconf.py 文件中， 放弃 pelican_manager.toml
- 添加 -c 参数， 用来指定 pelican 的 config 文件## 0.1.1 (2018-02-01)
- fix some bug.## 0.1 (2018-01-29)
- The first edition, which lists all articles, can modify their metadata
Package: pelican-markdown-image
Pelican Markdown Image ProcessorThis pelican plugin allows you to use native markdown syntax to reference images,
no matter whether the image is in your statics folder. This can help you use whatever
directory structure to store the images.Installationpip install pelican-markdown-imageDevelopmentGenerating distribution archives:python -m buildInstall this package in development mode:pip install -e . --no-build-isolation(We must add the --no-build-isolation option,
this can be a pip's bug)Upload to pypi:twine upload dist/*
Package: pelican-markdown-include
Markdown Include: A Plugin for PelicanThis plugin allows the use of theMarkdown-Include extensionin Pelican articles.InstallationThis plugin can be installed via:python -m pip install pelican-markdown-includeAs long as you have not explicitly added aPLUGINSsetting to your Pelican settings file, then the newly-installed plugin should be automatically detected and enabled. Otherwise, you must addmd_includeto your existingPLUGINSlist. For more information, please see theHow to Use Pluginsdocumentation.UsageThe syntax for use within Pelican articles is{!filename!}. According to the documentation of theMarkdown-Include extension, this statement will be replaced by the contents offilenameand will work recursively. The replacement is done prior to any other Markdown processing, so any Markdown syntax that is wanted can be used within the included files. For more details, see theMarkdown-Include extension documentation.ConfigurationThe following variables control the behavior of the plugin and can be set in the Pelican settings file:MD_INCLUDE_BASE_PATH: By default, the file name is given relative to the directory from where Pelican is run. This can be changed via this variable.MD_INCLUDE_ENCODING: The encoding of the included files. Default:"utf-8"MD_INCLUDE_INHERIT_HEADING_DEPTH: IfTrue, increases headings on included file by amount of previous heading. Combines withMD_HEADING_OFFSEToption below. Default:FalseMD_HEADING_OFFSET: Increases heading depth by a specific amount, in addition to theMD_INCLUDE_INHERIT_HEADING_DEPTHoption. Default:0Alternatives to this PluginPelican allows the use of extra Markdown extensions by declaring them in theMARKDOWNconfiguration variable.  However, asexplainedin the Pelican documentation, adding new extensions via theMARKDOWNsetting is awkward, because all the extensions loaded by default must also be explicitly listed. In addition to avoiding this problem, this plugin provides a “Pelican-ish” way of setting the configuration values of the Markdown-Include extension (base_path,encoding,inherit_heading_depth, andheading_offset).  Furthermore, theMarkdown-Include extensionmust be installed in a place where Pelican can find it, which may be tricky.ContributingContributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting onexisting issues.To start contributing to this plugin, review theContributing to Pelicandocumentation, beginning with theContributing Codesection.AcknowledgmentsThanks toJustin Mayerfor helping with migration of this plugin under the Pelican Plugins organization.AuthorCopyright © 2015, 2021-2023 Rafael Laboissière (rafael@laboissiere.net)LicenseThis project is licensed under the terms of the the AGPL-3.0 license.
Package: pelican-markdown-it-reader
Markdown-IT reader: A Plugin for PelicanReader plugin for Markdown-IT-py replacementThis is double-opinionated, in that it's opinionated using Markdown-IT
and again because we add in some additions; in particular:TablesfootnotesPygment-based syntax highlightingInstallationThis plugin can be installed via:python -m pip install pelican-markdown-it-readerUsageThere are currently no configuration items.Once installed it takes over responsibility for reading the following file extensions:mdmarkdownmkdmdownBy taking overlink_openandimagerender rules, the plugin handles replacing the
pelican link placeholders with appropriatehrefitems which are then rendered to html.ContributingContributions are welcome and much appreciated. Every little bit helps.
You can contribute by improving the documentation, adding missing features,
and fixing bugs. You can also help out by reviewing and commenting onexisting issues.To start contributing to this plugin, review theContributing to Pelicandocumentation, beginning with theContributing Codesection.LicenseThis project is licensed under the MIT license.
Package: pelican-markdown-unrendered-metadata
Pelican Markdown Unrendered MetadataRead Pelican metadata from link references.UsageWrite metadata in the form[//Pelican/KEY]: # (VALUE).
They can be placed anywhere in the document.
If the first text content is a top-level heading,
the heading is removed from the document, and used as the title.
For example,# Hello, world![//Pelican/date]:# (2000-10-31 00:00)[//Pelican/author]:# (Noname)Goodbye, world!The equivalent MultiMarkdown document used by Pelican would betitle: Hello, world!
date: 2000-10-31 00:00
author: Noname

Goodbye, world!If a key has multiple sources (references, MultiMarkdown, heading),
the order of stored value is unspecified.InstallationIfPLUGINSis not specified insidepelicanconf.py,
then installing this package should be sufficient setup.python-mpipinstallpelican-markdown-unrendered-metadataOtherwise, insidepelicanconf.py,
addmarkdown_unrendered_metadatato thePLUGINSlist variable.Raison d'êtrePelican metadata of Markdown documents
are colon-separated key-value pairs at the beginning of the document.
Markdown parsers see them as a block of text
and generate an unintended paragraph when rendered.To mitigate this, the metadata can be embedded
inside a form of Markdown comments.
This plugin uses link references as comments, suggested by aStackOverflow answer:[//]:# (This may be the most platform independent comment)
Package: pelican-mboxreader
pelican-mboxreaderThis pelican plugin adds a generator that can load a Unix style mbox file and
generate articles from all the entries in the mailbox.This was written to support easy interoperation between pelican and mailman
(which creates mbox archives). Future work, if done, will involve improving the
way (plaintext) email is turned into HTML and adding support for additional
mail directory types.Do I need other dependencies?Yes; you need python's dateutil module (so dates in emails can be parsed without
assuming a standard time format).Thesetup.pyscript will automatically take care of this when installing
the package.How do I install it?pelican-mboxreader is packaged and available from PyPI; to install it, you can
simply run the following command:pip install pelican-mboxreader.Alternatively, you can clone the git repository, build it, and install it
yourself by runningpython setup.py install.How does it work?Enable it using any other Pelican plugin, though note that the plugin is namedpelican_mboxreader, then add it to the configuration as follows:PLUGINS = [
    # ...
    'pelican_mboxreader',
    # ...
]Then add the following settings to the configuration:MBOX_PATH = ['/path/to/mail.box']
MBOX_CATEGORY = ['Name of Mbox Category']MBOX_PATHdefaults to "input.mbox" in the current directory. If it is not present,
Pelican should behave gracefully. ```MBOX_CATEGORY`` defaults to "Mailbox".As you might gather from these settings being lists, mboxreader supports taking input
from multiple Mailbox files. You must have one category name per mbox path.Other Configuration OptionsMBOX_AUTHOR_STRING = ''This string is appended to the end of authors created via mbox. This is used to
provide a way to distinguish authors via email and authors via normal Pelican,
if you want that. It is now disabled by default.MBOX_MARKDOWNIFY = FalseThis setting controls whether to feed input emails into Markdown or whether they should
be converted "manually" (i.e. replacing newlines with paragraph tags and break tags as
appropriate), which is the default. Markdown is the closest to "plaintext" (compare to
reStructuredText) though in the future I'll likely add an option to use the rST parser
instead.Is support for other mailbox types (maildir, etc.) possible?Yes. It would need to be programmed in and made configurable, however it would
be trivial if the mailbox type is implemented bypython's mailbox module(which is what this uses).Is this pointless?Maybe. See the above note about mailman; it was written for a reason but may not
be something that anyone in the real world actually needs.CreditsBen Rosserrosser.bjr@gmail.comWritten for use by theJHUACM.