Introduction
This Transmogrifier blueprint is based on collective.transmogrifier.sections.tests.PrettyPrinter, which anyone can use in their project by creating a utility like so:
<utility
component="collective.transmogrifier.sections.tests.PrettyPrinter"
name="print" />
Then adding a section to your pipeline like so:
[transmogrifier]
pipeline =
…
print
[print]
blueprint = print
transmogrify.print has has two advantages over the above approach:
It adds the utility for you
It allows you to specify a keys parameter to print individual keys. If no key is provided, it prints the entire item.
Installation
Make sure to require transmogrify.print in your project, e.g.:
from setuptools import setup
setup(
name='migrate',
py_modules=['migrate'],
install_requires=[
'plone.app.transmogrifier',
'transmogrify.filesystem',
'transmogrify.print',
]
)
Then you may use it in your pipelines, e.g.:
[transmogrifier]
pipeline =
data
constructor
# schema
print
[constructor]
blueprint = collective.transmogrifier.sections.constructor
[data]
blueprint = transmogrify.filesystem
directory = silly_content
file-type = Document
[print]
blueprint = transmogrify.print
keys = _path
[schema]
blueprint = plone.app.transmogrifier.atschemaupdater
See: https://github.com/aclark4life/silly_content_import for a working example.
Changelog
0.6.0 (2014-02-04)
Stop multiple prints for multiple keys [djowett]
0.5.0 (2011-08-30)
Fix entry point, now targetting transmogrify [aclark]
0.4.0 (2011-07-31)
Note the existence of collective.transmogrifier.sections.logger which does something similar. [aclark]
0.3.0 (2011-07-31)
Fix blueprint name, should be something unique like transmogrify.print (instead of print). [aclark]
Show keys being used in README [aclark]
0.2.0 (2011-07-31)
Fix package data, setup.py missing include_package_data. [aclark]
0.1.0 (2011-07-31)
Initial release [aclark]
1 maintainer
Metadata
1 maintainer
Release files for transmogrify.print 0.6.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 | |
|---|---|---|---|---|
| transmogrify.print-0.6.0.tar.gz | 3.4 kB | Without provenance | Details |
Release files / transmogrify.print-0.6.0.tar.gz
| Download URL | transmogrify.print-0.6.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23de3a6a1c8d8a18169e56ba123c68ff334a21c01324618db6f9ba8cbf981bf3
|
|
BLAKE2b-256 checksum How to use checksums |
836ea0ab81643307e68419bafa32795721b3ccb9024de52046f693c0e59d47b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for transmogrify.print 0.6.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.
