et_xmfile
et_xmlfile is a low memory library for creating large XML files.
It is based upon the xmlfile module from lxml with the aim of allowing code to be developed that will work with both libraries. It was developed initially for the openpyxl project but is now a standalone module.
The code was written by Elias Rabel as part of the Python Düsseldorf openpyxl sprint in September 2014.
Note on performance
The code was not developed with performance in mind but turned out to be faster than the existing SAX-based implementation but is significantly slower than lxml’s xmlfile. There is one area where an optimisation for lxml will negatively affect the performance of et_xmfile and that is when using the .element() method on an xmlfile context manager. It is, therefore, recommended not to use this, though the method is provided for code compatibility.
1 maintainer
Metadata
1 maintainer
Release files for et-xmlfile 1.0.1
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 | |
|---|---|---|---|---|
| et_xmlfile-1.0.1.tar.gz | 8.4 kB | Without provenance | Details |
Release files / et_xmlfile-1.0.1.tar.gz
| Download URL | et_xmlfile-1.0.1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
614d9722d572f6246302c4491846d2c393c199cfa4edc9af593437691683335b
|
|
BLAKE2b-256 checksum How to use checksums |
2228a99c42aea746e18382ad9fb36f64c1c1f04216f41797f2f0fa567da11388
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for et-xmlfile 1.0.1
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.
