Python’s standard library contains a pretty print module (pprint), but it’s output is in a very odd style. This project is a fairly straightforward fork which aim to create output suitable for use in python code with standard formatting.
I copied both pprint.py and test_pprint.py from the cpython (2.6) code base, and made the minimal changes to make things work, and all the tests pass. The result should be equally reliable as the stdlib pprint library.
>>> example_obj = {1:2, 3:4, 'range':range(3)} >>> example_obj['range'].append(range(5)) >>> example_obj['range'].append(range(20))>>> import buck.pprint >>> buck.pprint.pprint(example_obj) { 1: 2, 3: 4, 'range': [ 0, 1, 2, [0, 1, 2, 3, 4], [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19], ], }
This is how I’d format this object in my own code. Below is the formatting that the standard pprint gives. I believe you’ll agree that it’s not a style you’ve ever seen in real python code.
>>> import pprint
>>> pprint.pprint(example_obj)
{1: 2,
3: 4,
'range': [0,
1,
2,
[0, 1, 2, 3, 4],
[0,
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19]]}
History
0.0
2013-03-28 – Initial release.
Metadata
Release files for buck.pprint 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 |
|---|---|---|---|---|
| buck.pprint-0.0.tar.gz | 6.4 kB | Without provenance | Details for buck.pprint-0.0.tar.gz |
Release files / buck.pprint-0.0.tar.gz
| Download URL | buck.pprint-0.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4f110d370262bf971269020d47dec5f795de334b6365fcf8fd610f9df1a2ec8
|
|
BLAKE2b-256 checksum How to use checksums |
d77af59450dbe6fd7fdab3bd40195358cd08ccb316da2fa47bfeb5b734896269
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buck.pprint 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.