BSD Ports

www/py-laces 0.1.2 DragonFly

Django components that know how to render themselves

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
BSD3CLAUSE
Categories
python, www
Package size
31.3 KiB, 186.3 KiB installed

Description

Laces components provide a simple way to combine data (in the form of Python objects) with the Django templates that are meant to render that data. The components can then be simply rendered in any other template using the {%25 component %25} template tag. That parent template does not need to know anything about the component's template or data. No need to receive, filter, restructure or pass any data to the component's template. Just let the component render itself.

Template and data are tied together in the component, and they can be passed around together. This becomes especially useful when components are nested -- it allows us to avoid building the same nested structure twice (once in the data and again in the templates).

Working with objects that know how to render themselves as HTML elements is a common pattern found in complex Django applications, such as the Wagtail admin interface. The Wagtail admin is also where the APIs provided in this package have previously been discovered, developed and solidified. The purpose of this package is to make these tools available to other Django projects outside the Wagtail ecosystem.

In the other systems

The newest version among them is 0.1.2, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
DragonFlywww/py-laces0.1.2 newestnone known-[email protected]-
FreeBSDwww/py-laces0.1.2_1 newestnone known-[email protected]-
NetBSDwww/py-laces0.1.0nb1none known-[email protected]-
HardenedBSDwww/py-laces0.1.2_1 newestno data-[email protected]-
GhostBSDwww/py-laces0.1.2_1 newestno data-[email protected]-

Compare across BSDs

Install

Binary package:

pkg install py311-laces

From DPorts:

cd /usr/dports/www/py-laces && make install clean

Dependency graph

Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.

Dependencies

Run dependencies 2
Required by 1