Saravanan666/pypi-org huggingface dataset:
Package: lekkersim
LekkerSIM packageLekkerSIM is a open source package for linear simulation of photonic circuit, based on the well known scattering matrix method.
Its features include:Easy calculation of S-parameters of a photonic circuit;A collection of pre-defined building blocks for easy definition of circuits;Parametric building blocks;Hierarchical circuit definition;Monitors inside the circuit for calculation of power flow.InstallationYou can install LekkerSIM directly from pypi by running:pip install lekkersimDocumentationFull documentation is available onRead the Docs.
Package: lektor-asciidoctor
Lektor AsciiDoc PluginALektorplugin to add an AsciiDoc field type. This is a fork of the pluginlektor_asciidocpublished by@nixjdm.This version, now called lektor asciidoctor requires ruby and asciidoctor which is the origin of the for as agreed inthispull request.RequirementsGo toruby-lang.organdasciidoctor.orgfor installation instructions of both.InstallationAdd lektor-asciidoc to your project from command line:lektor plugins add lektor-asciidoctor
Package: lektor-atom
Lektor Atom PluginBuilds one or more Atom XML feeds for yourLektor-based site.Inspired by theatom-feed-supportplugin Armin Ronacher wrote for the Lektor official blog.InstallationAdd lektor-atom to your project from command line:lektorpluginsaddlektor-atomSeethe Lektor documentation for more instructions on installing plugins.ConfigurationHere is a basic configuration:[feed]name=My Site's Blogsource_path=/blogurl_path=/feed.xmlFor each feed you want to publish, add a section toconfigs/atom.ini. For example, a blog with a feed of all recent posts, and a feed of recent posts about coffee:[blog]name=My Blogsource_path=/url_path=/feed.xmlitems=site.query('/').filter(F.type == 'post')item_model=blog-post[coffee]name=My Blog: Articles About Coffeesource_path=/url_path=/category/coffee/feed.xmlitems=site.query('/blog').filter(F.categories.contains('coffee'))item_model=blog-postThe section names, likeblogandcoffee, are just used as internal identifiers.OptionsOptionDefaultDescriptionsource_path/Where in the content directory to find items' parent sourcenameconfig section nameFeed namefilenamefeed.xmlName of generated Atom feed fileurl_pathsource_path + filenameFeed's URL on your siteblog_author_fieldauthorName of source's author fieldblog_summary_fieldsummaryName of source's summary fielditemssource_path's childrenA query expression: e.g.site.query('/').filter(F.type == 'post')limit50How many recent items to includeitem_title_fieldtitleName of items' title fielditem_body_fieldbodyName of items' content body fielditem_author_fieldauthorName of items' author fielditem_date_fieldpub_dateName of items' publication date fielditem_modelNoneFiltersitemson name of items' modelCustomizing the plugin for your modelsUse the field options to tell lektor-atom how to read your items. For example, if your site's model is:[model]name=Blog[fields.writer]type=string[fields.short_description]type=stringThen add to atom.ini:[main]blog_author_field=writerblog_summary_field=short_descriptionSeetests/demo-project/configs/atom.inifor a complete example.Filtering itemsBy default, lektor-atom gets the source atsource_pathand includes all its children in the feed. If you setitem_model, lektor-atom includes only the children with that data model.Setitemsto any query expression to override the default. Ifitems_modelisalsospecified, lektor-atom applies it as a filter toitems.Use In TemplatesYou can link to a specific feed in your template. If youratom.inicontains a feed like this:[main]source_path=/blogLink to the feed in a template like this:{{ '/blog@atom/main'|url }}
Package: lektor-bibtex-support
Lektor Bibtex PluginThe plugin allows adding a list of publications generated from bibtex files to a page.Enabling the pluginTo enable the plugin add this to your project file:[packages]
lektor-bibtex-support = 0.1ConfiguringCreate a file configs/bibtex-support.ini with a section called Bibtex. Define a variable files that
is a white space separated list of bibtex files. Put these files into the assets directory of your project.[Bibtex]
files = A.bib B.bibOptionally you can also create a template file that should leave in the template directory to render the bibtex entries. If you skip this entry a default template will be used that sorts the entries by year.UsageYou can add the the publication anywhere in your jinja template by calling{{ list_publications(name=name, tag=tag, year=year, labels=labels, fname=fname)|safe }}The arguments are optional and can be used for filtering.By name: the name has to show up in the author list to be includedby year: only publications from this yearlabels: white space separated list of bibtex labels (the name of each entry in the bibtex file)fname: white space separated list files to search (by default all files will be searched)JavascriptFor the default template, you can also add the following javascript to show some entries if you have a long list (relies on jquery):$(document).ready(function()
	   {
	      $(".BIBTeX").hide();
	      $(".BIBTeXtoggle").click( function () {
		  $(this).parent().children(".BIBTeX").toggle(300);
		  return false;
		});
	      $(".BIBYear").hide();
	      $(".BIBYear:first").show();
	      $(".BIBYearheader").click( function () {
		  $(this).parent().children(".BIBYear").toggle(300);
		  return false;
		});
	      $(".bibshowall").click( function () {
		  $(".BIBYear").show();
		});
	      $(".bibhideall").click( function () {
		  $(".BIBYear").hide();
		  $(".BIBYear:first").show();
		});
           });
