Re: conflict with Thread::Running
[email protected] (Stuart Kendrick)
| Newsgroups | perl.datetime |
|---|---|
| Message-ID | <[email protected]> |
hi dave, thanx for the insight. particularly, the pointer around identifying how 'supported' a module appears to be last nite, i finished retiring my use of Thread::Running, in favor of other 'thread' modules, thus side-stepping this 'load.pm' issue --sk Dave Rolsky wrote: > On Wed, 31 Dec 2008, [email protected] 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 find file for 'DateTime::TimeZone::Local::Unix' at /usr/lib/ >> perl >> 5/site_perl/5.8.8/load.pm line 256. > > Note this error message is coming from load.pm, which is _not_ being > used by DateTime. Apparently, this is something Thread::Running uses, > and it's apparently breaking module loading. > > I note that load.pm has one negative review about not installing or > working with Perl 5.8.7. It's been 18 months since the last release, and > nearly 3 years since the last Thread::Running release. > > My conclusion is that these modules are broken somehow, and not really > supported any longer. I'd suggest looking into fixing them, or exploring > an alternate solution. I know there are a number of actively maintained > thread-related solutions on CPAN. > > > -dave > > /*============================================================ > http://VegGuide.org http://blog.urth.org > Your guide to all that's veg House Absolute(ly Pointless) > ============================================================*/