Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Upstream changes:
0.05 Thu Jun 5 12:52:12 WIB 2014
This release is done by SHARYANTO
Add 'format' argument (RT#95998)
Support '13 Nov 1986' format (RT#95999)
|
|
1.97 2016-03-23
- This release is based on version 2016c of the Olson database. This release
includes contemporary changes for Azerbaijan and Chile.
1.96 2016-03-15
- This release is based on version 2016b of the Olson database. This release
includes contemporary changes for Russia, Haiti, and Palestine.
|
|
1.03 2016-03-25
- Rebuilt all locale data with CLDR 29, released on 2016-03-19.
|
|
1.26 2016-03-21
- Switched from Module::Build to ExtUtils::MakeMaker. Implementation by Karen
Etheridge. GitHub #13.
|
|
|
|
|
|
v2.1
- Issue #156 parsedatetime 2.0 doesn't work on py26
v2.0
- 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"
v1.5
- 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
in Calendar.parseDT
- 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
fine)
- 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 am"
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"
v1.4
- 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
1.3
- Issue #45 make a new release to really fix backwards
compatibility
- Issue #43 Please tag version 1.3
- Commit 29c5c8961d devainandor fixed Python 3 compatibility
in pdtLocale_icu
- Commit d7304f18f7 inean Fix support for 'now' when no modifiers
are present
- Commit 26bfc91c28 sashaacker Added parseDT method.
- Commit 848deb47e2 rmecham Added support for dotted meridians.
- Commit c821e08ce2 ccho-sevenrooms corrected misspelling
of 'thirteen'
- 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.
|
|
|
|
|
|
|
|
|
|
== Version 0.3.47 (tzdata v2016b) - 15-Mar-2016
* Updated to tzdata version 2016b
(https://mm.icann.org/pipermail/tz-announce/2016-March/000036.html).
|
|
* Add a CONTRIBUTING.md file.
* Allow any characters to be used in alternate style formats.
* Update to tzdata version 2016b.
|
|
1.25 2016-03-06
- DateTime->from_object would die if given a DateTime::Infinite object. Now it
returns another DateTime::Infinite object. Reported by Greg Oschwald. RT
#112712.
|
|
|
|
Upstream changes:
0.13 2015-10-01
- Fixed pod warnings, by neilbowers
- Made all the SEE ALSO references hyperlinks, and made mentions
of other modules into links as well.
|
|
Add LICENSE
Update DEPENDS
Upstream changes:
0.18 2015-11-11
- added a test; depends on DateTime::Set 0.3600
0.17 2005-08-11
- added a test and fixed a bug where the parameter to
next($dt) had a timezone. Reported by Simon Wistow.
|
|
Upstream changes:
0.16 2015-04-17
- Fixed problem when GMP library was used.
0.15 2015-04-12
- Forgot to update MANIFEST
0.14 2015-04-12
- NTP epoch added (Michiel Beijen)
|
|
Upstream changes:
0.402 2015-07-06
- included META.JSON (closes RT #105633, by ETHER)
- added contributors list (and put back SPOON as the main author)
|
|
Add LICENSE
Upstream changes:
0.06 2016-02-12
- Fixed typo in regex that strangely works most of the time
|
|
Upstream changes:
1.03 2015-08-02 <schubiger@cpan.org>
- Merged development version to stable.
1.02_03 2015-07-21 <schubiger@cpan.org>
- Suggestions for simple documentation improvements.
[rt #98634 - Tim Bunce]
1.02_02 2015-06-05 <schubiger@cpan.org>
- Add encoding directive to POD. [rt #105000 - Debian Perl Group]
1.02_01 2014-02-09 <schubiger@cpan.org>
- Add metadata repository link. [David Steinbrunner]
|
|
Upstream changes:
0.16011 2015-06-19T13:40:27Z
- Support full interval syntax [pr #7]
|
|
Upstream changes:
0.13 2015-10-04 23:38:13Z
- make all tests pass with both the current DateTime::Locale and the
upcoming new version (currently still in trial releases).
0.12 2015-09-27 05:01:39Z
- fix new test that may fail with older Moose
|
|
Upstream changes:
0.3600 2015-11-11
- move t/22intersects.t to DT::Event::Recurrence module
0.3500 2015-11-10
- [rt.cpan.org #108633] Recurrent event does not intersect indefinite future,
test contributed by Brett Watson.
- documentation - intersects() returns 0 for false, and 'undef' for
undecidable.
|
|
not clear all bits. (Can happen on Linux --
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/67583)
|
|
1.24 2016-02-29
- The last release partially broke $dt->time. If you passed a value to use as
unit separator, this was ignored. Reported by Sergiy Zuban. RT #112585.
1.23 2016-02-28
- Make all DateTime::Infinite objects return the system's representation of
positive or negative infinity for any method which returns a number of
string representation (year(), month(), ymd(), iso8601(), etc.). Previously
some of these methods could return "Nan", "-Inf--Inf--Inf", and other
confusing outputs. Reported by Greg Oschwald. RT #110341.
1.22 2016-02-21 (TRIAL RELEASE)
- Fixed several issues with the handling of non-integer values passed to
from_epoch().
This method was simply broken for negative values, which would end up being
incremented by a full second, so for example -0.5 became 0.5.
The method did not accept all valid float values. Specifically, it did not
accept values in scientific notation.
Finally, this method now rounds all non-integer values to the nearest
millisecond. This matches the precision we can expect from Perl itself (53
bits) in most cases.
Patch by Christian Hansen. GitHub #11.
1.21 2015-09-30
- Make all tests pass with both the current DateTime::Locale and the upcoming
new version (currently still in trial releases).
|
|
Upstream changes:
1.64 2016-02-21
- Changed how a string that contains separate epoch and nanosecond fields is
turned into a DateTime object in order to deal with changes coming in the
next DateTime release.
1.63 2016-01-13
[BUG FIXES]
- The behaviour of silently ignoring text after the matching part was
lost in the rewrite. This has been restored. Patch by Dagfinn Ilmari
Manns疇ker. RT #111155.
1.62 2015-12-19
[BUG FIXES]
- When on_error was set to something that did not die (including the default
error handling), calling ->parse_datetime with some bad inputs could cause
the module to error out internally by trying to call methods on an undefined
value instead of returning undef. Reported by Mike Dorman. RT #110247.
|
|
|
|
|
|
Version 0.9.0
=============
*released on 15 February 2016*
- The ``collections`` parameter is now required in pair configurations.
Vdirsyncer will tell you what to do in its error message. See :gh:`328`.
|
|
This release brings:
- support for the latest libSystem
- further improvements
|
|
Based on version 2016a of the IANA Time Zone Database
(https://mm.icann.org/pipermail/tz-announce/2016-January/000035.html).
|
|
ocaml.mk. It was becoming more trouble than it was worth: only a minority
of packages used it, and it only made Makefiles more confusing.
(I've left out some packages: these will be updated forthwith)
|
|
Version 0.8.1
=============
*released on 30 January 2016*
- Fix error messages when invalid parameter fetching strategy is used. This is
important because users would receive awkward errors for using deprecated
``keyring`` fetching.
Version 0.8.0
=============
*released on 27 January 2016*
- Keyring support has been removed, which means that ``password.fetch =
["keyring", "example.com", "myuser"]`` doesn't work anymore.
For existing setups: Use ``password.fetch = ["command", "keyring", "get",
"example.com", "myuser"]`` instead, which is more generic. See the
documentation for details.
- Now emitting a warning when running under Python 2. See :gh:`219`.
|
|
1.95 2016-01-27
- This release is based on version 2016a of the Olson database. This release
includes contemporary changes for the Cayman Islands, Iran, and Chrita,
Russia.
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
BUILD_DEPENDS+= p5-Test-Warnings-[0-9]*:../../devel/p5-Test-Warnings
|
|
Upstream changes:
0.52 2015.04.16
The type of the Time::NVtime pointer is NV ()() not double ()(), as can be seen from looking at the Time::HiRes source.
On Linux x86_64 on a uselongdouble build when you replace the Time::NVtime entry with a
double (*)() pointer calls to that function end up leaving an entry on the FPU stack,
eventually causing the failure seen at https://rt.perl.org/Ticket/Display.html?id=123879
This minimal commit fixes that issue and allows DBIX::Class::TimeStamp to pass its tests.
(Tony Cook)
|
|
1.31 2015-10-20
- No Changes since 1.30_01
1.30_01 2015-09-01
- Ignore some tests on non *nix platforms
- fix compile warnings
- Inherit from Dynaloader (fix static build issues)
- Fix windows mem corruption
1.30 2015-05-16
- Stable release. Overview from 1.29:
- Make strftime more portable + fix %z %z
- Add many more tests
- Clean inheritance
1.29_05 2015-05-02
- Combine multiple 'use constant' statements (saves 0.5ms at runtime)
- Don't leave c_epoch undef
- deprecate parse() function
- More constructor tests
- export() calls Exporter::export
1.29_04 2015-04-09
- Clean inheritance of Exporter and DynaLoader (Thanks dolmen!)
- Refactor _strftime to use localtime/gmtime to generate tm struct
1.29_03 2015-04-04
- Don't mix gmtime and mktime in _strftime
- Clean whitespace at end of lines
- Add more tests for DST issues and also strptime parsing
1.29_02 2015-04-04
- Fix handling of %Z and %z in strftime (hopefully)
- Remove compile warnings for int cast
1.29_01 2015-03-30
- Fix handling of %Z and %z in strftime (in progress)
- Remove unused constants from Time::Seconds (Thanks Xaerxess!)
- _strftime: use system mktime to better support past/future dates
- Relicense strptime as BSD 2-clause http://git.io/vfNSg
|
|
|
|
|
|
TZInfo::Data contains data from the IANA Time Zone database packaged as Ruby
modules for use with TZInfo.
TZInfo::Data is the public domain [IANA Time Zone
Database](http://www.iana.org/time-zones) packaged as a set of Ruby modules
for use with [TZInfo](http://tzinfo.github.io).
If TZInfo::Data is installed, TZInfo will automatically use it as its source
of time zone data. If TZInfo::Data is not available, TZInfo will attempt to
use the system zoneinfo files instead. Please refer to the [TZInfo
documentation](http://rubydoc.info/gems/tzinfo/frames) for further details.
|
|
Version 1.2.2 - 8-Aug-2014
--------------------------
* Fix an error with duplicates being returned by Timezone#all_country_zones
and Timezone#all_country_zone_identifiers when used with tzinfo-data
v1.2014.6 or later.
* Use the zone1970.tab file for country timezone data if it is found in the
zoneinfo directory (and fallback to zone.tab if not). zone1970.tab was added
in tzdata 2014f. zone.tab is now deprecated.
Version 1.2.1 - 1-Jun-2014
--------------------------
* Support zoneinfo files generated with zic version 2014c and later.
* On platforms that only support positive 32-bit timestamps, ensure that
conversions are accurate from the epoch instead of just from the first
transition after the epoch.
* Minor documentation improvements.
Version 1.2.0 - 26-May-2014
---------------------------
* Raise the minimum supported Ruby version to 1.8.7.
* Support loading system zoneinfo data on FreeBSD, OpenBSD and Solaris.
Resolves #15.
* Add canonical_identifier and canonical_zone methods to Timezone. Resolves #16.
* Add a link to a DataSourceNotFound help page in the TZInfo::DataSourceNotFound
exception message.
* Load iso3166.tab and zone.tab files as UTF-8.
* Fix Timezone#local_to_utc returning local Time instances on systems using UTC
as the local time zone. Resolves #13.
* Fix == methods raising an exception when passed an instance of a different
class by making <=> return nil if passed a non-comparable argument.
* Eliminate "require 'rational'" warnings. Resolves #10.
* Eliminate "assigned but unused variable - info" warnings. Resolves #11.
* Switch to minitest v5 for unit tests. Resolves #18.
Version 1.1.0 - 25-Sep-2013
---------------------------
* TZInfo is now thread safe. ThreadSafe::Cache is now used instead of Hash
to cache Timezone and Country instances returned by Timezone.get and
Country.get. The tzinfo gem now depends on thread_safe ~> 0.1.
* Added a transitions_up_to method to Timezone that returns a list of the times
where the UTC offset of the timezone changes.
* Added an offsets_up_to method to Timezone that returns the set of offsets
that have been observed in a defined timezone.
* Fixed a "can't modify frozen String" error when loading a Timezone from a
zoneinfo file using an identifier String that is both tainted and frozen.
Resolves #3.
* Support TZif3 format zoneinfo files (now produced by zic from tzcode version
2013e onwards).
* Support using YARD to generate documentation (added a .yardopts file).
* Ignore the +VERSION file included in the zoneinfo directory on Mac OS X.
* Added a note to the documentation concerning 32-bit zoneinfo files (as
included with Mac OS X).
Version 1.0.1 - 22-Jun-2013
---------------------------
* Fix a test case failure when tests are run from a directory that contains a
dot in the path (issue #29751).
Version 1.0.0 - 2-Jun-2013
--------------------------
* Allow TZInfo to be used with different data sources instead of just the
built-in Ruby module data files.
* Include a data source that allows TZInfo to load data from the binary
zoneinfo files produced by zic and included with many Linux and Unix-like
distributions.
* Remove the definition and index Ruby modules from TZInfo and move them into
a separate TZInfo::Data library (available as the tzinfo-data gem).
* Default to using the TZInfo::Data library as the data source if it is
installed, otherwise use zoneinfo files instead.
* Preserve the nanoseconds of local timezone Time objects when performing
conversions (issue #29705).
* Don't add the tzinfo lib directory to the search path when requiring 'tzinfo'.
The tzinfo lib directory must now be in the search path before 'tzinfo' is
required.
* Add utc_start_time, utc_end_time, local_start_time and local_end_time instance
methods to TimezonePeriod. These return an identical value as the existing
utc_start, utc_end, local_start and local_end methods, but return Time
instances instead of DateTime.
* Make the start_transition, end_transition and offset properties of
TimezonePeriod protected. To access properties of the period, callers should
use other TimezonePeriod instance methods instead (issue #7655).
|
|
|
|
|
|
|
|
Version 0.7.5
=============
*released on 23 December 2015*
- Fixed a bug in :storage:`remotestorage` that would try to open a CLI browser
for OAuth.
- Fix a packaging bug that would prevent vdirsyncer from working with newer
lxml versions.
|
|
Version 0.7.4
=============
*released on 22 December 2015*
- Improved error messages instead of faulty server behavior, see :gh:`290` and
:gh:`300`.
- Safer shutdown of threadpool, avoid exceptions, see :gh:`291`.
- Fix a sync bug for read-only storages see commmit
`ed22764921b2e5bf6a934cf14aa9c5fede804d8e`.
- Etag changes are no longer sufficient to trigger sync operations. An actual
content change is also necessary. See :gh:`257`.
- :storage:`remotestorage` now automatically opens authentication dialogs in
your configured GUI browser.
- **Packagers:** ``lxml>=3.1`` is now required (newer lower-bound version).
|