Package: lektor-broken-links
Broken LinksFind all the broken links!Broken Links helps you detect broken links in yourLektorsite. It will warn you about broken internal and external HTTP links.GoalsFast - Less than 1 second to check sites with hundreds of pages.Simple - Install on your site and it quietly runs on every build.Getting StartedBroken Links depends on the following packages...mistune >= 0.7.0, <2click >= 7.0furl >= 2.1.0...which can be easily installed with...$ pip install mistune click furlOnce dependencies are installed, you can add Broken Links to your Lektor project with...$ lektor plugins add lektor-broken-linksAlternatively Broken Links can be installed manually by copying the plugin folder intopackages/.Once Broken Links is installed, runlektor buildorlektor server. Any broken internal links will be printed in the build output, along with the page they were found on.broken-links-tests$ lektor build
Started build
Started link check
Found 2 broken links in '/':
    /none
    ./none
Found 1 broken link in '/nested':
    ../none
Finished link check in 0.02 sec
Finished build in 0.03 sec
Started prune
Finished prune in 0.00 secExample output from buildingthe test site.ContributingThank you for your interest in this project! If you find a bug or have an idea for an awesome new feature please open an issue.
Pull Requests which help close issues are welcome!
Package: lektor-chameleon
lektor-chameleon is a plugin for theLektorstatic site generator
that makes is possible to write the templates
using theChameleontemplate engine.To use the plugin, add it to your project:lektor plugin add lektor-chameleonSince the plugin modifies the default environment,
it requires that it will be explicitly enabled.
To enable the plugin, create the fileconfigs/chameleon.iniand put the following lines into it:[chameleon]
enabled = yesIf you don’t want to use the “.html” extension for your template files,
you can set a different one in the configuration:[chameleon]
enabled = yes
file_ext = .ptUsage examples:<htmllang="${this.alt}"><h1tal:content="this.title">Page title</h1><spantal:replace="bag('translate', this.alt, 'message')">message</span>Many Lektor and Jinja filters are available using the>>operator:<ahref="${'/' >> url}">Home page</a><linkrel="stylesheet"href="${'/static/custom.css' >> asseturl}"/>Filters also accept parameters:<ahref="${'.' >> url(alt=this.alt)}">link text</a>But filter parameters must be given as keyword parameters:<!-- incorrect --><divtal:replace="this.body >> indent(4)">Page body</div><!-- correct --><divtal:replace="this.body >> indent(width=4)">Page body</div>
Package: lektor-citation
lektor-citationAn APA-styled citation plugin for the lektor static content management system (https://getlektor.com).PreparationsInstall the plugin bylektor plugin add lektor-citationor by copying this repository into thepackages-folder of your lektor-project.Create ancitation.iniin itsconfigs-folder:[Bibtex]
file = Literature.bib

[default]
priority = url
link = /for-example/link-to-your/biblioprahyAnd put aLiterature.bibBibTex-file into the project'sassets-folder respectively.Jinja_envBibliographyTo get a formated output of your whole BibTex library you can eitherUse method citation_short_output in the template of your literature page. It creates an unordered list of entries.<ul id="literatur">
  {% for entry in citation_entries() %}
  {{ citation_short_output(entry)|decode|safe }}
  {% endfor %}

</ul>Use method citation_full_output instead. This creates a more complete html-output for every entry.{% for entry in citation_entries() %}
  {{ citation_full_output(entry)|decode|safe }}
  {% endfor %}produces<h2>{title}</h2><h3>{authors} ({pubYear})</h3>
<p>{note}</p>
<dl class="literature">
<dt class="edition"></dt>
<dd>{edition}</dd>
<dt class="editors"></dt>
<dd>{editors}</dd>
<dt class="pages"></dt>
<dd>{pages}</dd>
<dt class="issbn"></dt>
<dd>{issbn}</dd>
<dt class="publisher"></dt>
<dd>{publisher}</dd>
</dl>You may also use the citation_entry method in combination withpybtex*sEntry-class. For example:<ul>
  {% for entry in citation_entries() %}
<li>{{ citation_entry(entry).fields['title'] |decode }}</li>
  {% endfor %}
  </ul>This creates an unordered list of all the titles of your bibtex file.
Of course you can also use citation_entry without a loop and put any id of your bibtex entries into it as parameter.Alternatively to the pybtex methods you can use the followingjinja_env globals:citation_authors_short(entry)
citation_authors_full(entry)
citation_editors_short(entry)
citation_editors_full(entry)
citation_pubYear(entry)
citation_edition(entry)
citation_publisher(entry)
citation_title(entry)
citation_url(entry)
citation_issbn(entry)
citation_pages(entry)
citation_note(entry)In-text CitesTo cite a certain entry in your texts you can use thejinja_env globals:citation_full_cite(id, link="")
citation_full_citeNP(id, link="")Both methods create a complete hyperlink inside your text for the entry withid. You may give it any url to thelinkparameter to e.g. link it to your bibliography page. The NP in the second stands forNo Parantheses. So you'll receive e.g.AuthorI & AuthorII (2019)or(AuthorI & AuthorII, 2019)link parameterWhich url is used for your citation's link depends on what you set in thecitation.inifile.If you setpriorityin thedefaultsection tourlthe link is set to the value of theurlfield of the entry.If there's no value in it the default-link you may set withlinkin the same section is used.If you set thelinkparameter of the function it overwrites the former options.Thanks to thelektor-jinja-contentplugin which is a dependency of this plugin you might also use the globals inside your markdown or html contents, too.
Package: lektor-creative-commons
Lektor Creative CommonsLektor plugin to add Creative Commons license to your pagesUsageOn your templates use:<div class="license">{{ render_cc_license(type, size, template, caller) }}</div>typeis astringwith the license type (e.g.:'by','by-sa','by-nc-sa').sizeis an optional parameter with the size'normal'or'compact'. It defaults to'normal'.templateis an optional parameter with the template'full','image-only'or'text-only'. It defaults to'full'.localeis an optional parameter that overrides the locale at function calling time.calleris an optional parameter that you can pass an callable to mount your own template. This argument is usually omitted. See the example of how to use it with theJinja call feature.ExamplesSimply rendering the license of your choice:<div class="license">{{ render_cc_license('by-sa') }}</div>Using Jinja2callblock to inject your own template:{% call(license, license_url, icon_path) render_cc_license('by-sa', size='normal') %}
  <a class="nav-item" rel="license" target="_blank" href="{{ license_url }}">
    <img alt="{{ license }}" style="border-width:0" src="{{ icon_path }}" />
  </a>
{% endcall %}There are more variables, you can check which with{% call() render_cc_license('by-sa', size='normal') %}
  {{ kwargs }}
{% endcall %}Notice that using the call block it injects its content ascallerparameter to therender_cc_licensefunction that skips the need of choosing a template and renders your own.Internationalization supportThis plugin has support to internationalization, and changes it language based on.lektorprojectfile.
The Current supported locales are:enpt_BRdeAny other locale will default toen(English).
Package: lektor-cssbuild
lektor-cssbuild is a plugin for theLektorstatic site generator that integrates CSS manipulation tools
into the build process. The tools that it uses are:libsass-pythonis run
before the Lektor build to generate a CSS file.uncssis run
after the Lektor build to remove unused CSS.rcssminis run
as the last step to minify the CSS.To use the plugin, add it to your project:lektor plugin add lektor-cssbuildCreate apackage.jsonfile (the name and version aren’t significant
for the plugin):{
  "name": "my-project-cssbuild",
  "version": "1.0.0",
  "private": true
}Install uncss:npm install --save-dev uncssCreate a configuration fileconfigs/cssbuild.iniand set the tool paths
(assuming that your source sass file isstyle/sass/main.scss):[sass]
source = src:style/sass/
output = src:assets/static/

[uncss]
output = dst:static/main.nested.css

[cssmin]
source = dst:static/main.nested.css
output = dst:static/main.cssWhen writing a path, thesrcprefix refers to a path
in the source folders and thedstprefix refers
to the build folders.If any tool section is missing, that tool will be skipped.To enable the plugin during Lektor build, thecssbuildflag
has to be included (same for theservercommand):lektor build -f cssbuildUsing the above configuration, the build process will run as follows:Thestyle/sass/main.scssfile is read
and the fileassets/static/main.cssis generated.Lektor generates the site artifacts.Based on the generated HTML pages, the unused CSS rules are removed
and the result is written into thestatic/main.nested.cssfilein the build directory.The generatedstatic/main.nested.cssfile is minified
and the result is written into themain.cssfile
in the same directory.During uncss, theignoreoption can be used to make sure
to keep some selectors:[uncss]
output = src:style/css/main.css
ignore = "/\.selector1.*/"0.3.1 (2019-08-10)Fix npm install bug.0.3 (2019-08-09)Replace node-sass with libsass-python.Replace node-cssmin with python rcssmin.0.2 (2019-08-06)Add ignore option to uncss stage.0.1 (2019-08-06)Initial release on PyPI.
Package: lektor-datetime-helpers
IntroductionThis is a plugin for Lektor which provides some helpers for dealing with
dates and times.Currently this provides adateordatetimemodel field type which
can contain either adateor adatetime.Also the following jinja filters are provided:isoformat(dt)Returns an iso formatted version the datetime, with timezone information.
Ifdtis naive, it is localized to the site’s default timezone.localize_datetime(dt)Ifdtis naive, it is localized to the site’s default timezone.ChangelogRelease 1.0.1 (2021-12-22)PackagingSetRequires-Python:>=3.6in METADATADeletedsetup.pyTestingAdd work-around for lektor bug#974Test under python 3.10, and lektor<3.3Release 1.0.0 (2021-08-16 — yanked)This release drops support for Python 2 and Python 3.5.This release has beenyankedfrom PyPI due to missingRequires-Pythonin METADATA allowing (broken) installation under
py27.  Use release 1.0.1 instead.DependenciesThis package no longer has any external dependencies.  Since python
3.6,datetime.astimezone()has the ability to interpret a naïvedatetimew.r.t. the system local timezone, so the use oftzlocalis no longer necessary.Release 0.3.3.post1 (2021-08-16)Fix useless comparison in test.Fix formatting inCHANGES.rst.Release 0.3.3 (2021-08-15)BugsPintzlocal<3.  (Tzlocal >= 3drops support for python 2.)Release 0.3.2 (2020-11-19)BugsEnsure thatcomparable_dateandcomparable_datetimeobjects
are hashable.  This fixes issues using these classes withpytzunder py3k.TestingTest under py3.9Release 0.3.1 (2020-05-21)This release freshens the packaging.
There are no substantive changes to the code in this release.PackagingUpdate packaging toPEP 517.Update LICENSE to latest 3-clause BSD text.DocstringsFix docstring syntax.  No substantive changes.TestsTest under python 3.7 and 3.8.Usetwine checkrather thansetup.py checkto test
description syntax.Release 0.3 (2018-01-18)Fix things so that date and datetime types returned by thedateordatetimeLektor type are comparable againstNone.  (Nonecompares less than all other dates and datetimes.)Release 0.2 (2017-08-04)New featuresMake lists ofdateordatetimetypes sortableThedateordatetimecustom Lektor type now returns subclasses ofdatetime.dateordatetime.datetimewhich can be compared against one another.  Normally, attempts to compare adateagainst adatetimeresults in aTypeErrorbeing raised.  This made it difficult to sort ondateordatetimevalues.Nowdates sort before anydatetimes with the same date.  Naïvedatetimes sort before timezone-awaredatetimes with the same date.Release 0.1 (2017-04-19)Initial release.
Package: lektor-debug
Lektor DebugExample ran on theLektor Example Project's/typepage:This Plugin provides a{% debug %}template tag that will render helpful debugging information in a template. To use, simply add this tag in a template, and run lektor server in development mode withLEKTOR_DEV=1 lektor server.This plugin replaces Lektor's built-in, optional{% debug %}tag from Jinja2's Debug Extension. That tag is completely superceded by this plugins, so we just replace it.This plugins tag can also be left in with no ill-effects. Unless the environment variableLEKTOR_DEV=1is set,{% debug %}will be a noop and return an empty string, unlike Lektor's current behavior which, since Jinja2's Debug Extension would not be added, would raise aTemplateSyntaxError.{% debug %}contentsThis tag automatically renders as a collapsed<detail>html element, so it is minimally invasive unless you need it. When expanded, it will show a Python-ish dict with keys for:All fields available onthisThe completedir(this), which shows it's native attributes and methods (different from the above)All flowblocks and their fieldsAll current template context, exactly like Jinja2's Debug ExtensionAll available template filters, exactly like Jinja2's Debug ExtensionAll available template tests, exactly like Jinja2's Debug ExtensionThe top-level keys are meant to quickly tell you what that piece of data is, but do not necessarily correspond to an available key in a real Python dict. For example,this.fieldsis not a key in any Lektor Python dict, but it's hopefully clear what this represents.Flowblocks are listed asthis.<flowblock name>.blocks, which is how you would access them in a template. Each flow field will present a list of dicts of all blocks' fields and their values.This debug info is presented as a code block, ran through Lektor's markdown processor. Since that is the case, if you haveLektor Markdown Highlighterinstalled and configured, this will also use the syntax highlighting for Python.Additional Template ContextThis plugin also adds the following template variables globally:{{ dir }}Python'sdirbuiltin{{ str }}Python'sstrbuiltin{{ type }}Python'stypebuiltin
Package: lektor-diazotheme
Introduction“What’s Diazo?”, I hear you say.  Fromdiazo.org:Diazo allows you to apply a theme contained in a static HTML web
page to a dynamic website created using any server-side
technology. With Diazo, you can take an HTML wireframe created by
a web designer and turn it into a theme for your favourite CMS,
redesign the user interface of a legacy web application without
even having access to the original source code, or build a unified
user experience across multiple disparate systems, all in a matter
of hours, not weeks.When using Diazo, you will work with syntax and concepts familiar
from working with HTML and CSS. And by allowing you seamlessly
integrate XSLT into your rule files, Diazo makes common cases
simple and complex requirements possible.A package to postprocess html artifacts with diazoThis is a plugin for theLektor content management systemthat
allows to postprocess any html file produced with aDiazo theme,
allowing to transform the html as pleased and to share the theme
between many projects.author:Alberto Berticontact:alberto@metapensiero.itlicense:GNU Lesser General Public License version 3 or laterChanges0.3 (2016-10-09)Fix plugin description.0.2 (2016-10-08)Fix packaging.0.1 (2016-10-08)Initial effort.
Package: lektor-disqus-comments
lektor-disqus-commentsThis plugin adds support for Disqus comments to Lektor.  Once the plugin is
enabled arender_disqus_commentsfunction which can render a disqus comment
box.Enabling the PluginTo enable the plugin add this to your project file:$lektorpluginsaddlektor-disqus-commentsConfiguring the PluginThe plugin has a config file that is needed to inform it about your
website.  Just create a file nameddisqus-comments.iniinto yourconfigs/folder and configure theshortnamekey with the name of
your disqus community:shortname=YOUR_SHORTNAMEIn TemplatesNow you can add a discussion box to any of your templates by just using
therender_disqus_commentsfunction.  Just calling it is enough to
get the comment box:<divclass="comments">{{ render_disqus_comments() }}</div>Optionally the function accepts a few arguemnts:identifierandurlcan be used to forcefully override the automatically
detected defaults.titlecan be used to set a title for the discussion that overrides
the title that disqus takes from the page's title tag otherwise.category_idsets the category id.  Look at the disqus documentation
for more information.
Package: lektor-embed-x
lektor-embed-xEnables simple embedding of web-contents from popular sites in
MarkDown(*.md) pages generated by Lektor CMS.Current Status:Alpha.Minimally works for limited number of content providers. Active
development is ongoing.SetupSimple way$ cd path/to/lektor/project_folder
$ lektor plugins add lektor-embed-x
Package lektor-embed-x (0.1.2) was added to the projectGeek way$ cd path/to/lektor/project_folder
$ cd ./packages
$ git clone https://github.com/kmonsoor/lektor-embed-x.gitThen add this line to your_lektor_project..lektorproject file’s[packages]section.lektor-embed-x = 0.1.2Then, remember to flash the plugin-cache ofLektor. Just in case.$ lektor plugins flush-cacheUsageYou need nothing explicit to enable the embedding inMarkDownformatted text on Lektor.If the content link is supported byembedX project, the content
link will automatically expanded to become embedded staff.For example, check out this page. // TODOCopyright:(c) 2016 Khaled Monsoork@kmonsoor.comDistributed underThe MIT License.Click for license details.