notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
Port details
py-laces Django components that know how to render themselves
0.1.1 www on this many watch lists=2 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout 0.1.1Version of this port present on the latest quarterly branch.
Maintainer: sunpoet@FreeBSD.org search for ports maintained by this maintainer
Port Added: 2024-03-09 14:12:39
Last Update: 2024-03-09 14:05:16
Commit Hash: 4f4fc4e
People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
Also Listed In: python
License: BSD3CLAUSE
WWW:
https://github.com/tbrlpld/laces
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 {% component %} 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.
Homepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
There is no configure plist information for this port.
Dependency lines:
  • ${PYTHON_PKGNAMEPREFIX}laces>0:www/py-laces@${PY_FLAVOR}
To install the port:
cd /usr/ports/www/py-laces/ && make install clean
To add the package, run one of these commands:
  • pkg install www/py-laces
  • pkg install py39-laces
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py39-laces listed in the above command, you can pick from the names under the Packages section.
PKGNAME: py39-laces
Package flavors (<flavor>: <package>)
  • py39: py39-laces
distinfo:
TIMESTAMP = 1709390340 SHA256 (laces-0.1.1.tar.gz) = e45159c46f6adca33010d34e9af869e57201b70675c6dc088e919b16c89456a4 SIZE (laces-0.1.1.tar.gz) = 26889

Packages (timestamps in pop-ups are UTC):
py311-laces
ABIaarch64amd64armv6armv7i386powerpcpowerpc64powerpc64le
FreeBSD:13:latest0.1.10.1.1-0.1.10.1.1---
FreeBSD:13:quarterly0.1.10.1.1-0.1.10.1.1---
FreeBSD:14:latest0.1.10.1.1-0.1.10.1.1---
FreeBSD:14:quarterly0.1.10.1.1-0.1.10.1.1---
FreeBSD:15:latest0.1.10.1.1n/a0.1.1n/a---
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. py39-django42>=3.2 : www/py-django42@py39
  2. py39-flit-core>=3.2<4 : devel/py-flit-core@py39
  3. python3.9 : lang/python39
  4. py39-build>=0 : devel/py-build@py39
  5. py39-installer>=0 : devel/py-installer@py39
Test dependencies:
  1. python3.9 : lang/python39
Runtime dependencies:
  1. py39-django42>=3.2 : www/py-django42@py39
  2. python3.9 : lang/python39
This port is required by:
for Run
  1. www/py-wagtail

Configuration Options:
No options to configure
Options name:
www_py-laces
USES:
python
FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (2 items)
Collapse this list.
  1. https://files.pythonhosted.org/packages/source/l/laces/
  2. https://pypi.org/packages/source/l/laces/
Collapse this list.

Number of commits found: 1

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
0.1.1
09 Mar 2024 14:05:16
commit hash: 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924commit hash: 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924commit hash: 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924commit hash: 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924 files touched by this commit
Po-Chuan Hsieh (sunpoet) search for other commits by this committer
www/py-laces: Add py-laces 0.1.1

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 {%
component %} 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.

Number of commits found: 1