Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tonyg/python-rfc3339
Implementation of the majority of RFC 3339 for python.
https://github.com/tonyg/python-rfc3339
Last synced: 3 days ago
JSON representation
Implementation of the majority of RFC 3339 for python.
- Host: GitHub
- URL: https://github.com/tonyg/python-rfc3339
- Owner: tonyg
- Created: 2010-02-26T03:10:11.000Z (over 14 years ago)
- Default Branch: master
- Last Pushed: 2021-05-12T14:51:44.000Z (over 3 years ago)
- Last Synced: 2024-10-31T23:31:13.357Z (10 days ago)
- Language: Python
- Homepage:
- Size: 18.6 KB
- Stars: 54
- Watchers: 5
- Forks: 10
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Python RFC 3339 implementation
Implementation of the majority of
. Provides an implementation of
`tzinfo` for UTC (why isn't this in the standard library?) as well as
various parsing and formatting routines based on RFC 3339's syntax for
dates and times.Use datetime.datetime.isoformat() as an inverse of the various parsing
routines in this module.This library sticks quite closely to the RFC 3339 profile of ISO
8601. If that's too strict for you, and you need something for parsing
more general ISO 8601 dates and times, you might find
[pyiso8601](https://github.com/micktwomey/pyiso8601) (in debian as package
[`python-iso8601`](http://packages.debian.org/search?keywords=python-iso8601))
useful.## Examples and documentation
See the docstrings in the rfc3339 module source code itself.
## Limitations and potential improvements
Limitations, with respect to RFC 3339:
- Section 4.3, "Unknown Local Offset Convention", is not implemented.
- Section 5.6, "Internet Date/Time Format", is the ONLY supported format
implemented by the various parsers in this module. (Section 5.6 is
reproduced in its entirety below.)- Section 5.7, "Restrictions", is left to the datetime.datetime constructor
to implement, with the exception of limits on timezone
minutes-east-of-UTC magnitude. In particular, leap seconds are not
addressed by this module. (And it appears that they are not supported
by datetime, either.)Potential Improvements:
- Support for leap seconds. (There's a table of them in RFC 3339
itself, and
is supposed to update monthly.)## Maintainer
Tony Garnock-Jones
## Copyright
rfc3339.py -- Implementation of the majority of RFC 3339 for python.
Copyright (c) 2008, 2009, 2010 LShift Ltd.
Copyright (c) 2011 Tony Garnock-JonesPermission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.