Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-June/015604.html below:

[Python-Dev] collecting timer resolution information...

• Previous message: [Python-Dev] collecting timer resolution information...
• Next message: [Python-Dev] latest unicode-related change causes failure in test_unicode & test_unicodedata
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Neil Schemenauer writes:
 > I've got it at 1024.
 > 
 >     >>> 976. / 10000 * 1024
 >     99.942400000000006
 > 
 > I think yours is at the 100 default.

  That's correct.  Yours could be bumped a bit (factor of 10?  I'm not
really sure where it would cause problems in practice, though I think
I understand the general explanations I've seen), and mine could be
bumped a good bit.  But I intend to stick with a stock kernel since I
expect most users will be using a stock kernel, and I don't have a
pile of extra machines to play with.  ;-(


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Digital Creations

• Previous message: [Python-Dev] collecting timer resolution information...
• Next message: [Python-Dev] latest unicode-related change causes failure in test_unicode & test_unicodedata
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4