pygments-openssl
Syntax coloring for OpenSSL configuration files
Overview
This package provides a Pygments lexer for OpenSSL configuration files. The lexer is published as an entry point and Pygments will pick it up automatically.
You can use the openssl language with Pygments:
$ pygmentize -l openssl /etc/openssl/openssl.cnf
In Sphinx documents the lexer is selected with the highlight directive:
.. highlight:: openssl
Installation
Use your favorite installer to install pygments-openssl into the same Python environment you have installed Pygments. For example:
$ pip install pygments-openssl
To verify the installation run:
$ pygmentize -L lexer | grep -i openssl
* openssl:
OpenSSL (filenames *.cnf, *.conf)
Changelog
2.0 - 2026-07-07
Update INI lexer tests for Pygments >= 2.19. [stefan]
Remove support for universal wheels. [stefan]
Remove deprecated license classifier. [stefan]
Upgrade GitHub workflow. [stefan]
Require Python >= 3.5. [stefan]
1.6 - 2023-09-14
Update INI lexer tests for Pygments >= 2.14. [stefan]
Update tox.ini for latest tox. [stefan]
Add GitHub CI workflow. [stefan]
1.5 - 2022-02-27
Add Python 3.8-3.10 to tox.ini. Remove old Python versions. [stefan]
Replace deprecated python setup.py test in tox.ini. [stefan]
Remove deprecated test_suite from setup.py. [stefan]
Move lexer into pygments_openssl namespace. [stefan]
Move metadata to setup.cfg and add a pyproject.toml file. [stefan]
Include tests in sdist but not in wheel. [stefan]
Support new .pragma and .include directives. [stefan]
Pygments 2.11 whitespace token modernization. [stefan]
1.4 - 2019-01-25
Add MANIFEST.in. [stefan]
Release as wheel. [stefan]
1.3 - 2017-02-05
Add a LICENSE file. [stefan]
Add a test suite and fix two minor whitespace lexing issues. [stefan]
1.2 - 2013-11-21
Update documentation. [stefan]
1.1 - 2012-10-12
Detect and color line continuations. [stefan]
1.0 - 2012-10-10
Initial release. [stefan]
1 maintainer
Metadata
1 maintainer
Release files for pygments-openssl 2.0
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 | Actions |
|---|---|---|---|---|
| pygments_openssl-2.0.tar.gz | 7.6 kB | Without provenance | Details for pygments_openssl-2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pygments_openssl-2.0-py3-none-any.whl | Python 3 | none | any | Details for pygments_openssl-2.0-py3-none-any.whl |
Total release size: 13.1 kB
Release files / pygments_openssl-2.0.tar.gz
| Download URL | pygments_openssl-2.0.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
563a622529ffefe73c3c23807b418b9667f36e32ebfd03382e58516ce916fe84
|
|
BLAKE2b-256 checksum How to use checksums |
daad2038d3d141a17120d7bd09fbb95abd1372f5d704d99018b6108f35be4074
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Release files / pygments_openssl-2.0-py3-none-any.whl
| Download URL | pygments_openssl-2.0-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7affefe0126a702478bd535c11304ce034144aad760452a844505d8e85dc9989
|
|
BLAKE2b-256 checksum How to use checksums |
1e5915e3795abf894755c5c843d2873d99946153d9b579b220c0dc5e057c80b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Security for pygments-openssl 2.0
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.
