zope.datetime
Functions to parse and format date/time strings in common formats.
The documentation is hosted at https://zopedatetime.readthedocs.io/
CHANGES
6.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
5.1 (2025-02-14)
Add support for Python 3.12, 3.13.
Drop support for Python 3.7, 3.8.
5.0.0 (2023-04-25)
Drop support for Python 2.7, 3.5, 3.6.
Add support for Python 3.10, 3.11.
4.3.0 (2021-02-26)
Drop support for Python 3.4.
Add support for Python 3.7, 3.8 and 3.9.
Prevent a DeprecationWarning in Python 3.8+ when using a parameter for iso8601_date, rfc850_date, or rfc1123_date which has to be converted via its __int__ method.
4.2.0 (2017-08-14)
Remove support for guessing the timezone name when a timestamp exceeds the value supported by Python’s localtime function. On platforms with a 32-bit time_t, this would involve parsed values that do not specify a timezone and are past the year 2038. Now the underlying exception will be propagated. Previously an undocumented heuristic was used. This is not expected to be a common issue; Windows, as one example, always uses a 64-bit time_t, even on 32-bit platforms. See https://github.com/zopefoundation/zope.datetime/issues/4
Use true division on Python 2 to match Python 3, in case certain parameters turn out to be integers instead of floating point values. This is not expected to be user-visible, but it can arise in artificial tests of internal functions.
Add support for Python 3.5 and 3.6.
Drop support for Python 2.6, 3.2 and 3.3.
4.1.0 (2014-12-26)
Add support for PyPy and PyPy3.
Add support for Python 3.4.
Add support for testing on Travis.
4.0.0 (2013-02-19)
Add support for Python 3.2 and 3.3.
Drop support for Python 2.4 and 2.5.
3.4.1 (2011-11-29)
Add test cases from LP #139360 (all passed without modification to the parse function).
Remove unneeded zope.testing dependency.
3.4.0 (2007-07-20)
Initial release as a separate project.
Metadata
Release files for zope.datetime 6.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 | |
|---|---|---|---|---|
| zope_datetime-6.0.tar.gz | 50.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_datetime-6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 92.8 kB
Release files / zope_datetime-6.0.tar.gz
| Download URL | zope_datetime-6.0.tar.gz |
|---|---|
| Size | 50.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c110ff575fbfbac9dc549d825b6a673c8023a047a9f8a9594b8aa56ab1472513
|
|
BLAKE2b-256 checksum How to use checksums |
8d2048c3611863f6cf6ce497f631d9fbbd5a56f50d802753093190a90a6537ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / zope_datetime-6.0-py3-none-any.whl
| Download URL | zope_datetime-6.0-py3-none-any.whl |
|---|---|
| Size | 42.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0aee3da0a44ec9fc42ce717bf21370a00c32ca082c3d4f5513f3b7c5cbfbe72
|
|
BLAKE2b-256 checksum How to use checksums |
e9716cc1f2164cd98c3d2b87e81db7502b941d66099aaf4503c34aab54ff3650
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for zope.datetime 6.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.
