Saravanan666/pypi-org huggingface dataset:
Package: wagtailperson
Wagtail PersonOn a CMS, we regularly need to represent an author, a speaker, a
person. To avoid repetition and duplication of datas about this, this
app add a person model to Wagtail, with admin UI. Do not hesitate to
use it on your blog or lectures appilaciton.This model is accompanied by a Person page model and a Persons index
page model. Each Person page is linked to a Person model to see it on
your website.This app also provide a basic CSS and templates, feel free to
customize it.ImportantSince version 0.9.8, the Person Page model has been split in 2 models:A Person modelA Person page model, with a many2one to a Person modelInstallSimply install it from pypi.org:pip install wagtailpersonAdd this app to django installed app in your settings.py:INSTALLED_APPS = [
    # …
    'wagtailperson',
    # …
    'wagtail.contrib.modeladmin',
    # …
    ]Then, finally, apply migration scripts:./manage.py migrate wagtailpersonUseThis application add a new entry to the administration menu, called
"Persons". From this menu, you can add a new author or
person.If you want to link one of your wagtail page models, or django models,
to a person: Simply add a many2one field linked towagtailperson.models.Person.This application also provide 2 pages models:A Person page: Show puplicly someone, can be used mostly
everywhere in the pages treeA Persons index page: A root page for Persons pages, it list each
of Persons pages it had as children pages and can only have Person
pages as childrenThe person index page can be useful to group persons, globally or per
group.A person got multiple fields:PictureNameTagsIntroductionAbstractThis application also provide a person block for StreamField, atwagtailperson.blocks.PersonBlock. Feel free to use it on your models
StreamField.DevelopmentThe source code repository provide a full Django project, so you can
easily work with wagtailperson for testing you modifications.Simply use these two steps in the source code working directory:./manage.py migrate
./manage.py runserverLicenceLGPLv3AuthorSébastien Gendre <seb@k-7.ch>
Package: wagtail-personalisation
Wagtail PersonalisationWagtail Personalisation is a fully-featured personalisation module forWagtail CMS. It enables editors to create customised pages
- or parts of pages - based on segments whose rules are configured directly
in the admin interface.InstructionsWagtail Personalisation requires Wagtail 2.0 or 2.1 and Django 1.11 or 2.0.To install the package with pip:pip install wagtail-personalisationNext, include thewagtail_personalisation,wagtail.contrib.modeladminandwagtailfontawesomeapps in your project’sINSTALLED_APPS:INSTALLED_APPS=[# ...'wagtail.contrib.modeladmin','wagtail_personalisation','wagtailfontawesome',# ...]Make sure thatdjango.contrib.sessions.middleware.SessionMiddlewarehas
been added in first, this is a prerequisite for this project.MIDDLEWARE=['django.contrib.sessions.middleware.SessionMiddleware',# ...]DocumentationYou can find more information about installing, extending and using this module
onRead the Docs.SandboxTo experiment with the package you can use the sandbox provided in
this repository. To install this you will need to create and activate a
virtualenv and then runmake sandbox. This will start a fresh Wagtail
install, with the personalisation module enabled, onhttp://localhost:8000andhttp://localhost:8000/cms/. The superuser credentials aresuperuser@example.comwith the passwordtesting.
Package: wagtail-personalisation-molo
Wagtail Personalisation is a fully-featured personalisation module forWagtail CMS. It enables editors to create customised pages
- or parts of pages - based on segments whose rules are configured directly
in the admin interface.InstructionsWagtail Personalisation requires Wagtail 1.9 or 1.10 and Django 1.9, 1.10 or 1.11.To install the package with pip:pip install wagtail-personalisationNext, include thewagtail_personalisation,wagtail.contrib.modeladminandwagtailfontawesomeapps in your project’sINSTALLED_APPS:INSTALLED_APPS=[# ...'wagtail.contrib.modeladmin','wagtail_personalisation','wagtailfontawesome',# ...]Make sure thatdjango.contrib.sessions.middleware.SessionMiddlewarehas
been added in first, this is a prerequisite for this project.MIDDLEWARE=['django.contrib.sessions.middleware.SessionMiddleware',# ...]SandboxTo experiment with the package you can use the sandbox provided in
this repository. To install this you will need to create and activate a
virtualenv and then runmake sandbox. This will start a fresh Wagtail
install, with the personalisation module enabled, onhttp://localhost:8000andhttp://localhost:8000/cms/. The superuser credentials aresuperuser@example.comwith the passwordtesting.
Package: wagtail-pg-search-backend
A PostgreSQL full text search backend for Wagtail CMS.InstallationPostgreSQL full text search in Wagtail requires PostgreSQL >= 9.2
(noticable speed improvements are in place for PostgreSQL >= 9.5),
Django >= 1.10 and Wagtail >= 1.8.First, install the module using:pip install wagtail-pg-search-backendThen you’ll need to do a little bit of configuration.Add the following to the project settings:INSTALLED_APPS = [
    ...
    'wagtail_pgsearchbackend'
    ...
]

WAGTAILSEARCH_BACKENDS = {
    'default': {
        'BACKEND': 'wagtail_pgsearchbackend.backend',
        'SEARCH_CONFIG': 'english'
    }
}Then run migrations to add the required database table:./manage.py migrate wagtail_pgsearchbackendConfigurationTheSEARCH_CONFIGkey takes a text search configuration name.
This controls the stemming, stopwords etc. used when searching and
indexing the database. To get a list of the available config names
use this query:SELECT cfgname FROM pg_catalog.pg_ts_configUsageThis backend implements the required methods to be compatible
with most features mentioned in the theWagtail search docs.Known limitationsSearchField.partial_matchbehaviour is not implemented.Due to a PostgreSQL limitation,SearchField.boostis only partially
respected. It is changed so that there can only be 4 different boosts.
If you define 4 or less different boosts,
everything will be perfectly accurate.
However, your search will be a little less accurate if you define more than
4 different boosts. That being said, it will work and be roughly the same.SearchField.es_extrais not handled because it is specific
to ElasticSearch.UsingSearchQuerySet.searchwhile limiting to specific field(s) is only
supported for database fields, not methods.PerformanceThe PostgreSQL search backend has been tried and tested on a few small
to medium sized website and its performance compares favorably to that
of ElasticSearch.Some noticeable speed improvements are in place when using PostgreSQL >= 9.5.Features to addThese features would awesome to have once this project is merged with Wagtail:Per-object boostingFacetingAutocomplete (maybe it should replace partial search?)Spelling suggestionsDevelopmentInstall the package and dev requirements:pip install -e . -r requirements-dev.txtCreating migrationsFirst create a database:createdb -Upostgres wagtail_pgsearchbackendThen call makemigrations using the test settings:django-admin makemigrations --settings=tests.settingsTestingTo run the unittests for the current environment’s Python version
and Wagtail run:make unittestsTo check the code for style errors run:make flaketestTo combine these tasks run:makeTo run the unittest against all supported versions of Python and
Wagtail run:toxThe tox run will also create a coverage report combining the results
of all runs. This report is located inhtmlcov/index.html.To run individual tests by name use theruntests.pyscript and give
the dotted path the the test module(s), class(es) or method(s) that you
want to test e.g.:./runtests.py tests.test_module.TestClass.test_method
Package: wagtail-photo-gallery
wagtail-image-galleryWith this extention you are just a few steps away from a simple photo gallery for your wagtail page.The gallery is configurable with the wagtail admin panel and is suited for large amounts of photos.The key idea of this project is to store and manage photos independently of the usual wagtail images.
Instead all photos are assigned to albums and can be managed by a drag-and-drop sorting widget which also supports item selection for mass-dragging and deletion.A collection may be assigned to each album, which is then used to include all albums belonging to a collection in aGalleryBlock.
TheGalleryBlockcan be used in wagtailsStreamFieldto embed albums into your page.Installationpipinstallwagtail-photo-galleryIf you don't have pillow installed, install it viapipinstallpillowFor the fastest possible image uploading (Faster resizing) usepillow-simdinstead.SettingsINSTALLED_APPS=['wagtail_photo_gallery','wagtail.contrib.modeladmin','wagtail.contrib.routable_page','generic_chooser',]Update your database structure using (remember to create abackup first):./manage.pymigrateExampleOnce you've installed this addon and configured the settings as above,
all you need to do is to inherit fromImageGalleryMixinand to addGalleryBlockto yourStreamField.fromwagtail.core.modelsimportPagefromwagtail.core.fieldsimportStreamFieldfromwagtail.admin.edit_handlersimportStreamFieldPanelfromwagtail_photo_gallery.modelsimportGalleryBlock,ImageGalleryMixinclassYourWagtailPage(ImageGalleryMixin,Page):content=StreamField([#...("gallery",GalleryBlock()),#...],blank=True)# content panel for the CMS (same as always)content_panels=Page.content_panels+[StreamFieldPanel("content"),]If you want to use the predefinedCSS-flexboxlayout for the albums,
you need to include the following css code in your gallery page (YourWagtailPage){% include 'wagtail_photo_gallery/extra_css.html' %}CreditsThis project was initially planned as a port ofdjango-photo-galleryas the name of this addon suggests.
Never the less, almost the entrie code is changed completely now due to incompability with wagtail and the incorporation ofdjango-modelcluster.Contributions to this project are welcome!
Package: wagtail-photography
Wagtail PhotographyBased onwagtail-photo-galleryBe warned, I'm mostly using this project as a learning experience for developing and distributing apps. I'm new at it so
things are likely to be broken or break in the future. I use it in production on my own website but would advise against
doing the same if reliability is important to you. I do hope to add tests and generally polish things up in the not so
distant future.Wagtail-photography is a Wagtail app to display photographs.Detailed documentation is in the "docs" directory.Quick startInstall librarypip install wagtail-photographyAdd "wagtail_photography" and wagtail-generic-chooser to your INSTALLED_APPS setting like this:INSTALLED_APPS=[..."wagtail.contrib.modeladmin","wagtail.contrib.routable_page","wagtail_photography","generic_chooser",]Setup Wagtail to dynamically serve image urls:fromwagtail.images.views.serveimportServeViewurlpatterns=[...re_path(r'^images/([^/]*)/(\d*)/([^/]*)/[^/]*$',ServeView.as_view(),name='wagtailimages_serve'),...# Ensure that the wagtailimages_serve line appears above the default Wagtail page serving routere_path(r'',include(wagtail_urls)),]Create a Page model that inherits fromPhotoGalleryMixin:classPhotoGallery(PhotoGalleryMixin,Page):content=StreamField([("gallery",GalleryBlock()),],blank=True,use_json_field=True)content_panels=Page.content_panels+[FieldPanel("content"),]Runpython manage.py migrateto create the wagtail_photography models.Start the development server and visithttp://127.0.0.1:8000/admin/to create an album.
Package: wagtail-photo-voter
Wagtail-photo-voterA Wagtail module for creating Photo competitions with voting.How to installInstall using pip:pip install wagtail-photo-voterAlso needs ExifTool fromhttps://exiftool.org/install.htmlinstalledSettingsIn your settings file, addwagtailphotovoterandwagtail.contrib.routable_pagetoINSTALLED_APPS:INSTALLED_APPS=[# ...'wagtail.contrib.routable_page','wagtailphotovoter',# ...]How to useThe basicsTo add a competition create a new page of typCompetitionenter title and rules (shown on submission page). You can enter dates for when submissions are allowed (if empty always allowed) and voting dates (empty, always allowed).Templates are extendingbase.htmlwhich should have blocks forcontentextra_cssextra_js.And Bootstrap, and jQuery loaded (for example viadjango-bootstrap4)You can modify the point-system with commasepareted values andallow same points.
0 points can always be given to any entry.Voting is allowed for users in the group with namecompetition-id-slugand available at:competition-page/voteresults available atcompetition-page/result.
Package: wagtail-picture-tag
Wagtail Picture Tag adds a picture template tag.
This is not supposed to be a solution for all situations but to be
a shortcut for most.It accepts 3 main types of filters: formats, resizing methods and sizes.FormatsBy default it will try and create JPEG, PNG, WEBP and AVIF (if available).You may useformat-jpeg,format-png,format-webp,format-gifandformat-avifThere are also two format shortcuts:photo - will create JPEG, WEBP and AVIFtransparent - will create WEBP, PNG and AVIFResizingResizing methods are the same as Wagtails with the exception that you
can provide multiple filtersSizesSizes are automatically generated to match resizing filters provided but
can be specified for more responsive sizes.size-250pxwill createsizes=”250px”size-max100-300vw size-250pxwill createsizes=”(max-width: 300px) 100vw, 250px”LazyIt also takes the argumentlazythat simply addsloading=”lazy”to the HTML tag.AVIFCurrently Willow (the image library used by Wagtail) does not support AVIF
but support can be patched in by installingwillowavifpackage.Quick startInstall the package:pip install wagtail-picture-tagAdd “wagtail-picture-tag” to your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'wagtail_picture_tag',
]Include the tag in your template:{% load picture_tags %}Use the tag:{% picture image photo fill-640x480 fill-320x240 %}AVIF supportAll that is needed is to install thewillowavifpackage, it is
then automatically imported and used.TestingTesting is done with pytest. Install and test can be done with:pip install -r requirements.txt -r requirements.dev.txt
pytest
Package: wagtail-placeholder-images
wagtial placeholder imagesThis is a package for using placeholder images when developing which can be useful if you're storing them on a server and don't want to download them or link directly to the server when working locally.InstallationFirst download the package:pipinstallwagtail-placeholder-imagesThen there's two options. If you're using your own custom image model you can usePlaceholderRenditionMixinlike so:fromwagtail.images.modelsimportAbstractImagefromwagtail_placeholder_images.mixinsimportPlaceholderRenditionMixinclassCustomImage(PlaceholderRenditionMixin,AbstractImage):admin_form_fields=Image.admin_form_fields+(# Then add the field names here to make them appear in the form:# 'caption',)If you're using the standard Wagtail Image model you can monkey patch it:fromwagtail.images.modelsimportAbstractImagefromwagtail_placeholder_images.mixinsimportPlaceholderRenditionMixinAbstractImage.get_placeholder_rendition=PlaceholderRenditionMixin.get_placeholder_renditionAbstractImage.get_rendition=PlaceholderRenditionMixin.get_renditionThen you have to setWAGTAIL_PLACEHOLDERIMAGES_DUMMYtoTrueand use your desired placeholder source by settingWAGTAIL_PLACEHOLDERIMAGES_SOURCE. This should be done in your development settings file, so this doesn't get enabled on your servers. E.g.# settings_dev.pyWAGTAIL_PLACEHOLDERIMAGES_DUMMY=TrueWAGTAIL_PLACEHOLDERIMAGES_SOURCE="//placedog.net/{width}/{height}/"That should be it!
Package: wagtailplus
Wagtail PlusWagtail Plus is a collection of independent modular add-ons forWagtail CMS, featuring:wagtailplus.wagtaillinks: Link storage and management for both email addresses and external URLs. Fully integrated with Wagtail’s rich-text editor.wagtailplus.wagtailrelations: Multi-faceted content relationship manager built around Wagtail’s implementation ofdjango-taggit. Includes views and templates for a hierarchical site map.wagtailplus.wagtailrollbacks: Version control manager that includes the ability to “rollback” or revert to a previous version of a page.DocumentationThe latest documentation is available atwagtailplus.readthedocs.org.
Package: wagtail-podcast
IntroductionThis is a very basic podcast app that integrates with Wagtail. It allows a person to upload a mp3 and then play it on the website. It generates a rss/xml feed that you can submit to Itunes, Google and/or Blubrry.This app is simple, and not feature rich. It does the basics and thats it. I will probably add more features and options to it as time permits, but only if requests are made.It is also not production ready as there areno tests currently writtenfor it. I did put this up on a site and they have been using it extensively and haven’t had any reported issues. That said,apps without tests should always be treated sceptically.I hope to write tests in a month or so when I get a bit of free time. I also hope to add a bunch of features in the near future.Please report any errors you encounter. I will try resolve them quickly and then add tests for them. Please visit:wagtail_podcast.  Documentation is at readthedocs.io:wagtail_podcast documentationInstallationTo install runpip install wagtail_podcastIt should automatically install mutagen; however, if it doesn’t then you will need to install it manually with:pip install mutagenRemember to addwagtail_podcastto your installed apps in settings.py i.e.INSTALLED_APPS=[...'wagtail_podcast',]Requirements:python3mutagenwagtaildjangodjango-social-shareI’m not quite sure how far back this app works; however, it should work going back quite far. It’s currently tested on Python3 with Wagtail >2 and Django >2 on openSUSE. It should work on all platforms and shouldn’t break anytime soon. Let me know if you have a combo that doesn’t work and I’ll see what I can do to support it.CaveatsI haven’t implemented categories at all so that is rather broken. You need to go into wagtail_podcast/templates/wagtail_podcast/feed.xml
and change it to something more appropriate<itunes:categorytext="{{ page.category }}"><itunes:categorytext="Christianity"/></itunes:category>There is currently no handling of ogg files though I plan on doing auto conversion to them at some point. All major browsers support mp3 these days.This is made only for audio podcasts though I may support video podcasts at a later stage since that doesn’t require much changing.Seasons are currently not supported. This is really high on my list, but I haven’t figured out a really great way to do it. The page hierarchy is already going to be a bit of a mess.This currently only supports one podcast per wagtail site. It should be relatively easy to make it support multiple; however, I’ll only do it if there is demand for the feature.
Package: wagtail-preference-blocks
wagtail-preference-blocksWagtail blocks for storing preferences for rendering. Please bear with us while we prepare more detailed documentation.Compatibilitywagtail-preference-blocks' major.minor version number indicates the Wagtail release it is compatible with. Currently this is Wagtail 4.1.xInstallationInstall usingpip:pipinstallwagtail-preference-blocksAddwagtail_preference_blocksto yourINSTALLED_APPSsetting:INSTALLED_APPS=[# ...'wagtail_preference_blocks'# ...]
Package: wagtailpress
WagtailpressA Blog build with Wagtail. Its name is not a reference to Wordpress,
but the name wagtail_blog is already taken.FeaturesIndex page modelArticle page modelAuthors are defined usingWagtail personTagsRSS feed for index pagesDelivred with acceptable templatesInstallSimply install it from pypi.org:pipinstallwagtailpressAdd this app and dependencies to django installed app in your
settings.py:INSTALLED_APPS=[# …'wagtail.contrib.routable_page','wagtailperson','wagtailpress',# …]Then, finally, apply migration scripts:./manage.pymigratewagtailpressUseThis application provide 2 pages models:A blog article page: A simple articleA blog index page: The index of your blog, it list its children
articles, their tags and provide a RSS feedA blog article page got multiple fields:TitlePublication dateOne or some authorsAn introAn optional header imageThe content of the articleDevelopmentThis source code repository provide a full Django project, so you can
easily work with wagtailperson for testing you modifications.Simply use these two steps in the source code working directory:./manage.pymigrate./manage.pyrunserverTestTo run test, simply run this in the root of the source code working directory:./manage.pytestLicenceLGPLv3Author(s)Sébastien Gendreseb@k-7.ch
Package: wagtail-publish-preflight
# Publish Preflight## What is this?Ever wanted to be able to save a draft in wagtail easily, but want lots of required fields for publish?
Of course you have.
This plugin creates some custom model validation that allows for drafts to be saved, but prevents publishing.It is VERY much in it’s infancy and really more of a proof of concept.## How to useinstalladd to INSTALLED_APPS(atm), include static js or css on the templates where you want the overrides to occur (is there a better way to do this?)## TODOs:messages are hidden, becuase at the moment it will create a big ol’ list of messages which could get ugly
-   would love to have a nuanced way to add errors to fields but not show errors in messages at the top
-   setting different kind of error levels would be great too
-   this would probably involve a custom message protocol, to either replace or enhance the way wagtail handles messagesadd_errorright now we check for any and all empty fields, we want to be able to define which fields to check
-   Whats a good interface for this? config file? Being able to define on each model similar toBlank=Trueseems best to me
Package: wagtail-purge
Wagtail PurgeA simple admin UI for removing individual pages from your CDN's cache. Assumes that your Wagtail site has already been configured withfrontend cache invalidation.InstructionsInstall this app withpip install wagtail-purgeAdd"wagtail_purge"to yourINSTALLED_APPSVisit 'CDN purge' in your admin settings menu
Package: wagtail-pygments
A block render syntax highlighter for Wagtail CMS.Installpip install-iwagtail-pygmentsExample UsageUse withStreamBlock:from wagtail_pygments.blocks import CodeBlock

class ContentStreamBlock(StreamBlock):
    heading = TextBlock()
    paragraph = TextBlock()
    code = CodeBlock(label='Code')Use withStreamField:from wagtail_pygments.blocks import CodeBlock

class PostPage(Page):
    body = StreamField([
        ('paragraph', RichTextBlock()),
        ('image', ImageChooserBlock()),
        ('embed', EmbedBlock()),
        ('code', CodeBlock())
    ])Example for django template:{% load static %}
<link rel="stylesheet" href="{% static 'css/monokai.css' %}">

{% for block in page.body %}
{% if block.block_type == "code" %}
    {{ block.value.code }}
    {% if block.value.caption %}
        <!-- Caption -->
        <figcaption>
          {{ block.value.caption }}
        </figcaption>
    {% endif %}
{% else %}
    {{ block.value }}
{% endif %}
{% endfor %}LanguagesConfiguringWAGTAIL_CODE_BLOCK_LANGUAGESin your Django settings:WAGTAIL_CODE_BLOCK_LANGUAGES = (
    ('cpp', 'C++'),
    ('java', 'Java'),
    ('python3', 'Python 3'),
    ('bash', 'Bash/Shell'),
    ('javascript', 'Javascript'),
    ('css', "CSS"),
    ('html', "HTML"),
    ('julia', "Julia"),
    ('nginx', "Nginx configuration file"),
    ('numpy', "NumPy"),
    ('django', "Django"),
    ('jinja', "Jinja"),
    ('docker', "Docker"),
    ('jinja', "Jinja"),
    ('yaml', "YAML"),
    ('json', "JSON"),
    ('plpgsql', "PL/pgSQL"),
    ('psql', "PostgreSQL console (psql)"),
)Can check full list inhttps://pygments.org/docs/lexers/.