2012/5/4 Victor Stinner :
> Anyway, the implementation and/or the documentation is buggy and
> should be fixed (especially the Windows case).
Done, I renamed "adjusted" to "adjustable", fixed its value on Windows
(time.time) and Linux (time.monotonic), and updated the doc.
--
changeset: 77415:0e
On Fri, May 4, 2012 at 10:12 AM, Cameron Simpson wrote:
> On 04May2012 01:47, Victor Stinner wrote:
> | I prefer "adjustable", because no OS tell us if the clock has an
> | ajustement or not... except Windows: see GetSystemTimeAdjustment().
> |
> http://msdn.microsoft.com/en-us/library/windows/d
> I'm -1 on that. To my mind "adjustable" suggests that the caller can
> adjust the clock, while "adjusted" suggests that the clock may be adjusted
> by a mechanism outside the caller's hands. That latter is the meaning
> in the context of the PEP.
Anyway, the implementation and/or the documentati
On 04May2012 01:47, Victor Stinner wrote:
| I prefer "adjustable", because no OS tell us if the clock has an
| ajustement or not... except Windows: see GetSystemTimeAdjustment().
|
http://msdn.microsoft.com/en-us/library/windows/desktop/ms724394%28v=vs.85%29.aspx
|
| I propose to rename is_adjus
> To me, "adjusted" and "is_adjusted" both imply that an adjustment
> has already been made; "adjustable" only implies that it is possible.
The documentation is:
"True if the clock can be adjusted (e.g. by a NTP daemon), False otherwise."
I prefer "adjustable", because no OS tell us if the clock
I've now renamed "is_monotonic" to "monotonic" and "is_adjusted" to "adjusted".
2012/4/29 Benjamin Peterson :
> Hi,
> I see PEP 418 gives time.clock_info() two boolean fields named
> "is_monotonic" and "is_adjusted". I think the "is_" is unnecessary and
> a bit ugly, and they could just be renamed
On 30Apr2012 09:26, Mark Shannon wrote:
| monotonic is an adjective,
Yes.
| whereas adjusted is (part of) a verb.
No. It is an adjective.
| I think
| both should be adjectives. Does "adjusted" mean that it has been
| adjusted, that it can be adjusted or it will be adjusted?
That depends on
On 29Apr2012 21:31, Benjamin Peterson wrote:
| 2012/4/29 Jim J. Jewett :
| > In http://mail.python.org/pipermail/python-dev/2012-April/119134.html
| > Benjamin Peterson wrote:
| >
| >> I see PEP 418 gives time.clock_info() two boolean fields named
| >> "is_monotonic" and "is_adjusted". I think the
Benjamin Peterson wrote:
2012/4/29 Jim J. Jewett :
In http://mail.python.org/pipermail/python-dev/2012-April/119134.html
Benjamin Peterson wrote:
I see PEP 418 gives time.clock_info() two boolean fields named
"is_monotonic" and "is_adjusted". I think the "is_" is unnecessary and
a bit ugly, a
2012/4/29 Jim J. Jewett :
>
>
> In http://mail.python.org/pipermail/python-dev/2012-April/119134.html
> Benjamin Peterson wrote:
>
>> I see PEP 418 gives time.clock_info() two boolean fields named
>> "is_monotonic" and "is_adjusted". I think the "is_" is unnecessary and
>> a bit ugly, and they coul
On Sun, 29 Apr 2012 19:25:16 -0400
Benjamin Peterson wrote:
> Hi,
> I see PEP 418 gives time.clock_info() two boolean fields named
> "is_monotonic" and "is_adjusted". I think the "is_" is unnecessary and
> a bit ugly, and they could just be renamed "monotonic" and "adjusted".
>
> Thoughts?
Agree
11 matches
Mail list logo
