Notes
This recipe is only tested with Debian, Gentoo and minitage. The z3c.recipe.staticlxml recipe is better maintained.
Options
- egg
The desired lxml egg version (like lxml==2.2.6).
- libxslt-url
The URL to download the libxslt tarballe, the default value is: ‘http://xmlsoft.org/sources/libxslt-1.1.26.tar.gz’
- libxml2-url
The URL to download the libxml2 tarball, the default value is: ‘http://xmlsoft.org/sources/libxml2-2.7.7.tar.gz’
Example buildout configuration
[buildout] parts = lxml eggs = lxml == 2.2.6 [lxml] recipe=plone.recipe.lxml egg = lxml == 2.2.6
Metadata
Release files for plone.recipe.lxml 0.4
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 |
|---|---|---|---|---|
| plone.recipe.lxml-0.4.tar.gz | 2.9 kB | Without provenance | Details for plone.recipe.lxml-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plone.recipe.lxml-0.4-py2.6.egg | Legacy Egg format | - | - | Details for plone.recipe.lxml-0.4-py2.6.egg |
Total release size: 9.2 kB
Release files / plone.recipe.lxml-0.4.tar.gz
| Download URL | plone.recipe.lxml-0.4.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
313e74f3dad4bc443fa3f1d8a60ff9faac73242878588a68230916579cdf71f5
|
|
BLAKE2b-256 checksum How to use checksums |
a829bf364326b6f674f6ad975b08ce39d7bfd591841df67ad557a1d219d347e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / plone.recipe.lxml-0.4-py2.6.egg
| Download URL | plone.recipe.lxml-0.4-py2.6.egg |
|---|---|
| Size | 6.3 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
95b00f7c8d92427c4ceaf9d0dfbf7d49100a9211de264ed3827bdd908ad3ec56
|
|
BLAKE2b-256 checksum How to use checksums |
ff60909d00b941984ae5e2583ea7c0bad69a17d424fa6f4adc9ddfd7df8a9ae8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.recipe.lxml 0.4
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.