Message162270
| Author |
barry |
| Recipients |
Alexander.Belopolsky, barry, belopolsky, djc, lemburg |
| Date |
2012年06月04日.16:12:43 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20120604121234.25889a57@limelight.wooz.org> |
| In-reply-to |
<CAP7h-xZkz7KSU01J5_kYLYThoSdM9dDDiUzi5efxht=4R9J20w@mail.gmail.com> |
| Content |
On Jun 04, 2012, at 04:03 PM, Alexander Belopolsky wrote:
>That's a valuable experience. How big of a deal was the lack of
>.ticks() and .gmticks()? How did you work around it?
It was *much* less of an issue than all the magic date format parsing that
mxDT supports. That's actually something that I think is a more serious
deficiency, since .strptime() is pretty limited (e.g. how would you parse ISO
8601 dates both with and without the 'T'?). A Python 3 compatible time format
parser would make for a very nice separate library (PyPI) and/or addition to
the stdlib (eventually).
FWIW, here's the changeset.
http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/revision/1354 |
|