[Python-Dev] Broken strptime in Python 2.3a1 & CVS (original) (raw)

Tim Peters tim.one@comcast.net
Tue, 14 Jan 2003 08:47:58 -0500

[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 -- 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 HAVESTRPTIME 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.