Jim J. Jewett wrote:
> Passing strict as an argument seems like overkill since it will always
> be meaningless on some (most?) platforms.
A keyword argument that gets passed as a constant in the caller is
usually poor API. Why not have two different functions?
Neil
__
2012/3/20 Jim J. Jewett :
>
>
> In http://mail.python.org/pipermail/python-dev/2012-March/117762.html
> Georg Brandl posted:
>
>>> + If available, a monotonic clock is used. By default, if *strict* is
>>> False,
>>> + the function falls back to another clock if the monotonic clock failed
>>>
In http://mail.python.org/pipermail/python-dev/2012-March/117762.html
Georg Brandl posted:
>> + If available, a monotonic clock is used. By default, if *strict* is
>> False,
>> + the function falls back to another clock if the monotonic clock failed
>> or is
>> + not available. If *stric
