On Sat, Apr 14, 2012 at 02:51, Victor Stinner wrote:
> Hi,
>
> Before posting a first draft of the PEP 418 to python-dev, I have some
> questions.
>
> == Naming: time.monotonic() or time.steady()? ==
The clock is monotonic by all reasonable definitions of monotonic (ie
they don't go backwards). T
Executive summary:
On naming, how about "CLOCK_METRONOMIC"? Also, "is_adjusted" is
better, until the API is expanded to provide "when and how much"
information about past adjustments.
On the glossary, (1) precision, accuracy, and resolution mean
different things for "points in time" and for "dur
Hi,
Before posting a first draft of the PEP 418 to python-dev, I have some
questions.
== Naming: time.monotonic() or time.steady()? ==
I like the "steady" name but different people complained that the
steady name should not be used if the function falls back to the
system clock or if the clock i
For those of you who had noticed that since the upgrade the tracker
search hasn't been returning a complete set of hits on typical searches,
this should now be fixed.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailma
By the way, I hesitate to add a new mandatory key to
time.get_clock_info() which indicates if the clock includes time
elapsed during a sleep. Is "is_realtime" a good name for such flag?
Examples:
time.get_clock_info('time')['is_realtime'] == True
time.get_clock_info('monotonic')['is_realtime'] ==
On Fri, 13 Apr 2012 18:29:10 +0200
Victor Stinner wrote:
> > The descriptions should really stress the scope of the result's
> > validity. My guess (or wish :-)) would be:
> >
> > - time.monotonic(): system-wide results, comparable from one process to
> > another
> > - time.perf_counter(): proces
bugs.python.org already sanitizes the ok_message and Ezio already posted
a patch to the upstream bug tracker, so I don’t see what else we could do.
Also note that the Firefox extension NoScript blocks the XSS in this case.
Regards
___
Python-Dev maili
On Fri, Apr 13, 2012 at 9:23 PM, anatoly techtonik wrote:
> Are there any good small Python libraries for making HTML safe out there?
>
> http://goo.gl/D6ag1
>
> Just to make sure that devs are aware of the problem, which was
> reported more than 6 months ago, gain some traction and release fix
>
Are there any good small Python libraries for making HTML safe out there?
http://goo.gl/D6ag1
Just to make sure that devs are aware of the problem, which was
reported more than 6 months ago, gain some traction and release fix
sooner. I am not sure what can you do with a stolen bugs.python.org
coo
On Fri, Apr 13, 2012 at 11:29, Victor Stinner
> I will move the precision of monotonic clock of Windows 9x info into this
> table.
I would just remove it entirely. It's not relevant since it's not supported.
___
Python-Dev mailing list
Python-Dev@python
> The descriptions should really stress the scope of the result's
> validity. My guess (or wish :-)) would be:
>
> - time.monotonic(): system-wide results, comparable from one process to
> another
> - time.perf_counter(): process-wide results, comparable from one thread
> to another (?)
> - time.
ACTIVITY SUMMARY (2012-04-06 - 2012-04-13)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open3377 (+17)
closed 22971 (+36)
total 26348 (+53)
Open issues wit
Hello,
I'm just starting a new thread since the old ones are so crowded.
First, overall I think the PEP is starting to look really good and
insightful! (congratulations to Victor)
I have a couple of comments, mostly small ones:
> "function" (str): name of the underlying operating system functio
On Wed, 11 Apr 2012 02:49:41 -0400
Jim Jewett wrote:
>
> Accuracy:
> Is the answer correct? Any clock will eventually ; if a
> clock is intended to match , it will need to be
> back to the "true" time.
You may also point to
http://en.wikipedia.org/wiki/Accuracy_and_precision
We are probab
14 matches
Mail list logo
