RetroSearch Browse

Tue Jul 28 07:27:52 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/141040.html

On 07/27/2015 10:08 PM, Lennart Regebro wrote:
> On Tue, Jul 28, 2015 at 12:11 AM, Ronald Oussoren wrote:

>> It might be nice to have time zone aware datetime objects with the right(TM)
>>  semantics, but those can and should not replace the naive objects we know
>>  and love.
>
> Yes, they most certainly should.
> I will try to shut up now, but let me be clear on that the time zone
> support as it stands now is intentionally broken. Not naive, *broken*.
> All the usecases people have here for supporting "naive" objects would
> work just as well if they actually used naive objects, ie datetimes
> with no timezone info. If you explicitly do NOT want the
> datetimeobject to care about timezones, then you should not add a
> timezone to the object.

Lennart, are you saying you would leave naive objects alone, and "fix" the tz-aware objects only?

--
~Ethan~

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/141040.html below:

[Python-Dev] Status on PEP-431 Timezones