➜

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 petri.lehtinen
Recipients belopolsky, eric.smith, jbatista, joar, maker, petri.lehtinen, ronaldoussoren, thezulk
Date 2013-02-27.11:10:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20130227111104.GL13784@p29>
In-reply-to <1361961719.06.0.209731601235.issue17267@psf.upfronthosting.co.za>
Content 
A time object isn't associated with any date, so I don't really see a
problem here. The fact that you can shoot yourself in the leg can be
documented, noting that you should use datetime instead.

ISTM the reason why time objects even have an associated timezone is
to support easy calculations between times in different timezones.
History
Date User Action Args
2013-02-27 11:10:23petri.lehtinensetrecipients: + petri.lehtinen, ronaldoussoren, belopolsky, eric.smith, maker, thezulk, joar, jbatista
2013-02-27 11:10:23petri.lehtinenlinkissue17267 messages
2013-02-27 11:10:23petri.lehtinencreate