Description
pyRFC3339 parses and generates RFC 3339-compliant timestamps using Python datetime.datetime objects.
>>> from pyrfc3339 import generate, parse
>>> from datetime import datetime
>>> import pytz
>>> generate(datetime.utcnow().replace(tzinfo=pytz.utc)) #doctest:+ELLIPSIS
'...T...Z'
>>> parse('2009-01-01T10:01:02Z')
datetime.datetime(2009, 1, 1, 10, 1, 2, tzinfo=<UTC>)
>>> parse('2009-01-01T14:01:02-04:00')
datetime.datetime(2009, 1, 1, 14, 1, 2, tzinfo=<UTC-04:00>)
Installation
To install the latest version from PyPI:
$ pip install pyRFC3339
To install the latest development version:
$ pip install https://github.com/kurtraschke/pyRFC3339/tarball/master#egg=pyRFC3339-dev
To build the documentation with Sphinx:
$ pip install Sphinx
$ python setup.py build_sphinx
The documentation is also available online at:
https://pythonhosted.org/pyRFC3339/
Metadata
Release files for pyRFC3339 0.2
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 |
|---|---|---|---|---|
| pyRFC3339-0.2.tar.gz | 5.1 kB | Without provenance | Details for pyRFC3339-0.2.tar.gz |
Release files / pyRFC3339-0.2.tar.gz
| Download URL | pyRFC3339-0.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a504ff6bcb363fa402d393f65fe5f542475e54fbfc55817b80892ba93b22e6de
|
|
BLAKE2b-256 checksum How to use checksums |
9c80472db644715f8bd7d7bb5df77c740605549ed7d059c4ebcfcbd4cd4efd84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyRFC3339 0.2
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.