[Skip Montanaro]
> ...
> * Is strptime even the right name for it? I doubt it. Only
> us C-heads would think that was a good name.
Given that we're stuck with strftime for date->string, strptime for
string->date is better than just about anything else ('f' for 'format', 'p'
for 'parse').
> * If you create a strptime (or timeparse or parsedate) module
> should it really have exposed functions named julianFirst,
> julianToGreg or gregToJulian?
No, and definitely not at first. Stick to the original request and this
will be sooooo much easier to resolve. As you put it earlier,
All PEP 42 asked for was
Add a portable implementation of time.strptime() that works in
clearly defined ways on all platforms.
Cool! Let's do just that much to start, and don't take it as "a reason" to
rename the time module either (it really is trivial to add another .py file
to Lib! give the name a leading underscore if you want to imply it's a
helper for something else).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4