Changes between Version 15 and Version 16 of TracDev/ApiChanges/0.11

Timestamp:

Apr 21, 2007, 1:05:40 AM (17 years ago)

Author:

trac@…

Comment:

Remove redundant word

TracDev/ApiChanges/0.11

@@ -29 +29 @@
 More precisely, the database layer still uses `int` timestamps, but manipulation of time values is now done on `datetime` objects as soon as possible, see e.g. the [source:trunk/trac/Timeline.py Timeline] module.
 
-Those `datetime` values are directly added by the controllers to the data model, and it's the responsibility of the ''templates'' to pick up the appropriate time representation, using one of the built-in date formatting utilities: `format_date`, `format_datetime`, `format_datetime`, `http_date`, `pretty_timedelta` (see [source:trunk/trac/chrome.py chrome.py]), or even the `$dateinfo()` macro. 
+Those `datetime` values are directly added by the controllers to the data model, and it's the responsibility of the ''templates'' to pick up the appropriate time representation, using one of the built-in date formatting utilities: `format_date`, `format_datetime`, `http_date`, `pretty_timedelta` (see [source:trunk/trac/chrome.py chrome.py]), or even the `$dateinfo()` macro. 
 
 Those utilities automatically take into account the ''timezone'' information set by the user, so that the dates are presented in a meaningful way to him.