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 skip.montanaro
Recipients brett.cannon, eric.smith, skip.montanaro
Date 2007-09-17.13:50:09
SpamBayes Score 0.013905391
Marked as misclassified No
Message-id <1190037009.62.0.710295247678.issue1158@psf.upfronthosting.co.za>
In-reply-to
Content
Brett,

Continuing the discussion of strptime... It returns a time.struct_time.
Would it cause too much breakage (only do this in 3.0) to add a tm_usec
field to the end of that object?  It seems a lot of bits of code might
still expect a length 9 tuple-ish thing and do this:

  yy, mm, dd, hh, mm, ss, wk, j, tz = time.strptime(...)

If we could make that change for 3.0 that might allow strptime to parse
%f format codes.

S
History
Date User Action Args
2007-09-17 13:50:09skip.montanarosetspambayes_score: 0.0139054 -> 0.013905391
recipients: + skip.montanaro, brett.cannon, eric.smith
2007-09-17 13:50:09skip.montanarosetspambayes_score: 0.0139054 -> 0.0139054
messageid: <1190037009.62.0.710295247678.issue1158@psf.upfronthosting.co.za>
2007-09-17 13:50:09skip.montanarolinkissue1158 messages
2007-09-17 13:50:09skip.montanarocreate