Message 144099 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	techtonik
Recipients	Alexander.Belopolsky, belopolsky, docs@python, shaq, techtonik
Date	2011-09-15.20:17:56
SpamBayes Score	3.8685238e-07
Marked as misclassified	No
Message-id	<CAPkN8xLvbJJgP6kz0PUOnCYCyp7PZmwd7nHo2Erd8MVAbg233w@mail.gmail.com>
In-reply-to	<CAP7h-xabbVra4mPxfDD8KubcYVtFxKG8yhtANV9LBv-oXqVfKw@mail.gmail.com>

Content
On Thu, Sep 15, 2011 at 10:42 PM, Alexander Belopolsky <report@bugs.python.org> wrote: > > Shouldn't we say "datetime and time" instead of "date and time"? > There is no tzinfo attribute in date objects. Does that mean that if aware `datetime` is converted to `date` and then back, the tzinfo information is lost and object implicitly becomes naive? In this case it should mentioned IMO. -- anatoly t.

On Thu, Sep 15, 2011 at 10:42 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
>
> Shouldn't we say "datetime and time" instead of "date and time"?
> There is no tzinfo attribute in date objects.

Does that mean that if aware `datetime` is converted to `date` and
then back, the tzinfo information is lost and object implicitly
becomes naive? In this case it should mentioned IMO.
--
anatoly t.

History
Date	User	Action	Args
2011-09-15 20:17:57	techtonik	set	recipients: + techtonik, belopolsky, Alexander.Belopolsky, docs@python, shaq
2011-09-15 20:17:56	techtonik	link	issue8822 messages
2011-09-15 20:17:56	techtonik	create