Zope-datetime

Latest version: v4.2.0

Safety actively analyzes 613568 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

4.2.1

==================

- Nothing changed yet.

4.2.0

==================

- 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

==================

- Add support for PyPy and PyPy3.

- Add support for Python 3.4.

- Add support for testing on Travis.

4.0.0

==================

- Add support for Python 3.2 and 3.3.

- Drop support for Python 2.4 and 2.5.

3.4.1

==================

- Add test cases from LP 139360 (all passed without modification to
the ``parse`` function).

- Remove unneeded ``zope.testing`` dependency.

3.4.0

==================

- Initial release as a separate project.

Links

Releases

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.