zope.filerepresentation
The interfaces defined here are used for file-system and file-system-like representations of objects, such as file-system synchronization, FTP, PUT, and WebDAV.
Documentation is hosted at https://zopefilerepresentation.readthedocs.io/
Changes
7.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
6.1 (2025-02-14)
Drop support for Python 3.7, 3.8.
Add support for Python 3.12, 3.13.
6.0 (2023-01-14)
Drop support for Python 2.7, 3.5, 3.6.
Add support for Python 3.9, 3.10, 3.11.
5.0.0 (2020-03-31)
Drop support for Python 3.4.
Add support for Python 3.7 and 3.8.
Ensure all objects have a consistent interface resolution order. See issue 7.
4.2.0 (2017-08-10)
Add support for Python 3.5 and 3.6.
Drop support for Python 2.6 and 3.3.
4.1.0 (2014-12-27)
Add support for PyPy3.
Add support for Python 3.4.
4.0.2 (2013-03-08)
Add Trove classifiers indicating CPython and PyPy support.
4.0.1 (2013-02-11)
Add tox.ini to release.
4.0.0 (2013-02-11)
Add support for Python 3.3 and PyPy.
Drop support for Python 2.4 / 2.5.
3.6.1 (2011-11-29)
Add undeclared zope.schema dependency.
Remove zope.testing test dependency and test extra.
3.6.0 (2009-10-08)
Add IRawReadFile and IRawWriteFile interfaces. These extend IReadFile and IWritefile, respectively, to behave pretty much like a standard Python file object with a few embellishments. This in turn allows efficient, iterator- based implementations of file reading and writing.
Remove dependency on zope.container: IReadDirectory and IWriteDirectory inherit only from interfaces defined in zope.interface and zope.interface.common.mapping.
3.5.0 (2009-01-31)
Change use of zope.app.container to zope.container.
3.4.0 (2007-10-02)
Initial Zope-independent release.
Metadata
Release files for zope.filerepresentation 7.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 |
|---|---|---|---|---|
| zope_filerepresentation-7.0.tar.gz | 16.4 kB | Without provenance | Details for zope_filerepresentation-7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zope_filerepresentation-7.0-py3-none-any.whl | Python 3 | none | any | Details for zope_filerepresentation-7.0-py3-none-any.whl |
Total release size: 24.1 kB
Release files / zope_filerepresentation-7.0.tar.gz
| Download URL | zope_filerepresentation-7.0.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58604043795f98e37908912d53c7f582b42fc248314c31fab7df010cd3e889f4
|
|
BLAKE2b-256 checksum How to use checksums |
e70e994e45f62c45e19068f60bc1f902e28d9ccbc9f1cbfac6005ad1bb80015e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / zope_filerepresentation-7.0-py3-none-any.whl
| Download URL | zope_filerepresentation-7.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d4f241a87ef87987f065489654a00481758a278d8f8eac23127739a198389c0
|
|
BLAKE2b-256 checksum How to use checksums |
2c93d90e2cce3703cbcb3491b6d94b8a6596596567450b3f07894014e528cdb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for zope.filerepresentation 7.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.
