Python Library Reference, Chapter 6.9: 

strptime: Many (at least glibc 2) versions of strptime
can't parse the time zone (which strftime prints with
%Z). This should be mentioned as a warning in the
documentation.

Logged In: YES 
user_id=357491

I will add some note, but I don't know what yet.

Logged In: YES 
user_id=6656

Is 2.3 going to call the libc strptime?  If we keep using
Brett's, presumably this is irrelevant.

Logged In: YES 
user_id=357491

So, from what I remember when Guido switched off the libc usage to get 
more testing of _strptime Tim was in support of just moving completely over 
to _strptime while Guido seemed okay with it.  There was no final declaration 
that I know of (if there was then it was rather silly to leave in the libc wrapper 
code).

If _strptime does turn into the only implementation I will completely flesh 
out the docs on _strptime and its limitations (this is one of them; been 
debating whether it should be able to recognize UTC and GMT as timezones 
beyond the two the platforms tends to know).

Logged In: YES 
user_id=357491

OK, so it was agreed that _strptime will become the only implementation of 
time.strptime if no one gripes by the time 2.3b2 rolls around.  I will fix the 
docs when I rip out the old C code.

Logged In: YES 
user_id=357491

New docs checked in as revision 1.58 for the Doc/lib/libtime.tex .