Where is time.strptime()?

[Tim Peters]

[Tim]
> ...
> IIRC, supplying strptime everywhere is already a feature request in
> PEP42.  That will happen if and when someone contributes unencumbered
> code+docs+tests to implement it.

[Gareth McCaughan]
> The copyright notice on the version of strptime in FreeBSD
> says:
>
>  * Copyright (c) 1994 Powerdog Industries.  All rights reserved.
>  *
>  * Redistribution and use in source and binary forms, with or without
>  * modification, are permitted provided that the following conditions
>  * are met:
>  * 1. Redistributions of source code must retain the above copyright
>  *    notice, this list of conditions and the following disclaimer.
>  * 2. Redistributions in binary form must reproduce the above copyright
>  *    notice, this list of conditions and the following disclaimer
>  *    in the documentation and/or other materials provided with the
>  *    distribution.
>  * 3. All advertising materials mentioning features or use of this
>  *    software must display the following acknowledgement:
>  *      This product includes software developed by Powerdog Industries.
>  * 4. The name of Powerdog Industries may not be used to endorse or
>  *    promote products derived from this software without specific prior
>  *    written permission.
>
> followed by the usual all-caps-to-make-sure-no-one-reads-it
> disclaimer of warranty.
>
> That looks sufficiently unencumbered to me. (Note that #3
> is not quite the usual-but-now-discarded BSD advertising
> clause.) Am I missing something?

+ Where are the docs?

+ Where's the test suite?

+ Does this compile and run correctly on all Python platforms?

+ Is this particular version of strptime "the correct" one (strptime isn't
available everywhere *now* because it's not part of ANSI C, so some
platforms don't supply it -- while those that do apparently don't always
agree on its input->output behavior)?

+ Clause 3 renders this license incompatible with the GPL (the Regents of
the U of CA have no authority to revoke such clauses in licenses other than
their own).

+ Is there a patch on SourceForge that addresses all of the above?

There are a lot of hoops to jump thru before code can be added to the std
Python distribution.  A raw piece of code is usually the least of it, but is
about the only part programmers volunteer without severe arm-twisting <0.6
wink>.

it-will-be-added-when-someone-cares-enough-to-twist-their-own-
    arm-ly y'rs  - tim