version detection (thanks to John Marino for reporting this).
Changes from 1.4.1 include:
* Switched from personal fork of OCaml curses bindings to the
community-maintained library from
http://www.nongnu.org/ocaml-tmk/ .
* Fixed bug which prevented "quick add" feature from accepting
UTF-8 encoded text.
* Implemented improved support for Remind's new "reminder
directory" capability.
Fixed an instance of insecure tempfile creation. This
addresses a security vulnerability that had the potential to
cause data loss.
Modified the configure script to support weird locations of
ncurses term.h .
Deprecated the 'calendar_selection' colorable object. For
consistency with the rest of the Wyrd interface, the selected
calendar day is now rendered in reverse video.
Added the 'untimed_bold' configuration variable for selecting
between normal and boldface rendering of untimed reminders.
Added support for remind's 'filedir()' function within INCLUDE
directives, for those who like to
"INCLUDE [filedir()]/some-extra-reminders". Thanks to Stefan
Wehr for the patch.
Implemented more extensive shell-expansion of filenames specified
within wyrdrc, enabling the use of idioms like
'set reminders_file="$DOT_REMINDERS"'.
* Added support for Remind 3.1.0 advance warning of reminders
throughout the Wyrd interface, enabled via the 'advance_warning'
configuration variable.
* Support new Remind 3.1.0 date formatting.
* Added the untimed_window_width rcfile option, which lets the
user set the width of the windows on the right side of the
display.
Tweaked the resize handler so Wyrd does not completely die
when the terminal is resized too small.
Made modifications to support rendering UTF-8 reminders
(requires ncurses built with wide char support)
* Added the home_sticky option, allowing the cursor position
to automatically track the current time.
Added command-line option to append reminders using the
natural language parser.
* Eliminated dependence on Bash-style tilde expansion.
3.2 (2012-11-27)
----------------
* Documentation file layout restructuring.
[thet]
* Fix time support. vTime events can be instantiated with a datetime.time
object, and do not inherit from datetime.time itself.
[rdunklau]
* Correctly handle tzinfo objects parsed with dateutil. Fixes#77.
[warvariuc, thet]
* Text values are escaped correclty. Fixes#74.
[warvariuc]
* Returned old folding algorithm, as the current implementation fails in some
cases. Fixes#72, Fixes#73.
[warvariuc]
* Supports to_ical() on date/time properties for dates prior to 1900.
[cdevienne]
Upstream changes:
1.56 2012-11-30
- The previous release was missing some files. That's what I get for running
"git clean -dxf". Reported by Andreas Koenig. RT #81593.
1.55 2012-11-30
- Updated mapping from Win32 to Olson time zone names. Patch by Andrey
Makhnutin. RT #81456.
Upstream changes:
0.78 2012-11-16
- Reverted the change to round nanoseconds up or down in various
situtations. Now we always round down. This avoids the case where rounding
up would require us to then increment the second value (which could then
require us to increment the minute, which could then require us to increment
the hour, which could then ...).
In other words, we don't want to round 2011-12-31T23:59:59.999999 up to
2012-01-01T00:00:00, because that would be insane.
This applies to the return values for ->microsecond, ->millisecond, and the
%N specifier for strftime.
Patch by Martin Hasch. RT #79845.
Upstream changes:
1.54 2012-11-13
- This release is based on version 2012j of the Olson database. This release
includes contemporary changes for Libya.
Upstream changes:
1.53 2012-11-03
- This release is based on version 2012i of the Olson database. This release
includes contemporary changes for Cuba.
1.52 2012-10-31
- This release is based on version 2012h of the Olson database. This release
includes contemporary changes for Brazil, Israel, and Jordan.
1.51 2012-10-18
- This release is based on version 2012g of the Olson database. This release
includes contemporary changes for Palestine and Samoa.
1.50 2012-09-16
- In scalar context, DateTime::TimeZone->names_in_category returned an
arrayref containing an arrayref (rather than _just_ an arrayref). Reported
by Ed Shrock. RT #76791.
- The DateTime::TimeZone->names_in_category claimed that it returned names
based on the population of the zone. I don't think this was ever true, but
this data is definitely not part of the current Olson database. Reported by
Ed Shrock. RT #76792.
However, the DateTime::TimeZone->names_in_country method does preserve the
order specified in the Olson database, which is sort of based on population
and geography. This method is probably the best choice for presenting a list
of names to end user.
1.49 2012-09-13
- This release is based on version 2012f of the Olson database. This release
includes contemporary changes for Fiji.
1.48 2012-08-03
- This release is based on version 2012e of the Olson database. This release
includes contemporary changes for Fakaofo.
1.47 2012-07-19
- This release is based on version 2012d of the Olson database. This release
includes contemporary changes for Morocco.
libXext/buildlink3.mk, now that it is included there.
Leave the places where its API version is set or variables from it
are used directly (about 3 packages).
Changes in version 3.0
======================
API Change
----------
Since version we unified to icalendar de/serialization API to use only to_ical
(for writing an ical string from the internal representation) and from_ical
(for parsing an ical string into the internal representation).
to_ical is now used instead of the methods ical, string, as_string and instead
of string casting via __str__ and str.
from_ical is now used instead of from_string.
This change is a requirement for future Python 3 compatibility. Please update
your code to reflect to the new API.
Timezone support
----------------
Timezones are now fully supported in icalendar for serialization and
deserialization. We use the pytz library for timezone components of datetime
instances. The timezone identifiers must be valid pytz respectively Olson
database timezone identifiers. This can be a problem for 'GMT' identifiers,
which are not defined in the Olson database.
Instead of the own UTC tzinfo implementation we use pytz UTC tzinfo object now.
About this fork which is not a fork anymore
===========================================
Aim of this fork (not fork anymore, read further) was to bring this package up
to date with latest icalendar `RFC`_ specification as part of
`plone.app.event`_ project which goal is to bring recurrent evens to `Plone`_.
After some thoughts we (Plone developers involved with `plone.app.event`_) send
a suggestion to icalendar-dev@codespeak.net to take over mainaining of
`icalendar`_. Nobody object and since version 2.2 we are back to development.
.. _`icalendar`: http://pypi.python.org/pypi/icalendar
.. _`plone.app.event`: http://github.com/collective/plone.app.event
.. _`Plone`: http://plone.org
.. _`pytz`: http://pypi.python.org/pypi/pytz
.. _`setuptools`: http://pypi.python.org/pypi/setuptools
.. _`RFC`: http://www.ietf.org/rfc/rfc5545.txt
.. _`BSD`: https://github.com/collective/icalendar/issues/2
3.1
Make sure parameters to certain properties propagate to the
ical output. [kanarip]
Re-include doctests. [rnix]
endure correct datatype at instance creation time in prop.vCalAddress
and prop.vText. [rnix]
Apply TZID parameter to datetimes parsed from RECURRENCE-ID
[dbstovall]
Localize datetimes for timezones to avoid DST transition errors.
[dbstovall]
Allow UTC-OFFSET property value data types in seconds, which
follows RFC5545 specification. [nikolaeff]
Remove utctz and normalized_timezone methods to simplify the
codebase. The methods were too tiny to be useful and just used
at one place. [thet]
When using Component.add() to add icalendar properties, force
a value conversion to UTC for CREATED, DTSTART and LAST-MODIFIED.
The RFC expects UTC for those properties. [thet]
Removed last occurrences of old API (from_string). [Rembane]
Add
listing. For example when parsing a text/calendar text including
multiple components (e.g. a VCALENDAR with 5 VEVENTs), the
previous situation required us to look over all properties in
VEVENTs even if we just want the properties under the VCALENDAR
component (VERSION, PRODID, CALSCALE, METHOD). [dmikurube]
All unit tests fixed. [mikaelfrykholm]
3.0.1b2 (2012-03-01)
For all TZID parameters in DATE-TIME properties, use timezone
identifiers (e.g. Europe/Vienna) instead of timezone names
(e.g. CET), as required by RFC5545. Timezone names are used
together with timezone identifiers in the Timezone components.
[thet]
Timezone parsing, issues and test fixes. [mikaelfrykholm,
garbas, tgecho]
Since we use pytz for timezones, also use UTC tzinfo object
from the pytz library instead of own implementation. [thet]
3.0.1b1 (2012-02-24)
Update Release information. [thet]
3.0
Add API for proper Timezone support. Allow creating ical
DATE-TIME strings with timezone information from Python datetimes
with pytz based timezone information and vice versa. [thet]
Unify API to only use to_ical and from_ical and remove string
casting as a requirement for Python 3 compatibility: New:
to_ical. Old: ical, string, as_string and string casting via
__str__ and str. New: from_ical. Old: from_string. [thet]
1.9724nb1 to 1.9725.
upstream changes:
1.9725 [2012-02-01]
- Correct stack discipline in stat(), which was screwing up list
operations in expressions containing calls to it [rt.cpan.org
#72926].
- Add missing OUTPUT sections to the XS code [rt.cpan.org #70930].
- Skip itimer tests on GNU/Hurd, which has the API but lacks
the implementation [rt.cpan.org #72754].
- Fix a doubled word in the documentation [rt.cpan.org #72763].
version 2.03.2, 2012-06-26:
===========================
o [Compilation] Compatibility with OCaml 4
version 2.03.1, 2011-03-24:
===========================
* [Calendar] Fixed bug in Calendar.prev and Fcalendar.prev: mostly raised
exception Date.Out_of_bounds before.
* [Printer] `Thurday' was printed instead of `Thursday'
version 2.03, 2010-07-05:
=========================
o [Date] new function Date.precise_sub
o [Calendar] new function Calendar.precise_sub
(from Dario Teixeira's suggestion)
* [Compilation] detect whether native dynlink works
(prevents compilation bug on Mac OS X)
version 2.02, 2009-12-11:
=========================
o [License] add the usual Ocaml linking exception in the license
o [Calendar] Calendar_sig.Period.to_time is deprecated.
Replaced by a new function Calendar_sig.Period.safe_to_time
o [Date] Date.Period.nb_days is deprecated.
Replaced by a new function Date.Period.safe_nb_days
o [Compilation] calendarLib.cmxs provided if ocaml >= 3.11 is installed
(patch of Mehdi Dogguy)
o [Date] new functions Date.make_year and Date.make_year_month
o [Date] improve memory representation of Date.Period.t
* [Compilation] remove installation of packed *.cmi
* [Compilation] bug fixed under Cygwin
* [Compilation] META files was incorrect, so "ocamlfind ocamlopt" did not work
* [Compilation] file date_sig.mli, time_sig.mli and calendar_sig.mli was not
properly linked
version 2.01.1, 2009-02-23:
===========================
o [Date] add a missing coercion rule for months
(e.g. "Date.make 2008 18 1" is now equal to "Date.make 2009 6 1")
* [Date] bug fixed in date arithmetic operations due to the missing above
feature
version 2.01, 2009-01-26:
=========================
o [Printer] new formats available for printers and parsers
- %C century: as %Y without the two last digits
- %F replace %i which is now deprecated
- %P am or pm
- %R shortcut for %H:%M
- %s number of seconds since 1970/1/1
- %z time zone in the form +hhmm (from Warren Harris' suggestion)
- %:z time zone in the form +hh:mm (from Warren Harris' suggestion)
- %::z time zone in the form +hh:mm:ss (from Warren Harris' suggestion)
- %:::z time zone in the form +hh (from Warren Harris' suggestion)
o [Printer] new paddings available for printers
- 0 (zero): pad fields with zeroes like by default
- ^: use uppercase if possible
o [Compilation] calendarLib.cma and calendarLib.cmxa are now installed
(Janne Hellsten and Guillaume Yziquel's suggestion)
* [Tests] test suite now uses Utils.Float.equal if required
(patch of Richard Jones)
* [Compilation] small bug fixed in make install
* [Compilation] support of win64 (patch of David Allsopp)
time/p5-DateTime-Format-Strptime from 1.5000 to 1.5200.
pkgsrc changes:
- Update comment and homepage
- append 00 to upstream version to avoid comparing conflicts in pkgsrc
Upstream changes:
1.52 2012-07-01
- Shut up "unescaped braces in regex" warning from 5.17.0. RT #77514. Patch by
Zefram.
1.51 2012-05-27
- Packaging cleanup, including listing Test::More as a test prereq, not a
runtime prereq. RT #76128.
to 0.7600.
Upstream changes:
0.76 2012-07-01
- The DateTime->subtract method ignored the end_of_month parameter. Patch by
Chris Reinhardt. RT #77844.
0.75 2012-06-11
- The epoch for years 1-999 was broken because Time::Local is "clever". A pox
on all clever APIs, I say! Reported by Christian Hansen. RT #77719.
- Shut up compilation warning from 5.17.x. Reported by Tom Wyant. RT #77490.
Changes from 3.2.3 to 3.2.4
Fixed a possible double deallocation in the mxDateTime C API
import helper. Thanks to Daniele Varrazzo for reporting this.
Changes from 3.2.2 to 3.2.3
Fixed a possible segfault when using the .pydate(), .pydatetime()
and .pytime() methods. Thanks to Daniel Szoska for reporting
this.
Changes from 3.2.1 to 3.2.2
mxDateTime seconds rounding is now more careful to not show
60.00 or 61.00 as second value.
mxDateTime will now correctly work with numeric arrays (numpy)
again. Thanks to Christian Marquardt for reporting the problem.
mxDateTime's DateTimeFromAbsDateTime() now accepts leap second
values (86400.0 - <86401.0) as well. Thanks to Christian
Marquardt for reporting the problem.
mxDateTime range errors did not always format the wrong value.
Made mxDateTime compile again on Python 2.1 and 2.2.
Changes from 3.2.0 to 3.2.1
Fixed a segfault when comparing DateTime/DateTimeDelta with
None objects. Thanks to Mark Matthews for reporting this.
Changes from 3.1.2 to 3.2.0
Added new .rebuild() methods to both DateTime and DateTimeDelta
objects, making it easier creating new objects from existing
ones by just replacing some of the parameters (akin to the
mxURL .rebuild() method).
Greatly enhanced the interoperability with the Python datetime
module objects:
Added support for handling mixed type operations with
datetime.time objects.
Added new constructor methods to DateTime and DateTimeDelta
objects which aid in combining them with Python datetime
module objects: .pytime(), .pytimedelta(), .pydatetime()
and .pydate() as appropriate.
Added support for Python datetime module objects to the
generic mxDateTime constructors DateTimeFrom(), DateFrom(),
DateTimeDeltaFrom() (and their aliases).
The Python datetime module's C API is now loaded on demand
whenever mxDateTime needs to work with PyDateTime objects.
mxDateTime was updated to use mixed type number slots, a
feature which was added to Python in version 2.1 (by the
author of mxDateTime, Marc-André Lemburg). This has made
working with DateTime and DateTimeDelta objects and other
date/time types a lot more orbust.
mxDateTime's gmtime() now also works for ticks values beyond
2038 on 32-bit platforms that implement a POSIX confirm gmtime(),
but cannot handle post 2038 dates due to data type restrictions,
e.g. older 32-bit Linux platforms. As side-effect, this also
speeds up the gmtime() implementation on all platforms with
POSIX conform date/time handling.
mxDateTime will try to use the most accurate clock available
on the system for now(). For most POSIX systems, this is a
nanosecond resolution clock. A new global now_resolution allows
checking the resolution reported by the system. The performance
of now() was enhanced by directly interfacing to the various
platform C APIs.
Changed: mxDateTime will now format the seconds value in the
repr() and the str() output rounded to two decimal places. In
previous versions, it used to truncate the fraction after two
decimal places.
Known problem: mxDateTime doesn't build on FreeBSD with Python
2.7 and 2.7.1. This is a known problem with Python 2.7 and will
be fixed in Python 2.7.2. See http://bugs.python.org/issue10547
for details.
DateTimeFrom() now accepts a defaultdate parameter when parsing
strings or keyword-only arguments. defaultdate provides the
defaults to assume when pars of the date/time are not given.
It defaults to today().
DateFrom() will now only parse the date parts of a string and
only accept date-related keyword arguments.
Fixed a bug in the mxDateTime parser that triggered with some
ISO formats using second fractions. Thanks to Francesco
Pierfederici for bringing this to our attention.
Added support for more US AM/PM date formats such as "5:08pm"
(without space), "5:08 p.m." (with additional dots) to the
mxDateTime parser. Thanks to Tom at TicketStumbler for bringing
this to our attention.
Changed C API: mxDateTime now uses C longs for years internally
and in the C API. Note that the published C API has changed
because of this: mxDateTime.DateTime_FromDateAndTime() now
expects a long as year instead of an int. This change will
require a recompile of the applications using the mxDateTime
C API, but should only be noticeable on 64-bit platforms.
Added new C API DateTime_FromAbsDateTime to the mxDateTime C
API.
Added version number to C API object: Due to the changes in
the C API, the name of the C API object "mxDateTimeAPI" was
changed to "mxDateTimeAPI2", so that applications relying on
the old API don't import the changed API by accident.
Added optional calendar parameter to DateTimeFromAbsDateTime().
This allows creating DateTime instances with a given calendar.
Default is to use the Gregorian calendar.
Added BST to mx.DateTime.Timezone.
Fixed problem with now() resolution on Windows. It now provides
millisecond resolution again.
Fixed a bug in mx.DateTime.DateTimeFromAbsDateTime() which
caused an endless loop on 64-bit platforms for very large year
values.
Fixed Debian bug#494792: Incorrect subtraction with regular
Python datetime. This was actually a side-effect of the coercion
logic previously used in mxDateTime and not really a bug. The
new mixed type number slot implementations made it possible
to Darko Zurman for pointing this out.
Removed left-over debug code which caused the builtin strptime()
never to get used. Thanks to Alok Singhal for this one.
Fixed a bug in the mxDateTime .ticks() method which causes it
to raise an error for vahe Epoch.
xfce4-orage depends on x11/xfce4-panel which takes care of creating
the plugins directory. Remove the redundant directory creation which
can lead to directories being removed prematurely.
