Message226067
| Author |
vstinner |
| Recipients |
belopolsky, neologix, python-dev, vstinner |
| Date |
2014年08月29日.15:30:15 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1409326217.43.0.496818659461.issue22043@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ok, I prepared Python for monotonic clock, I attached an updated patch. It is now much simpler.
pymonotonic-3.patch:
* time.monotonic() is now always available
* _PyTime_Init() ensures that the operating system provides a monotonic clock and that the clock works
* Python 3.5 now requires a monotonic clock. All operating systems supported by Python 3.5 provides a monotonic clock. GNU Hurd doesn't, but it is not supported.
* drop try/except ImportError around "from time import monotonic"
* use a monotonic clock in _thread, gc and socket modules to compute elapsed time and timeouts |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年08月29日 15:30:17 | vstinner | set | recipients:
+ vstinner, belopolsky, neologix, python-dev |
| 2014年08月29日 15:30:17 | vstinner | set | messageid: <1409326217.43.0.496818659461.issue22043@psf.upfronthosting.co.za> |
| 2014年08月29日 15:30:17 | vstinner | link | issue22043 messages |
| 2014年08月29日 15:30:17 | vstinner | create |
|