/py-parsedatetime, Python module for parsing human-readable date/time text
2.3, Package name:
py27-parsedatetime-2.3, Maintainer: pkgsrc-users
A collection of routines to input, parse and manipulate date and times.
The text can either be 'normal' date values or it can be human readable.
Required to run:
] Required to build:
Master sites: SHA1:
Version history: (Expand)
- (2017-03-14) Updated to version: py27-parsedatetime-2.3
- (2017-01-24) Updated to version: py27-parsedatetime-2.2
- (2016-04-05) Updated to version: py27-parsedatetime-2.1
- (2014-01-20) Updated to version: py27-parsedatetime-1.1.2
- (2012-10-08) Updated to version: py27-parsedatetime-0.8.7
- (2010-09-05) Updated to version: py26-parsedatetime-0.8.7
CVS history: (Expand)
| 2017-03-13 11:17:36 by Thomas Klausner | Files touched by this commit (2) | |
Updated py-parsedatetime to 2.3.
Fix for Issue #215 (test failure)
| 2017-02-15 01:53:26 by Joerg Sonnenberger | Files touched by this commit (1) |
Add missing py-test-runner dependency.
| 2017-01-24 14:18:04 by Filip Hajny | Files touched by this commit (3) | |
Update time/py-parsedatetime to 2.2.
- Added French locale support
- Added Python 2.6 support
- Minor fixes
| 2016-04-05 16:07:46 by Thomas Klausner | Files touched by this commit (2) |
| 2016-04-05 12:31:38 by Filip Hajny | Files touched by this commit (3) | |
Update time/py-parsedatetime to 2.1 (in-freeze, OK by wiz).
- Issue #156 parsedatetime 2.0 doesn't work on py26
- Issue #155 Relative times containing years fail when computed
from a leap day
- Issue #145 cal.parse('2015-11-18') returns November 19th 2015
- Issue #143 What is the second value returned by `parse`?
- Issue #141 Bad test case in TestComplexDateTimes
- Issue #123 update supporting files for v2.0 release
- Issue #124 Put locales into config-files (yaml)
- Issue #125 Remove extra files
- Issue #137 Year is parsed wrongly if the date is of format
MMM DD, YYxx xx:SS bug
- Issue #136 Why I see 2016 instead of 2015?
- Issue #133 Bug: "2015-01-01" is parsed as the current date.
- Issue #126 "Unresolved attribute reference 'parse' for class
'object'... " in Pycharm IDE. bug
- Issue #120 the pdt_locales/en_AU.py file uses en_A for
the localID instead of en_AU
- Issue #114 Dates in the format 'YYYY-MM-DD HH:MM' give
the incorrect month and day
- Issue #112 Document getting a time from parsedatetime
into a standard Python structure
- Issue #110 AttributeError when running in the context
of an HTTP request
- Issue #109 YearParseStyle is ignored for dates in MM/DD style
- Issue #107 yyyy/mm/dd date format
- Issue #105 "this week" is not parsed
- Issue #103 get UTC times from parseDT - trouble with at 9:30
clock times being interpreted directly in UTC
- Issue #100 Fractional deltas result in incoherent results.
- PR #118 ADD: improve russian locale
- PR #117 ADD: Russian Locale
- PR #116 Fix spelling of "separator".
- PR #115 Update README.rst
- PR #113 Add datetime example to readme.
- PR #111 Allowed real number appear in text like "5.5 days ago"
- Issue #99 Which year is implied when given just a month and day?
Next and last? question
- Issue #96 Word boundary issues for specials (on, at, in) in nlp
- Issue #94 inconsistent application of sourceTime
- Issue #87 nlp() doesn't recognize some "next ..." expressions
- Issue #84 Afternoon? bug
- Issue #82 'last week' and 'next week' are broken
- Issue #81 parse returns default time of 0900 with dates like
'next friday' despite passed struct_time bug
- Issue #78 Link for Travis in README is wrong
- Issue #72 Enable travis
- Issue #71 Calendar() class can not be initialized 1.4 (it's
- Issue #66 Unexpected struct_time flag with Calendar.parse
on HTML <a href> string
- Issue #65 NLP false positives
- Issue #63 Supporting multiple shortweekday abbreviations
- Issue #61 Short weekday abbreviations bug
- Issue #56 Parse words to numbers (thirteen => 13)
- Issue #54 testMonths fails
- commit 107c7e4655 fix for issue 95 - parsing 'next june 15'
- commit 2c0c8ec778 Fixed faulty test, "730am" parses as "73:0 \
which is a bug for a later day.
- commit 6f244e891d Fix "ones" parsing as "1s." Require a word
boundary between spelled numbers and units.
- commit 035818edef Fix "1 day ago" parsing like "1d 1y ago"
where "a" within the word "day" is interpreted as 1.
- commit 45002e6eec Fixes "next week" and similar modifier
+ unit pairs in nlp()
- commit 47d2e1d527 Fixed "last week"
- Updated setup.py for wheel compatibility
- renamed README.txt to README.rst
- renamed MANIFEST to MANIFEST.in
- cleaned up a lot of the doc and notes
- Commit 3fc165e701 mafagafo Now it works for Python 3.4.1
- Commit d5883801e7 borgstrom Restore Python 2.6 compatibility
- Issue #45 make a new release to really fix backwards
- Issue #43 Please tag version 1.3
- Commit 29c5c8961d devainandor fixed Python 3 compatibility
- Commit d7304f18f7 inean Fix support for 'now' when no modifiers
- Commit 26bfc91c28 sashaacker Added parseDT method.
- Commit 848deb47e2 rmecham Added support for dotted meridians.
- Commit c821e08ce2 ccho-sevenrooms corrected misspelling
- Biggest change is the addition of the nlp() function
by Geoffrey Floyd:
nlp() function that utilizes parse() after making judgements
about what datetime information belongs together. It makes
logical groupings based on proximity and returns a parsed
datetime for each matched grouping of datetime text, along
with location info within the given inputString.
| 2014-01-19 20:52:44 by Thomas Klausner | Files touched by this commit (3) | |
Update to 1.1.2:
03 Mar 2013 - bear
bumped version to 1.1.1
Ugh - debug log caused an error during formatting
Issue 10 https://github.com/bear/parsedatetime/issues/10
14 Nov 2012 - bear
Added test for "last friday"
Updated MANIFEST to reflect renamed README file
Bumped version to 1.1
15 Mar 2011 - bear
Updated 1.0.0 code to work with 2.6+ (need to try 2.5) and also updated
docs and other supporting code
07 Sep 2009 - bear
Created branches/python25 from current trunk to save the current code
Converted trunk to Python 3 and also refactored how the module is structured
so that it no longer requires import parsedatetime.parsedatetime
Bumped version to 1.0.0 to reflect the major refactoring
| 2012-10-08 15:04:32 by Aleksej Saushev | Files touched by this commit (146) |
Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.
| 2010-09-04 20:45:22 by Matthias Scheler | Files touched by this commit (1) |
Remove me as maintainer. This module isn't very useful after all.