Ripped from FormEncode and strainer just to support Pythons 2 and 3. Intended for use in your webapp test suites.
Build Status
Branch |
Status |
|---|---|
master |
|
develop |
For Example
There are two main functions you might care to use: eq_xml and in_xml:
>>> from sieve.operators import eq_xml, in_xml >>> a = "<foo><bar>Value</bar></foo>" >>> b = """ ... <foo> ... <bar> ... Value ... </bar> ... </foo> ... """ >>> eq_xml(a, b) True >>> c = "<html><body><foo><bar>Value</bar></foo></body></html" >>> in_xml(a, c) # 'needle' in a 'haystack' True
There are also two sibling convenience functions: assert_eq_xml and assert_in_xml.
Metadata
Release files for sieve 0.1.9
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 | |
|---|---|---|---|---|
| sieve-0.1.9.tar.gz | 5.7 kB | Without provenance | Details |
Release files / sieve-0.1.9.tar.gz
| Download URL | sieve-0.1.9.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c84d8f49cad1ff9c9e35e3acb8978ab5ab11590208fe2e8a3e39e243b2dd51a
|
|
BLAKE2b-256 checksum How to use checksums |
094b86a224cd68c40932d2bfcabc7568f69276a7c0cd9a7beb5778d9745d8227
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sieve 0.1.9
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.