Message 75411 - 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	lemburg
Recipients	brett.cannon, catlee, erik.stephens, guettli, jribbens, lemburg, skip.montanaro, steve.roberts, tim.peters, tomster
Date	2008-10-31.10:23:44
SpamBayes Score	0.00014775165
Marked as misclassified	No
Message-id	<1225448626.65.0.0708004997729.issue1673409@psf.upfronthosting.co.za>
In-reply-to

Content
You can have all this by using the time module's functions. It is true that these don't work for all dates, but they are still useful to have. FWIW: mxDateTime has always had methods to convert the date/time values to ticks and back again: http://www.egenix.com/products/python/mxBase/mxDateTime/ Since most of the datetime module was inspired by mxDateTime, I wonder why these were left out.

You can have all this by using the time module's functions.

It is true that these don't work for all dates, but they are still
useful to have.

FWIW: mxDateTime has always had methods to convert the date/time values
to ticks and back again:

    http://www.egenix.com/products/python/mxBase/mxDateTime/

Since most of the datetime module was inspired by mxDateTime, I wonder
why these were left out.

History
Date	User	Action	Args
2008-10-31 10:23:46	lemburg	set	recipients: + lemburg, tim.peters, skip.montanaro, brett.cannon, jribbens, guettli, catlee, tomster, erik.stephens, steve.roberts
2008-10-31 10:23:46	lemburg	set	messageid: <1225448626.65.0.0708004997729.issue1673409@psf.upfronthosting.co.za>
2008-10-31 10:23:45	lemburg	link	issue1673409 messages
2008-10-31 10:23:44	lemburg	create