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 facundobatista
Recipients belopolsky, facundobatista, r.david.murray, tim.peters
Date 2014-07-24.20:12:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <53D168AE.60209@taniquetil.com.ar>
In-reply-to <1406224906.59.0.243618558365.issue22058@psf.upfronthosting.co.za>
Content
El 24/07/14 a las 15:01, Tim Peters escibió:

> "datetime.date() should accept a datetime.datetime as init
> parameter"
> 
> instead?  That's what the example appears to be getting at.
> 
> If so, -1.  Datetime objects already have .date(), .time(), and
> .timetz() methods to extract, respectively, the date, naive time, and

Ah, I wasn't aware of the .date() method.

I guess because it's more natural to me to do int(a_float) than
a_float.integer().

So, unless anyody wants to pursue with this, I'll close the issue.

Thanks!
History
Date User Action Args
2014-07-24 20:12:32facundobatistasetrecipients: + facundobatista, tim.peters, belopolsky, r.david.murray
2014-07-24 20:12:32facundobatistalinkissue22058 messages
2014-07-24 20:12:32facundobatistacreate