About
A simple pygments lexer for LCONF. The light and simple readable data serialization format for dynamic configurations and data exchange.
For features check out the: CHANGELOG.rst
Requirements
Requires Pygments
Installation
To install from pypi using pip/pip3:
$ pip3 install python_lconf_lexer
To install from the source:
$ python3 setup.py install
to check if it installed ok and is available:
$ pygmentize -L
lconf should be one of the available lexers
Projects using python_lconf_lexer
projects which make use of: python_lconf_lexer
- PSphinxTheme
A sphinx theme which has an admonition for LCONF examples.
Online Resources
python_lconf_lexer is distributed under the terms of the BSD 3-clause license. Consult LICENSE or BSD-3-Clause.
(c) 2014, peter1000 https://github.com/peter1000 All rights reserved.
1 maintainer
Metadata
1 maintainer
Release files for python_lconf_lexer 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| python_lconf_lexer-1.1.1.tar.bz2 | 14.8 kB | Without provenance | Details |
Release files / python_lconf_lexer-1.1.1.tar.bz2
| Download URL | python_lconf_lexer-1.1.1.tar.bz2 |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9bd5e71504cc700f00240a0aead28c618c517755ea091115d75d75d925ef9c4
|
|
BLAKE2b-256 checksum How to use checksums |
d0bb20b47d51aea672b8e8ee9e5b24f3bd143ff2bbc018d72e2e92a476275c89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for python_lconf_lexer 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
