1 packageManifest
A Python 3 framework for creating and maintaining a generalised manifest of files inspired by the Python MANIFEST.in. The framework would typically used as the basis of some kind of packaging tool to define the file needed for distribution of the package.
1.1 Main Features
YAML based file format
Common manifest operations:
include/exclude
global include/exclude
recursive include/exclude
prune/graft
1.2 Installation
The simplest way to acquire packageManifest is using pip.
pip install packageManifest
1.3 Getting Started
The manifest YAML file is simply a list of the include or exclude operations to comprise the formulation of files. There are six different types of operations - the same as the Python MANIFEST.in.
Each include/exclude operation can take either a files directive or a directory directive, or both, depending on the type of include/exclude being applied.
- include:
files: [ 'LICENSE', 'README.md' ]
- exclude:
files: [ '*.orig' ]
- recursive-include:
directory: 'include'
files: [ '*.h', '*.c' ]
- recursive-exclude:
directory: 'temp/subdir'
files: [ '*' ]
- global-include:
files: [ 'Makefile' ]
- global-exclude:
files: [ '*.txt', '*.tmp', 'test' ]
- prune:
directory: 'bin'
- graft:
directory: 'src'
The files directive contains a list of unix-glob like patterns to be applied to files. The directory directive contains a single character string of the directory.
Using the manifest file is simply a matter of importing the library and using the from_yamlFile class method to import the operations and apply them to the specified root directory of the directory tree from which to extract files.
from package-manifest import Manifest
thisManifest = Manifest.from_yamlFile( 'manifest.yml', '.' )
manifestFiles = thisManifest.apply()
manifestFiles now contains a Python set of the file names from the root directory '.' that have been filtered by the operations specified in the file manifest.yml.
Metadata
Release files for packageManifest 1.0.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 |
|---|---|---|---|---|
| packageManifest-1.0.0.tar.gz | 27.5 kB | Without provenance | Details for packageManifest-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| packageManifest-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for packageManifest-1.0.0-py3-none-any.whl |
Total release size: 186.5 kB
Release files / packageManifest-1.0.0.tar.gz
| Download URL | packageManifest-1.0.0.tar.gz |
|---|---|
| Size | 27.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
977cdf6e57b7e2bbd752ad8587a18381d47d4e53ba0086bad0bec8bfb14cb05d
|
|
BLAKE2b-256 checksum How to use checksums |
945826913d24871eaec9220d9581412458f5b84030bec0ac66e61307b33ad8d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.18.4
|
Release files / packageManifest-1.0.0-py3-none-any.whl
| Download URL | packageManifest-1.0.0-py3-none-any.whl |
|---|---|
| Size | 159.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb51aef5dcf33bf47a7556937b0331eb96fb4c21eeb0f61d49807fe95ae7261a
|
|
BLAKE2b-256 checksum How to use checksums |
922be6dc25104ed7a489369dc8eb46626ce94200ca2a313334b2e56869290534
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.18.4
|
Security for packageManifest 1.0.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.