Catherine Devlin <fredv8vi...@liquidid.net> added the comment: > There is the non-zero cost of keeping two copies of that bit of > information in-sync with each other (and the code).
That's true, but how often do the strftime format codes change? I'd be happy to personally volunteer to keep them in synch. I suspect it would take me half an hour once or even twice per decade. > I believe the reason is that time.strftime behavior is platform dependent, so > "man strftime" is likely to produce more relevant documentation than "pydoc > time.strftime". So everything I've written with strftime is not cross-platform after all? Eek. Anyway, why couldn't the docstring do the same thing the Python docs do - report the ANSI codes, and mention that platform-specific variations are possible? Alternately, simply including a suggestion to ``man strftime`` in the docs would be a good start, since I had no idea about that (and I doubt I'm the only one). Of course, it's useless advice for Windows users. > Note the source at one of these sites: > "Source: Python’s strftime documentation." :-) Of course - the point is that people are feeling enough pain in drilling down to the right place in the Python documentation that a convenient designated URL seems attractive by comparison. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9650> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
