File: control

package info (click to toggle)
python-plaster 1.0-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 388 kB
  • sloc: python: 849; makefile: 153
file content (46 lines) | stat: -rw-r--r-- 1,965 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Source: python-plaster
Section: python
Priority: optional
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Uploaders: Nicolas Dandrimont <olasd@debian.org>
Build-Depends: debhelper-compat (= 11),
               dh-python,
               python3-all,
               python3-pytest,
               python3-setuptools,
               python3-sphinx
Standards-Version: 4.1.4
Homepage: https://pylonsproject.org/projects/plaster/about
Vcs-Git: https://salsa.debian.org/python-team/modules/python-plaster.git
Vcs-Browser: https://salsa.debian.org/python-team/modules/python-plaster

Package: python3-plaster
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}
Description: Python multi-format configuration file loader interface - Python 3.x module
 plaster is a loader interface around arbitrary config file formats. It exists
 to define a common API for applications to use when they wish to load
 configuration settings.
 .
 The library itself does not aim to handle anything except a basic API that
 applications may use to find and load configuration settings. Any specific
 constraints should be implemented in a pluggable loader which can be registered
 via an entrypoint.
 .
 This package provides the Python 3 version of the module.

Package: python-plaster-doc
Architecture: all
Section: doc
Depends: ${misc:Depends}, ${sphinxdoc:Depends}
Description: Python multi-format configuration file loader interface - Documentation
 plaster is a loader interface around arbitrary config file formats. It exists
 to define a common API for applications to use when they wish to load
 configuration settings.
 .
 The library itself does not aim to handle anything except a basic API that
 applications may use to find and load configuration settings. Any specific
 constraints should be implemented in a pluggable loader which can be registered
 via an entrypoint.
 .
 This package provides the documentation of the module.