Re: date.timezone E_WARNING -- Really necessary? What's the rationale?

From: Date: Wed, 28 Aug 2013 09:08:20 +0000
Subject: Re: date.timezone E_WARNING -- Really necessary? What's the rationale?
References: 1  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Thu, May 23, 2013 at 8:40 PM, Daniel Lowrey <[email protected]> wrote:

> I'm probably not the typical PHP user; I spend 99% of my PHP time
> using the CLI (and not web SAPIs).
> This means that I frequently run PHP without an .ini file. As a
> result, when I use any of the date/time
> functionality I invariably end up with this awesomeness:
>
> > Warning: date(): It is not safe to rely on the system's timezone
> settings blah blah blah.
>

I was thinking about this again and maybe we could reach the following
compromise:

 * Set date.timezone = UTC as the default INI value
 * In php.ini-production and php.ini-development uncomment the
       ;date.timezone =
   line, i.e. change it to
       date.timezone =

This would mean that people running PHP without an ini would get UTC as the
default and people running with an ini based on
php.ini-production/php.ini-development would get the warning.

Short of completely dropping the warning this is the behavior that would
make most sense to me. (As people running without an ini obviously don't
care about setting the timezone)

Thanks,
Nikita


Thread (70 messages)

« previous php.internals (#68632) next »