parsedatetime
Parse human-readable date/time strings.
Python 2.7 or greater is required for parsedatetime version 1.0 or greater.
Installing
You can install parsedatetime using:
pip install parsedatetime
Running Tests
From the source directory:
make test
To run tests on several python versions, type tox:
$ tox [... tox creates a virtualenv for every python version and runs tests inside of each] py27: commands succeeded py35: commands succeeded
This assumes that you have python2.7, python3.5, etc in PATH.
Using parsedatetime
An example of how to use parsedatetime:
import parsedatetime
cal = parsedatetime.Calendar()
cal.parse("tomorrow")
To get it to a Python datetime object:
from datetime import datetime
from time import mktime
time_struct, parse_status = cal.parse("tomorrow")
datetime.fromtimestamp(mktime(time_struct))
Parse datetime with timezone support (using pytz package):
import parsedatetime
import pytz
from pytz import timezone
cal = parsedatetime.Calendar()
datetime_obj, _ = cal.parseDT(datetimeString="tomorrow", tzinfo=timezone("US/Pacific"))
More detailed examples can be found in the examples directory.
Documentation
The generated documentation is included by default in the docs directory and can also be viewed online at https://bear.im/code/parsedatetime/docs/index.html
The docs can be generated by running:
make docs
Notes
The Calendar class has a member property named ptc which is created during the class init method to be an instance of parsedatetime_consts.CalendarConstants().
History
The code in parsedatetime has been implemented over the years in many different languages (C, Clipper, Delphi) as part of different custom/proprietary systems I’ve worked on. Sadly the previous code is not “open” in any sense of that word.
When I went to work for Open Source Applications Foundation and realized that the Chandler project could benefit from my experience with parsing of date/time text I decided to start from scratch and implement the code using Python and make it truly open.
After working on the initial concept and creating something that could be shown to the Chandler folks the code has now evolved to it’s current state with the help the Chandler folks, most especially Darshana.
2 maintainers
Metadata
2 maintainers
Release files for parsedatetime 2.1
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 | |
|---|---|---|---|---|
| parsedatetime-2.1.tar.gz | 56.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| parsedatetime-2.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 94.1 kB
Release files / parsedatetime-2.1.tar.gz
| Download URL | parsedatetime-2.1.tar.gz |
|---|---|
| Size | 56.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17c578775520c99131634e09cfca5a05ea9e1bd2a05cd06967ebece10df7af2d
|
|
BLAKE2b-256 checksum How to use checksums |
8b2037822d52be72c99cad913fad0b992d982928cac882efbbc491d4b9d216a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / parsedatetime-2.1-py2-none-any.whl
| Download URL | parsedatetime-2.1-py2-none-any.whl |
|---|---|
| Size | 37.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
ce9d422165cf6e963905cd5f74f274ebf7cc98c941916169178ef93f0e557838
|
|
BLAKE2b-256 checksum How to use checksums |
851f13fc06097e516f6259d62cea502b116451321c96e18a9d0fff9da3442e02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for parsedatetime 2.1
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.
