Peppercorn
A library for converting a token stream into a data structure comprised of sequences, mappings, and scalars, developed primarily for converting HTTP form post data into a richer data structure. It runs on Python 2.7, 3.4, 3.5, 3.6 and 3.7.
Please see https://docs.pylonsproject.org/projects/peppercorn/en/latest/ for the documentation.
See https://github.com/Pylons/peppercorn for in-development version.
Changes
0.6 (2018-08-24)
Add support for Python 3.4, 3.5, 3.6 and 3.7.
Drop support for Python 2.6, 3.2 and 3.3.
Add contributing.md and update docs. See https://github.com/Pylons/peppercorn/issues/13
0.5 (2014-09-29)
Switch to an iterative parser rather than a recursive parser to avoid DoS attacks.
Add the ignore operation. The subsequent data elements in the stream will be ignored until the corresponding __end__ marker. This feature is useful for form elements designed for client-side scripting, such as a “select all” checkbox in the middle of a list of other kinds of fields.
Add support for Python 3.3.
Drop support for Python 2.5 and Jython.
0.4 (2012-02-14)
Drop support for Python 2.4.
Add support for Python 3.2.
Move project to GitHub.
Switch to Pylons Project Sphinx theme.
Add tox configuration.
0.3 (2010-09-02)
0.2 was a brownbag release. Handle the case where rename operation types may not have children.
0.2 (2010-09-02)
Add new operation type: rename. rename begins a special mode. The value of the first subsequent data element in the stream will be used within its parent sequence or mapping. Any remaining data elements until the corresponding __end__ marker are ignored. This is mostly in support of radio buttons. See the rename docs within https://docs.pylonsproject.org/projects/peppercorn/en/latest/ for more information.
0.1 (2010-03-23)
Initial release.
3 maintainers
Metadata
3 maintainers
Release files for peppercorn 0.6
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 |
|---|---|---|---|---|
| peppercorn-0.6.tar.gz | 16.4 kB | Without provenance | Details for peppercorn-0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| peppercorn-0.6-py3-none-any.whl | Python 3 | none | any | Details for peppercorn-0.6-py3-none-any.whl |
Total release size: 21.2 kB
Release files / peppercorn-0.6.tar.gz
| Download URL | peppercorn-0.6.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96d7681d7a04545cfbaf2c6fb66de67b29cfc42421aa263e4c78f2cbb85be4c6
|
|
BLAKE2b-256 checksum How to use checksums |
e47793085de7108cdf1a0b092ff443872a8f9442c736d7ddebdf2f27627935f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.7.0
|
Release files / peppercorn-0.6-py3-none-any.whl
| Download URL | peppercorn-0.6-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46125cad688a9cf3b08e463bcb797891ee73ece93602a8ea6f14e40d1042d454
|
|
BLAKE2b-256 checksum How to use checksums |
1484d8d9c3f17bda2b6f49406982546d6f6bc0fa188a43d4e3ba9169a457ee04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.7.0
|
Security for peppercorn 0.6
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.
