On Sun, 13 Sep 2009, Vaclav Barta wrote:
On Saturday 12 September 2009 19:41:54 Dave Rolsky wrote:
Note that this release officially deprecates a lot of old methods. If you
are using (cough, Rick Measham ;) then please update your code.
We are many, :-) and looking at the POD, would it be
etzler. RT #41365.
Dave Rolsky
Compassionate Action for Animals - http://www.exploreveg.org/
VegGuide.Org - http://www.vegguide.org/
On Fri, 11 Sep 2009, Jim Monty wrote:
The CLDR has this:
  Â
http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/windows_tzid.html
And here is its XML source named supplementalData.xml:
  Â
http://unicode.org/repos/cldr/trunk/common/supplemental/supplementalData.xml
So it seem
http://www.nntp.perl.org/group/perl.cpan.testers/2009/09/msg5285650.html
Anyone care to take a stab at figuring that out?
-dave
/*
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg House Absolute
On Wed, 2 Sep 2009, Jonathan Leffler wrote:
As of both last night (2009-09-01T22:30-07:00) and this morning
(2009-09-02T11:15-07:00), the http://datetime.perl.org web site is not
responding.
Does anybody know why? Did I miss an announcement of its impending demise?
Doh, I forgot to get them t
0.952009-08-18
- Attempting to load an invalid Olson-style name like "Bad/Name" did throw
an error since 0.92. Reported by Florian Ragwitz.
- Localized $SIG{__DIE__} for every eval.
-dave
/*
http://VegGuide.org ht
0.942009-08-17
- This release is based on version 2009j of the Olson database. This
release has changes for Egypt.
- Localize $SIG{__DIE__} in DateTime::TimeZone::Local, so errors in evals
done
by that module are not seen by existing __DIE__ handlers. Based on a
patch
from Jim. RT #
On Tue, 14 Jul 2009, Rick Measham wrote:
This release depends on DateTime::Locale 0.43 and the locale tests expect the
data provided by that module. This isn't future-proof, but Dave says that the
methods that provide the %x, %X and %c patterns to strftime are deprecated.
Once the target stops
On Tue, 14 Jul 2009, Rick Measham wrote:
Dave Rolsky wrote:
All those methods that convert to strftime patterns are deprecated and will
go away in a future release, so even if I fixed this bug, if you're relying
on them, your code will break eventually.
Erm .. I'm confused.
On Mon, 13 Jul 2009, Metz, Bobby wrote:
I'm sorry all to reply to my own post. I should have read the
original message first before replying to Dave's message. I see that
the module I'm questioning is at the root of the issue, so my apologies
again.
As someone who uses DateTime::Format::
On Mon, 13 Jul 2009, Rick Measham wrote:
I believe there's an error in DateTime::Locale::Base that is screwing with my
fix. Line 277 turns the CLDR notation 'y' into the strftime notation '%y'.
From my reading of
http://www.unicode.org/reports/tr35/tr35-9.html#Date_Format_Patterns 'y'
should
[ please keep discussion on the datetime@perl.org list ]
On Mon, 6 Jul 2009, Luc St-Louis wrote:
Hi Dave,
I was trying to install DateTime::Format::Strptime this morning, but
tests were failing. I think I tracked it down to DateTime::Locale whose
generated files (like DateTime/Locale/en.pm) ap
On Thu, 2 Jul 2009, Vaclav Barta wrote:
Given that the stand-alone names are much less used, _and_ that they're
typically used for things like calendars, where you need to loop over them
anyway, I don't think it'd be that helpful to add an API to DateTime.pm
itself for them.
Well, perhaps not,
On Thu, 2 Jul 2009, Vaclav Barta wrote:
I'm using DateTime to generate calendars on my web page (e.g.
http://www.mangrove.cz/calendar/vb ), which is localized to Czech and English
(change your browser preferences if you want to see the two languages). The
heading of the calendar is currently tak
On Mon, 8 Jun 2009, Brian Hann wrote:
It's been a good long while since I've done any work on this, but I'm
gearing up to start again.
I don't think I heard any word back on whether the namespace choice
was kosher, so I guess this is the same query to the DateTime folks,
et al.
The namespace
On Sat, 30 May 2009, Steven Schubiger wrote:
DateTime::Format::Natural currently does calculate its dates and times
with an initial DateTime object received by "DateTime->now" (with timezone
support). As a consequence thereof, many resulting final DateTime objects
within DateTime::Format::Natura
On Wed, 29 Apr 2009, Mikko Lipasti wrote:
Tried to update FAQSimpleCalculations, got this error:
Should be fixed now.
-dave
/*
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg House Absolute(
On Wed, 29 Apr 2009, Dan Dascalescu wrote:
We've just released to CPAN a new version of MojoMojo, the Catalyst-based wiki.
I'd be more than happy to look into migrating the Kwiki content to
MojoMojo; all I need is a wiki dump.
And a host, since I don't have MojoMojo set up on my server.
Of c
On Fri, 24 Apr 2009, Metz, Bobby wrote:
I don't have need for a solution, but I agree with Shane's point.
It seems to me that "truncate-to-day" logically means the start of the
day which, due to DST rules, does not necessarily mean 00:00:00. The
later is a fallacy of non-DST thinking. So if
On Tue, 21 Apr 2009, Dan Dascalescu wrote:
http://datetime.perl.org/index.cgi?FAQSampleCalculations
I was wondering if you've looked into a more modern wiki for
datetime.perl.org... Kwiki is showing its age. formfu.org switched to
MojoMojo.
Yeah, Kwiki is rather gross. I'd love to upgrade, b
On Mon, 20 Apr 2009, Dan Dascalescu wrote:
This is the output I get when surfing to
http://datetime.perl.org/index.cgi?FAQSampleCalculations
Thanks, it's fixed.
I tried
http://web.archive.org/web/*/http://datetime.perl.org/index.cgi?FAQSampleCalculations
but robots.txt disallowed archiving.
On Tue, 7 Apr 2009, Terrence Brannon wrote:
Yes, I would determine that aribtrary 1 second or nanosecond based on
the data in my database tables. a MySQL BETWEEN clause includes its
endpoints.
Unfortunately, BETWEEN is kind of broken.
What people generally want is:
$x <= Column < $y
But un
On Thu, 2 Apr 2009, Olivier Mengué wrote:
2009/4/1 Gabor Szabo
Hi,
while installing Smolder I got a DateTime related error.
Michael Peters narrowed it down to the following call:
perl -MDateTime -le 'print DateTime->now(time_zone => q(local));'
which dies with the error:
Cannot determine
On Tue, 31 Mar 2009, Terrence Brannon wrote:
Intuitively, it would seem that specifying the 'before' of a datetime
span using the end option of the ->from_datetimes() constructor would
yield a range that is 1 second (1 nanosecond?) earlier than the actual
date supplied.
But as it is stands, the
0.862009-03-23
- This release is based on version 2009d of the Olson database. This
release has changes for Morocco, Tunisia, Syria, and Argentina.
There may be a 2009e shortly, though.
-dave
/*
http://VegGuide.org
0.852009-03-16
- This release is based on version 2009c of the Olson database. The
only changes in this release are for Cuba.
- Fixes for Win32 with Microsoft's December time zone update. This
updated added a zone for Mauritius that wasn't accounted for in the
DateTime::TimeZone::Local
On Thu, 12 Mar 2009, Bill Moseley wrote:
On Thu, Mar 12, 2009 at 02:28:34PM -0500, Dave Rolsky wrote:
On Thu, 12 Mar 2009, Bill Moseley wrote:
Is there a canonical approach, or is it something like:
$dt->add( days => 1 )->truncate( to => 'day' )->subtract( seconds =
On Thu, 12 Mar 2009, Bill Moseley wrote:
Is there a canonical approach, or is it something like:
$dt->add( days => 1 )->truncate( to => 'day' )->subtract( seconds => 1 );
That should work fine, _but_ if you're not in the floating timezone that
could land you on "second 60" every once in a wh
os Kollar.
0.46 2009-02-28
- Added a duration_class method for the benefit of DateTime.pm
subclasses. Patch by Shawn Moore.
Dave Rolsky
Compassionate Action for Animals - http://www.exploreveg.org/
VegGuide.Org - http://www.vegguide.org/
On Fri, 23 Jan 2009, arie.ha...@gmail.com wrote:
Why DateTime module is loaded so slow?
This simple script that just imports DateTime is executed for 1 second
approximately:
use DateTime;
Can I make it faster?
Yes, you need a faster computer!
auta...@houseabsolute:~/projects/R2$ time perl
0.842009-01-21
- This release is based on version 2009a of the Olson
database. Changes include spelling "Katmandu" as "Kathmandu" (with a
link for the old spelling), fixes for historical rules in
Switzerland, and changes to America/Resolute and Cuba for the past
few years (but not pre
On Tue, 20 Jan 2009, Eugene van der Pijll wrote:
Dave Rolsky schreef:
On Tue, 20 Jan 2009, Eugene van der Pijll wrote:
It may be useful if these kinds of lists were packaged and put on
CPAN; maybe I'll do that at some time.
If you generated this list programmatically, it'd be
On Tue, 20 Jan 2009, Eugene van der Pijll wrote:
It may be useful if these kinds of lists were packaged and put on
CPAN; maybe I'll do that at some time.
If you generated this list programmatically, it'd be better to include it
in DateTime::TimeZone, since the list of what's unique can change
On Wed, 14 Jan 2009, Alex Teslik wrote:
On Wed, 14 Jan 2009 18:40:50 +, Lyle wrote
Hi All,
I'm new to this list so please forgive me if I'm talking about
anything that have been previously covered.
http://www.nntp.perl.org/group/perl.datetime/2008/11/msg7116.html
Wrong answer.
DateTi
On Wed, 31 Dec 2008, skend...@fhcrc.org wrote:
how do i trouble-shoot this? conceptually, what is Thread::Running
doing to hammer DateTime's 'now' method?
guru> cat test
#!/usr/bin/perl
use DateTime;
use Thread::Running;
my $dt = DateTime->now( time_zone => 'local' );
guru> ./test
Could not
On Tue, 16 Dec 2008, Perrin Harkins wrote:
On Mon, Dec 15, 2008 at 8:29 PM, Alex Teslik wrote:
On Mon, 15 Dec 2008 20:04:26 -0500, Perrin Harkins wrote
my $d1 = DateTime->today;
my $d2 = $d1->clone->subtract(years => 1);
my $dur = $d1->delta_days($d2);
print $dur->in_units('days') . "\n";
On Sat, 22 Nov 2008, Daisuke Maki wrote:
I have an RFC/request for blessing for a module.
So my thought is go ahead, but can you call it DateTimeX::Lite?
Basically, I'm worried that people will expect your module to work just
like DateTime, but since they won't share a common code base going
On Wed, 26 Nov 2008, Daisuke Maki wrote:
Are you sure this is what you intended to do? (from r4116)
-sub quarter {$_[0]->{local_c}{quarter} };
-
I'm not sure what you're looking at. It's not in my diff, and the method's
still there (the tests would catch it if not).
-dave
/*=
On Mon, 24 Nov 2008, Avianna Chao wrote:
I've been using DateTime 0.41 quite happily for a while, but recently I
upgraded to 0.45, and am encountering a bug where if you do a epoch() on a DT
object that is quite sometime before epoch.
Fixed in 0.4501.
-dave
/*==
On Tue, 25 Nov 2008, Daisuke Maki wrote:
Yes, I wrote a crude benchmark script in
DateTime-Lite/tools/benchmar/load_times.pl
If you don't load arithmetic and strftime, DT::Lite is twice as fast plain
DT.
Rate dt dt_lite_full dt_lite
dt 46.6/s -
On Sat, 22 Nov 2008, Daisuke Maki wrote:
=item Non-essential methods are loaded on demand
A lot of times you don't even need to do date time arithmetic, for
example. These methods are separated out onto a different file, so you
need to load it on demand.
use DateTime::Lite qw(Arithmetic);
On Thu, 13 Nov 2008, Jim Monty wrote:
I just installed DateTime 0.45 on ActivePerl v5.8.8 using the
ActiveState Perl Package Manager rather than by compiling it myself. How
can be certain I'm using the XS version of DateTime and not the Pure
Perl version?
perl -MDateTime -le 'print $DateTim
0.45 2008-11-11
- Reverted the changes to use Time::y2038, on the recommendation of
Michael Schwern (the author of said module), because it is not yet
stable. This may come back in a future release.
/*
http://VegGuide.org
0.4401 2008-11-03
- In order to handle epochs > 2**32 properly on a 32-bit machine, we
also need to import gmtime from Time::y2038. This changes fixes a
whole bunch of test failures seen with 0.44.
-dave
/*
http://VegGuide.org
0.44 2008-11-01
- XS-capable DateTime.pm now uses Time::y2038 instead of
Time::Local. This lets it handle epochs up to 142 million years
before and after the Unix epoch.
- Fixed a compiler warning with Perl 5.10.0.
- Fixed docs for year_with_era, which had AD and BC
backwards. Reported
On Mon, 20 Oct 2008, Eugene van der Pijll wrote:
DateTime cannot handle fractional leap hours.
See the source code of subtract_datetime(), section "This is a gross
hack", where the length of the leap hour is hardcoded in the lines
$bigger_min -= 60
$bigger_min += 60
This should probably
0.822008-10-13
- This release is based on version 2008h of the Olson database. The
major changes in this release are for Mauritius and Syria.
/*
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg
0.812008-10-06
- This release is based on version 2008g of the Olson database. The
major changes in this release are for Brazil.
-dave
/*==
VegGuide.Org
Your guide to all that's veg
==*/
0.4305 2008-10-03
- The pure Perl version of this module did not know about the end of
2008 leap second. Reported by James T Monty.
-dave
/*==
VegGuide.Org
Your guide to all that's veg
==*/
On Wed, 1 Oct 2008, Zefram wrote:
So, anyway, most users don't need precise leap second handling. Many,
presumably, do need (approximate) calculations on times in the future
and before 1972. It is sensible for them that vague-regular-UT is
used in those eras. But they'd be better served by a
On Tue, 30 Sep 2008, Artem Novikov wrote:
Mistake in pod:
parse_datetime
---
# As a class method
my $datetime = DateTime::format::Excel->parse_datetime( 37680 );
must be
my $datetime = DateTime::Format::Excel->parse_datetime( 37680 );
This module really needs a new maint
On Mon, 15 Sep 2008, Dave Rolsky wrote:
0.802008-09-15
- This release is based on version 2008g of the Olson database. The
major changes in this release are for Mauritius, Morocco, Pakistan,
Argentina, and Brazil.
That should say "2008f"
0.802008-09-15
- This release is based on version 2008g of the Olson database. The
major changes in this release are for Mauritius, Morocco, Pakistan,
Argentina, and Brazil.
/*==
VegGuide.Org
Your guide to all that's veg
==*/
0.42 2008-09-12
- Based on CLDR 1.6.1, but this has no changes in the data we use. I
just used 1.6.1 so people wouldn't ask me why I don't use 1.6.1 ;)
- In the switch to CLDR (back in 0.30), I accidentally dropped a
number of hard-coded aliases, notably for 'C'. These aliases have
been
On Thu, 28 Aug 2008, Kristian Flint wrote:
So I take it you don't see any problem with producing this module? I'll
gladly look at the Dt::E::Ical before writing anything, I might just
post to the London.pm list to check if any of them can foresee any
problems in doing this.
More DateTime::Ev
0.7903 2008-08-22
- The DateTime::TimeZone->names_in_country() method was broken when
called as a method. Reported by Lars Eggert. RT #38665.
-dave
/*==
VegGuide.Org
Your guide to all that's veg
==*/
On Tue, 19 Aug 2008, Zefram wrote:
I can understand the arguments about EST, but if there's no ambiguity
about CET,
We just found an ambiguity about CET: does it include the DST rules?
Also, consider that your form of CET, with European-rules DST, is only
defined for 1977 and later (when the E
0.7901 2008-08-18
- This distro now provides the CET, EET, MET, and WET zones. These are
provided by the Olson database for backwards compatibility. It's
probably a bad idea to use them, but it's best if this package
matches what a Unix system provides.
- Moved the catalog to DateTime::Ti
On Mon, 18 Aug 2008, Eugene van der Pijll wrote:
Dave Rolsky schreef:
The problem is that CET could map to many, many different time zones
including Europe/Paris, Europe/Vienna, Europe/Tirane, and many more.
No, CET is unambiguously UTC +1, and therefore not equal to any of those
zones
On Mon, 18 Aug 2008, Dave Rolsky wrote:
I guess I could add them back. Whatever this Solaris box returns for CET
comes from the Olson database, so the sysadmin shouldn't be surprised by what
DT::TZ does either.
I just committed a change to include them. I realized that it's be
On Mon, 18 Aug 2008, Ton Voon wrote:
I can understand the arguments about EST, but if there's no ambiguity about
CET, would it be correct to add that in? I note that EST, MST and HST are
supported timezones: http://search.cpan.org/dist/DateTime-TimeZone/.
If it is just a case of adding CET in
0.792008-07-29
- This release is based on version 2008e of the Olson database. The
major changes in this release are for Mauritius and Central Europe
(historical changes only).
- Fixes for the local TZ tests on Win32. Thanks to David Pinkowitz for
pointing out my mistake.
Dave
On Mon, 28 Jul 2008, Dan Muey wrote:
Thanks for the feedback, I've replied inline below. Please let me know if you
have any other questions or suggestions.
On Jul 27, 2008, at 4:12 PM, Dave Rolsky wrote:
On Sun, 27 Jul 2008, Flavio S. Glock wrote:
re:
http://search.cpan.org/dist/Dat
On Sun, 27 Jul 2008, Flavio S. Glock wrote:
re:
http://search.cpan.org/dist/DateTime-Format-Span/
This module seems to handle durations, instead of spans.
How about naming it DateTime::Format::Duration instead?
Well, such a module already exists!
Daniel, Flavio raises a good point, though.
On Mon, 14 Jul 2008, David E. Wheeler wrote:
On Jul 12, 2008, at 07:47, Dave Rolsky wrote:
DateTime.pm
0.4303 2008-07-12
- There is a new leap second coming at the end of 2008.
FYI, I got locale failures when I tried to install this version before I
installed the latest DateTime::Locale
DateTime.pm
0.4303 2008-07-12
- There is a new leap second coming at the end of 2008.
DT::TZ
0.782008-07-12
- This release is based on version 2008d of the Olson database. The
major changes in this release are for Mauritius and Brazil (which
now has a new America/Santarem zone).
DT
On Sun, 6 Jul 2008, Jim Monty wrote:
CLDR 1.6 was released on 2008-07-02:
http://unicode.org/cldr/version/1.6.html
The current version of DateTime::Locale, version 0.4001, is based on
CLDR 1.5.1 (2007-12-21). I've noted in the past that Dave Rolsky keeps
DateTime::TimeZone remarkabl
On Thu, 19 Jun 2008, Jim Spath wrote:
I'm a bit unclear on how to properly deal with DST when determining the
number of seconds left in a day.
Here's what I have now:
my $now = DateTime->now(time_zone => 'local');
my $tom =
($dt + DateTime::Duration->new(days => 1))->truncate(to => 'day'));
0.77 2008-05-27
- This release is based on version 2008b of the Olson database. The
major changes in this release are for Morocco, Mongolia, and
Pakistan.
- More Windows changes from David Pinkowitz. Determining the local
time zone on a Win32 system should now work regardless of the
On Mon, 19 May 2008, Rick Measham wrote:
Dave Rolsky wrote:
However, it will break DateTime::Format::Strptime, apparently.
Paging Rick Measham ;)
Thanks for the work with Locales Dave, great to get all the available data in
there.
I'll look at strptime in the next couple of days u
On Sun, 18 May 2008, David E. Wheeler wrote:
On May 18, 2008, at 11:05, Dave Rolsky wrote:
- Added support for formatting the CLDR date pattern language, which
is much more powerful than strftime. This, combined with the latest
DateTime::Locale, makes the localized output much more correct
On Sun, 18 May 2008, Dave Rolsky wrote:
This is a pretty major release. I reworked the Locale generation code to
extract much more information from the CLDR xml data, and to do the
generation much more correctly.
I also added support for the CLDR date pattern language to DateTime.pm. This
This is a pretty major release. I reworked the Locale generation code to
extract much more information from the CLDR xml data, and to do the
generation much more correctly.
I also added support for the CLDR date pattern language to DateTime.pm.
This enables us to use the additional datetime fo
On Thu, 15 May 2008, David E. Wheeler wrote:
On May 14, 2008, at 16:49, Dave Rolsky wrote:
So the question is whether it's worth bothering with this. I'm kind of
tempted to just punt and simply display either a long TZ name,
abbreviation, or offset.
I think that's a reas
So I started looking into supporting the various formats provided by the
CLDR data, and promptly fell down a crazy rabbit hole.
It turns out that since I switched over to CLDR, DT::Locale has not been
handling the CLDR formats properly. While they're somewhat like Java
patterns, they're not
On Mon, 12 May 2008, Brian Hirt wrote:
it includes the year (which i do not want).Does anyone have any advice on
how to do this other than manually defining and maintaining 200 different
format strings outside of DateTime?If it is not possible to print a "day
month" string, is this som
David Pinkowitz. RT #35273.
Dave Rolsky
Compassionate Action for Animals - http://www.exploreveg.org/
VegGuide.Org - http://www.vegguide.org/
On Wed, 26 Mar 2008, Ewald Beekman wrote:
I never knew about the "clone" method and "is_dst" on itself is not available
as method inside DateTime::TimeZone
That's cause a timezone is a description of a historical set of changes
("-0700 until X date"). Without that date, it can't know if DST i
On Mon, 24 Mar 2008, William Heath wrote:
I am enjoying DateTime::TimeZone as usual. I have a unique need to be able
to somehow know all the countries, cities, and postal codes that are in a
certain TimeZone, can anyone recommend a way to do that?
_If_ you could get the geographic data descri
0.74 2008-03-24
- This release is based on version 2008b of the Olson database. The
major changes in this release are for San Luis in Argentina, Cuba,
Iraq, and Syria.
-dave
/*==
VegGuide.Org
Your guide to all that's veg
==*/
[Moving this to the datetime@perl.org list]
On Sat, 15 Mar 2008, Dan Muey wrote:
I've got this new module DateTime::Duration::Human to stringify a duration in
a localizable way.
This really isn't the right name. It should go under the DateTime::Format
namespace, since it's a way of formattin
On Tue, 6 Nov 2007, Antano Solar wrote:
Kindly also suggest another DateTime name space if you would prefer it to
be named anything else within the DateTime namespace.
I think either we should discuss the API first _or_ it should be renamed
out of the DateTime namespace. Folks are welcome to
On Fri, 14 Mar 2008, Dave Rolsky wrote:
On Fri, 14 Mar 2008, Jozef Kutej wrote:
I noticed you released a module DateTime::WorkingHours recently. I'd
prefer that folks not release modules under the DateTime namespace
without talking to the datetime@perl.org list about it first. In
parti
On Fri, 14 Mar 2008, Jozef Kutej wrote:
I noticed you released a module DateTime::WorkingHours recently. I'd
prefer that folks not release modules under the DateTime namespace
without talking to the datetime@perl.org list about it first. In
particular, the namespace you've chosen doesn't really
On Thu, 13 Mar 2008, Rick Measham wrote:
William Heath wrote:
I think I figured it out, what is important to understand is that you
can't choose EST, you must choose a country/city for the function to
adjust for DST automatically. My question was probably too simple for
you to give me this sol
On Wed, 12 Mar 2008, Rick Measham wrote:
printf( "%s%02d%02d",
$dt->offset >= 0 ? '+' : '-',
int($dt->offset / 60 / 60),
($dt->offset / 60) % 60
);
or better yet ...
print DateTime::TimeZone->offset_as_string($offset)
-dave
/*==
VegGuide.O
On Sat, 8 Mar 2008, Dave Rolsky wrote:
0.73 2007-03-08
- The DT::TZ::Local::VMS module declared its package as
DateTime::TimeZone::Local::Win32, which clearly is not
right. Patched by Peter Prymmer.
- This release is based on version 2007j of the Olson database. The
major changes in
0.73 2007-03-08
- The DT::TZ::Local::VMS module declared its package as
DateTime::TimeZone::Local::Win32, which clearly is not
right. Patched by Peter Prymmer.
- This release is based on version 2007j of the Olson database. The
major changes in this release are for Argentina and Chile,
0.09 2008-03-07
- The output of format_datetime() always includes the time
portion. Without this the module produced what I think was an
invalid iCal date. More importantly, this makes the output
consistent (always a DATE-TIME). Reported by Bill Moseley.
- removes RRULE: and EXRULE: fr
On Tue, 4 Mar 2008, Bill Moseley wrote:
I'm not very familiar with icalendar format.
http://search.cpan.org/src/DROLSKY/DateTime-Format-ICal-0.08/lib/DateTime/Format/ICal.pm
format_datetime() only adds the time if it's not 00:00:00:
my $base =
( $dt->hour || $dt->min || $dt->sec ?
On Wed, 20 Feb 2008, Dr.Ruud wrote:
Maybe add a "safe => 1" (with new, add, subtract) such that the
following don't die() anymore:
I'm not too keen on this, because it clutters up the API and puts too much
burden on the end user to know about the possibility of "unsafe" datetime
math.
Eith
On Sat, 19 Jan 2008, Steven Schubiger wrote:
As some of you might recall, DateTime::Format::Natural used to
ship with multiple language support (english and german), but back
then the entire concept was flawed (no functional tokeniser/lexer
combination) and some ugly workarounds were applied to
Well, I kind of missed it, as it was January 9th. I've been reading my old
use Perl journal posts and that led me to the post that basically started
the Perl DateTime project back in 2003 -
http://www.nntp.perl.org/group/perl.datetime/2003/01/msg388.html
Thanks to everyone who's contributed ov
0.72 2007-12-31
- This release is based on version 2007j of the Olson database. The
major changes in this release are for Argentinia.
/*===
VegGuide.Orgwww.BookIRead.com
Your guide to all that's veg. My book bl
I hate time zones ...
0.71 2007-12-28
- Fixes a major bug in the generation of time zone data. This bug
affected any time zone that has more than one rule (most of them)
and currently has no DST changes (many of them). An example would be
America/Caracas. The symptom would either be mi
On Fri, 28 Dec 2007, Éric Cholet wrote:
Hi,
I ran into the following problem with a specific datetime, and the Caracas
time zone:
my $d = DateTime->new(year => 2007, month => 12, day => 9, hour => 11, minute
=> 8, time_zone => 'UTC');
print "$d\n";
$d->set(locale => 'fr');
print "$d\n";
$d
On Mon, 3 Dec 2007, Zefram wrote:
Dave Rolsky wrote:
is one major change in this release, for the new Venezuelan time
zone.
What, again? I thought he'd've learned the first time.
Maybe it's the same one. This has been discussed for a few months but I
think it was only ma
Sometimes I wonder if Hugo Chavez is just a big Woody Allen fan ...
0.70 2007-12-03
- This release is based on version 2007j of the Olson database. There
is one major change in this release, for the new Venezuelan time
zone.
-dave
/*===
On Tue, 20 Nov 2007, Julien GILLES wrote:
btw, why there is no locale setter in DateTime ?
$dt->set( locale => ... );
or
$dt->set_locale(...);
-dave
/*===
VegGuide.Orgwww.BookIRead.com
Your guide to all that's veg.
On Wed, 7 Nov 2007, brian d foy wrote:
I usually ask the module authors to rename or withdraw modules, with
varying responses from "fuck you" to "ok, sure". I was thinking that it
might be good to encourage people to use DateTimeX to publish things that
use/produce/relate to DateTime modules bu
101 - 200 of 1439 matches
Mail list logo
