Alexander Belopolsky email@example.com added the comment:
On Tue, Jan 11, 2011 at 1:56 PM, Georg Brandl firstname.lastname@example.org wrote: ..
It seems to me that the quoted function from bzr ... would be very helpful to add to the `time` module docs as an example.
The problem with this function is the same as with the doc patches that have been proposed so far. It is subtly wrong. See issue #1647654. Specifically, see the link to a bug in Hg mentioned in msg122166.
I have to agree with the OP that the current state of the docs is not as clear as it could be.
In some ways the state of the docs is reflective of the state of the code. C/POSIX API on which time module design is based is not very well suited to the age of smart phones and distributed VC systems. The whole idea that there is a static "system timezone" is absurd when a "system" is in your pocket or in the cloud.
I agree that the docs can be improved, but I don't see patches that would constitute an improvement. I've explained what I would see as an improvement in my prior comments.