[Python-Dev] Broken strptime in Python 2.3a1 & CVS

[Tim Peters]

[Tim]
>> I think we should lose the C version of strptime and use
>> _strptime.py everywhere now -- allowing x-platform accidents to
>> sneak thru is un-Pythonic (unless they're *valuable* x-platform
>> accidents <wink> -- strptime accidents are random crap).

[Guido]
> Guess what.  Through clever use of the time-machine, we *are* using
> _strptime.py everwhere now.  There's an #undef HAVE_STRPTIME in
> timemodule.c.

I know.  I want to delete the C wrapper too and get rid of HAVE_STRPTIME:
full steam ahead, no looking back.  This is pushing back against the growing
notion that the way to deal with legacy platform strptime quirks is to keep
an option open to recompile Python, to avoid using the portable code.  Since
that will be the easiest way out (one person here has already taken it),
we'll never get Python's own strptime story straight so long as it's an
option.