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 vstinner
Recipients Alexander.Belopolsky, Neil Muller, amaury.forgeotdarc, andersjm, belopolsky, catlee, davidfraser, erik.stephens, guettli, hodgestar, jribbens, mark.dickinson, pitrou, srittau, steve.roberts, tebeka, tim.peters, tomster, vstinner, werneck
Date 2010-05-21.11:26:40
SpamBayes Score 0.05725152
Marked as misclassified No
Message-id <1274441201.95.0.480701545945.issue2736@psf.upfronthosting.co.za>
In-reply-to
Content
> As you explain in your own documentation, the proposed method 
> is equivalent to ``(time.mktime(self.timetuple()), self.microsecond)``,
> so all it does is replacing a less than a one-liner.

a one-liner, but an horrible one liner :-) I don't like mixing datetime and time modules. I prefer to use only datetime, I prefer its API.

>  ... If the tzinfo of the datetime object does not match the 
> system TZ used by mktime, the result will be quite misleading.

Can you suggest a possible fix to take care of the timezone information? I don't know how to use that.
History
Date User Action Args
2010-05-21 11:26:42vstinnersetrecipients: + vstinner, tim.peters, jribbens, srittau, guettli, amaury.forgeotdarc, tebeka, mark.dickinson, davidfraser, belopolsky, pitrou, andersjm, catlee, tomster, werneck, hodgestar, Neil Muller, erik.stephens, steve.roberts, Alexander.Belopolsky
2010-05-21 11:26:41vstinnersetmessageid: <1274441201.95.0.480701545945.issue2736@psf.upfronthosting.co.za>
2010-05-21 11:26:40vstinnerlinkissue2736 messages
2010-05-21 11:26:40vstinnercreate