Group :: Development/Python3
RPM: python3-module-udatetime
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
Current version: 0.0.17-alt1
Build date: 10 december 2022, 15:18 ( 73.9 weeks ago )
Size: 23.34 Kb
Home page: https://pypi.org/project/udatetime
License: Apache-2.0
Summary: Fast RFC3339 compliant Python date-time library
Description:
List of contributors List of rpms provided by this srpm:
ACL:
Build date: 10 december 2022, 15:18 ( 73.9 weeks ago )
Size: 23.34 Kb
Home page: https://pypi.org/project/udatetime
License: Apache-2.0
Summary: Fast RFC3339 compliant Python date-time library
Description:
Handling date-times is a painful act because of the sheer endless amount
of formats used by people. Luckily there are a couple of specified
standards out there like ISO 8601. But even ISO 8601 leaves to many
options on how to define date and time. That's why I encourage using the
RFC3339 specified date-time format.
udatetime offers on average 76% faster datetime object instantiation,
serialization and deserialization of RFC3339 date-time strings.
udatetime is using Python's datetime class under the hood and code
already using datetime should be able to easily switch to udatetime.
All datetime objects created by udatetime are timezone-aware. The
timezones that udatetime uses are fixed-offset timezones, meaning
that they don't observe daylight savings time (DST), and thus return
a fixed offset from UTC all year round.
Current maintainer: Anton Zhukharev of formats used by people. Luckily there are a couple of specified
standards out there like ISO 8601. But even ISO 8601 leaves to many
options on how to define date and time. That's why I encourage using the
RFC3339 specified date-time format.
udatetime offers on average 76% faster datetime object instantiation,
serialization and deserialization of RFC3339 date-time strings.
udatetime is using Python's datetime class under the hood and code
already using datetime should be able to easily switch to udatetime.
All datetime objects created by udatetime are timezone-aware. The
timezones that udatetime uses are fixed-offset timezones, meaning
that they don't observe daylight savings time (DST), and thus return
a fixed offset from UTC all year round.
List of contributors List of rpms provided by this srpm:
- python3-module-udatetime
- python3-module-udatetime-debuginfo
- python3-module-udatetime-benchmark