Installation
pip install pnu-libmanconf
LIBMANCONF(3)
NAME
libmanconf — library for handling man(1) and manpath(1) configuration files
SYNOPSIS
import libmanconf
String, String, List libmanconf.read_man_conf_files(Integer debug_level = 0, String manpath_so_far = '')
DESCRIPTION
The read_man_conf_files() function reads the configuration files located at "/etc/man.conf" and "/usr/local/etc/man.d/*.conf" to configure the manual search path, locales and utility set used by man(1) and related utilities.
The function takes an optional argument debug_level with an integer value from 0 (default) to 3, to print increasingly detailed information on standard error output.
It can also take another optional argument manpath_so_far with a colon separated string of already added directories to the manual path, in order to check for duplicate entries.
It returns a triplet consisting of:
- a string containing colon separated existing MANPATH directories
- a string containing colon separated locales (for example, "fr_FR.UTF-8:ja_JP.eucJP")
- a list containing processors (for example, ["TBL_JA=/usr/local/bin/gtbl", "NROFF_JA=/usr/local/bin/groff -man -dlang=ja_JP.eucJP"])
SEE ALSO
apropos(1), man(1), man.conf(5), manpath(1), whatis(1)
STANDARDS
The libmanconf library is not a standard UNIX one.
It tries to follow the PEP 8 style guide for Python code.
PORTABILITY
To be tested under Windows.
HISTORY
This library was made for the PNU project to factor code for the man(1) and manpath(1) commands.
LICENSE
It is available under the 3-clause BSD license.
AUTHORS
The man.conf(5) manual page is largely based on the one written for FreeBSD by Gordon Tetlow.
1 maintainer
Metadata
1 maintainer
Release files for pnu-libmanconf 1.1.2
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 |
|---|---|---|---|---|
| pnu_libmanconf-1.1.2.tar.gz | 9.6 kB | Without provenance | Details for pnu_libmanconf-1.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pnu_libmanconf-1.1.2-py3-none-any.whl | Python 3 | none | any | Details for pnu_libmanconf-1.1.2-py3-none-any.whl |
Total release size: 18.3 kB
Release files / pnu_libmanconf-1.1.2.tar.gz
| Download URL | pnu_libmanconf-1.1.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
286f2c98eed3196fd54446f8ebe07ca1991a8b983ddd47a49dc965e383aa5004
|
|
BLAKE2b-256 checksum How to use checksums |
7d0f207f47f6525cf35ee603f73c623bdd600caf87811153e54a0208d0acb3be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.12
|
Release files / pnu_libmanconf-1.1.2-py3-none-any.whl
| Download URL | pnu_libmanconf-1.1.2-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
917bb1c93dbe7c081ddebb3d427148b853c55f5ce0547b482299537425364c7b
|
|
BLAKE2b-256 checksum How to use checksums |
98539f1c53a9589ee3916f92c039d64ddac180bb0ce9e16fc26b40a3dc137147
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.12
|
Security for pnu-libmanconf 1.1.2
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.
