[issue41309] test_subprocess.test_pause_reading timing out randomly on Windows

Steve Dower added the comment: Assuming this is fixed -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44153] Signaling an asyncio subprocess raises ProcessLookupError, depending on timing

New submission from Max Marrone : # Summary Basic use of `asyncio.subprocess.Process.terminate()` can raise a `ProcessLookupError`, depending on the timing of the subprocess's exit. I assume (but haven't checked) that this problem extends to `.kill()` and `.send_signal()`. This breaks

[issue41309] test_subprocess.test_pause_reading timing out randomly on Windows

Change by Steve Dower : -- title: test_subprocess timing out randomly on Windows -> test_subprocess.test_pause_reading timing out randomly on Windows ___ Python tracker <https://bugs.python.org/issu

[issue41309] test_subprocess timing out randomly on Windows

Change by Steve Dower : -- keywords: +patch pull_requests: +20638 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21495 ___ Python tracker ___

[issue41309] test_subprocess timing out randomly on Windows

lib\test\libregrtest\main.py", line 717 in main File "D:\a\1\s\lib\test\__main__.py", line 2 in File "D:\a\1\s\lib\runpy.py", line 87 in _run_code File "D:\a\1\s\lib\runpy.py", line 197 in _run_module_as_main ##[error]Cmd.exe exited w

Re: execution timing of the method QWidget.show()

Search for PyQt mailing list will get you to https://www.riverbankcomputing.com/mailman/listinfo/pyqt Barry > On 8 Jul 2020, at 21:17, artis.pain...@gmail.com wrote: > > I might be wrong but since I have not found anygroup newsgroup dedicated to > PyQt5. > > My small program is expected to

Re: execution timing of the method QWidget.show()

On 2020-07-08 21:11, artis.pain...@gmail.com wrote: I might be wrong but since I have not found anygroup newsgroup dedicated to PyQt5. My small program is expected to show a window GUI for 4 seconds before changing it, so I naively coded: "... ... # codes to set up the GUI ... F0.show() # F0

execution timing of the method QWidget.show()

I might be wrong but since I have not found anygroup newsgroup dedicated to PyQt5. My small program is expected to show a window GUI for 4 seconds before changing it, so I naively coded: "... ... # codes to set up the GUI ... F0.show() # F0 being a QMainWindow object time.sleep(4) ... # codes

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Terry J. Reedy added the comment: Raymond, I finished the backporting and assume that your patch was meant to be a complete fix. -- nosy: +terry.reedy versions: +Python 3.9 ___ Python tracker

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue40197] Add nanoseconds to timing table in What's new python 3.8

miss-islington added the comment: New changeset 1bf7dee8d35cb19db7ee98229dd2e5726e6c7606 by Miss Islington (bot) in branch '3.8': bpo-40197: Better describe the benchmark results table (GH-19386) https://github.com/python/cpython/commit/1bf7dee8d35cb19db7ee98229dd2e5726e6c7606 --

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Change by miss-islington : -- pull_requests: +18818 pull_request: https://github.com/python/cpython/pull/19462 ___ Python tracker ___

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Morten Hels added the comment: It turns out I was wrong about microseconds. The output in https://bugs.python.org/issue35884 does show microseconds, but the output is before this commit https://github.com/python/cpython/commit/9da3583e78603a81b1839e17a420079f734a75b0 that fixes a typo

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Change by miss-islington : -- pull_requests: +18751 pull_request: https://github.com/python/cpython/pull/19388 ___ Python tracker ___

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Raymond Hettinger added the comment: New changeset c63629e7c09da80a6b7d0253d04a9b3f57f88eff by Raymond Hettinger in branch 'master': bpo-40197: Better describe the benchmark results table (GH-19386) https://github.com/python/cpython/commit/c63629e7c09da80a6b7d0253d04a9b3f57f88eff

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +18750 pull_request: https://github.com/python/cpython/pull/19387 ___ Python tracker

[issue40197] Add nanoseconds to timing table in What's new python 3.8

Change by Raymond Hettinger : -- title: Add microseconds to timing table in What's new python 3.8 -> Add nanoseconds to timing table in What's new python 3.8 ___ Python tracker <https://bugs.python.org/issu

[issue40197] Add microseconds to timing table in What's new python 3.8

Change by Raymond Hettinger : -- keywords: +patch pull_requests: +18749 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19386 ___ Python tracker

[issue40197] Add microseconds to timing table in What's new python 3.8

Change by STINNER Victor : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list

[issue40197] Add microseconds to timing table in What's new python 3.8

New submission from Morten Hels : It is not immediately obvious to me what the units are in the timing table here: https://docs.python.org/3/whatsnew/3.8.html#demos-and-tools Clicking through to https://bugs.python.org/issue35884 shows that the unit is microseconds, but I think it would

Re: Timing problem?

On Fri, Mar 22, 2019 at 1:01 AM Steve wrote: > > I believe I can see what is happening here but maybe someone can explain > least I run into this again. > > Situation 1: I am using "ws.MessageBeep(1)" to generate a tone through the > speakers. I wanted two tones to separate it from other tones

Timing problem?

I believe I can see what is happening here but maybe someone can explain least I run into this again. Situation 1: I am using "ws.MessageBeep(1)" to generate a tone through the speakers. I wanted two tones to separate it from other tones that might happen and placed that code a second time in

MIDI note timing

I'd like to do some algorithmic composing using python. I've seen various libraries that seem to be capable of sending a MIDI message to a MIDI port, but I don't know where to get the timing from. Normally, with something like CSOUND, the program locks itself to the timing of the soundcard

Midi output timing?

I'd like to use a python program to send out MIDI events to another program. I've done in the past by generating scores for csound which would do the MIDI output. The apparent hurdle is the timing bit. I've seen packages that allow the creation of MIDI events, but given a list of events

[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: Thanks Martin for your change, I commited it. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22875 ___

[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: Oops, I forgot to mention the issue number in my commit. changeset: 93893:a59fed8c710b branch: 3.4 parent: 93891:1da9e9eaeae8 user:Victor Stinner victor.stin...@gmail.com date:Mon Dec 15 17:50:55 2014 +0100 files:

[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: FYI I added a new test to the aiotest project (test suite for asyncio), for this issue: https://bitbucket.org/haypo/aiotest/commits/17dd11fc2f4bafad623f940b1a33a3b8b0d39ccd -- ___ Python tracker

[issue22875] asyncio: call_soon() documentation unclear on timing

Guido van Rossum added the comment: Docfix LGTM. On Fri, Dec 12, 2014 at 10:53 PM, Martin Panter rep...@bugs.python.org wrote: Martin Panter added the comment: I have been bitten by this when attempting to implement my own event loops. Parts of the “asyncio” code itself expects that the

[issue22875] asyncio: call_soon() documentation unclear on timing

Martin Panter added the comment: I have been bitten by this when attempting to implement my own event loops. Parts of the “asyncio” code itself expects that the callback is not invoked directly after call_soon() returns. Here is a simple patch. -- keywords: +patch nosy: +vadmium

[issue22875] asyncio: call_soon() documentation unclear on timing

, yselivanov priority: normal severity: normal status: open title: asyncio: call_soon() documentation unclear on timing ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22875

[issue22875] asyncio: call_soon() documentation unclear on timing

Guido van Rossum added the comment: As soon as possible is constrained by all callbacks are called from the event loop. Feel free to suggest a doc patch (asyncio docs are in dire need of more help!) -- ___ Python tracker rep...@bugs.python.org

[issue22875] asyncio: call_soon() documentation unclear on timing

R. David Murray added the comment: Personally, when I read that I thought arrange for made it pretty clear it was when control returned to the event loop, but I agree that if it can be made clearer it should be. -- nosy: +r.david.murray ___ Python

[issue19371] timing test too tight

Changes by Ezio Melotti ezio.melo...@gmail.com: -- stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___

[issue19371] timing test too tight

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___ ___ Python-bugs-list

[issue19371] timing test too tight

Changes by Guido van Rossum gu...@python.org: -- resolution: - duplicate superseder: - test_asyncio: test__run_once timings should be relaxed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371

[issue19371] timing test too tight

Ezio Melotti added the comment: Also this should use assertAlmostEqual(). -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___

[issue19371] timing test too tight

New submission from Antoine Pitrou: Looks like test_asyncio still has rather tight timing expectations: http://buildbot.python.org/all/builders/x86%20Windows%20Server%202008%20%5BSB%5D%203.x/builds/1495/steps/test/logs/stdio

Re: timing issue: shutil.rmtree and os.makedirs

of the traceback; when I run it a second time (immediately after the first time), it runs fine. That's why I thought it was a timing issue. I thought about just putting a sleep in there, but that made me feel dirty. hmm, now that you mention it, this is executing on a remote box with access

Re: timing issue: shutil.rmtree and os.makedirs

On Tue, Jul 30, 2013 at 2:10 PM, Tim jtim.arn...@gmail.com wrote: hmm, now that you mention it, this is executing on a remote box with access to the same file system my local calling program is on. That is, there is a local call to an intermediate script that connects to a socket on the

Re: timing issue: shutil.rmtree and os.makedirs

On Tue, 30 Jul 2013 14:27:10 +0100, Chris Angelico wrote: for delay in 100,300,600,1000,3000,5000,1: if not os.path.exists(directory): break sleep(delay) That'll sleep a maximum of 20 seconds, tune as required. Actually, that will sleep a maximum of 5.55 hours, and a minimum of 1.7

Re: timing issue: shutil.rmtree and os.makedirs

On Tue, Jul 30, 2013 at 3:07 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: On Tue, 30 Jul 2013 14:27:10 +0100, Chris Angelico wrote: for delay in 100,300,600,1000,3000,5000,1: if not os.path.exists(directory): break sleep(delay) That'll sleep a maximum of 20

Re: timing issue: shutil.rmtree and os.makedirs

On Tuesday, July 30, 2013 9:27:10 AM UTC-4, Chris Angelico wrote: On Tue, Jul 30, 2013 at 2:10 PM, Tim wrote: hmm, now that you mention it, this is executing on a remote box with access to the same file system my local calling program is on. That is, there is a local call to an

Re: timing issue: shutil.rmtree and os.makedirs

On Tue, Jul 30, 2013 at 4:37 PM, Tim jtim.arn...@gmail.com wrote: Argg, this isn't the first time I've had troubles with the file system. This is FreeBSD and NFS. I will code up a progressive delay as you mentioned (with Steve's correction). I've used several different networked file

Re: timing issue: shutil.rmtree and os.makedirs

On Jul 30, 2013 3:29 PM, Chris Angelico ros...@gmail.com wrote: On Tue, Jul 30, 2013 at 2:10 PM, Tim jtim.arn...@gmail.com wrote: hmm, now that you mention it, this is executing on a remote box with access to the same file system my local calling program is on. That is, there is a local call

timing issue: shutil.rmtree and os.makedirs

I have the following function (Python2.7 on FreeBSD) that results in an OSError. My intent is to pass it a directory name or path and if it exists, use shutil.rmtree to remove whatever is there (if it isn't a directory, try to unlink it); then use os.makedirs to create a new directory or path:

Re: timing issue: shutil.rmtree and os.makedirs

On Mon, Jul 29, 2013 at 8:16 PM, Tim jtim.arn...@gmail.com wrote: My intent is to pass it a directory name or path and if it exists, use shutil.rmtree to remove whatever is there (if it isn't a directory, try to unlink it); then use os.makedirs to create a new directory or path: def

Timing of string membership (was Re: hex dump w/ or w/out utf-8 chars)

On Sun, Jul 14, 2013 at 11:44 PM, wxjmfa...@gmail.com wrote: Le dimanche 14 juillet 2013 12:44:12 UTC+2, Steven D'Aprano a écrit : On Sun, 14 Jul 2013 01:20:33 -0700, wxjmfauth wrote: For a very simple reason, the latin-1 block: considered and accepted today as beeing a Unicode design

Re: Timing of string membership (was Re: hex dump w/ or w/out utf-8 chars)

On 7/14/2013 10:56 AM, Chris Angelico wrote: On Sun, Jul 14, 2013 at 11:44 PM, wxjmfa...@gmail.com wrote: timeit.repeat(a = 'hundred'; 'x' in a) [0.11785943134991479, 0.09850454944486256, 0.09761604599423179] timeit.repeat(a = 'hundreœ'; 'x' in a) [0.23955250303158593, 0.2195812612416752,

Re: Timing of string membership (was Re: hex dump w/ or w/out utf-8 chars)

On Mon, Jul 15, 2013 at 2:18 PM, Terry Reedy tjre...@udel.edu wrote: On 7/14/2013 10:56 AM, Chris Angelico wrote: As issue about finding stings in strings was opened last September and, as reported on this list, fixes were applied about last March. As I remember, some but not all of the

Re: Installation of yappi (timing module)

On 24-Aug-2012 12:28, Virgil Stokes wrote: I have been doing some experiments with different modules for the timing of functions and code segments. One module I would like to test is yappi (thread aware timer) which is listed at PyPI. However, I have been unable to install it on Windows Vista

Installation of yappi (timing module)

I have been doing some experiments with different modules for the timing of functions and code segments. One module I would like to test is yappi (thread aware timer) which is listed at PyPI. However, I have been unable to install it on Windows Vista and Windows 7 (Python 2.7 on both). I have

Spacing and timing for comparing algorithms and data-structures

What would you recommend I use to compare data-structures and algorithms on space and time? (runtime) Thanks for all suggestions, Alec Taylor -- http://mail.python.org/mailman/listinfo/python-list

Re: Spacing and timing for comparing algorithms and data-structures

On Thu, Mar 1, 2012 at 8:55 PM, Alec Taylor alec.tayl...@gmail.com wrote: What would you recommend I use to compare data-structures and algorithms on space and time? (runtime) For the latter metric, one of the profiling modules: http://docs.python.org/library/debug.html I'd start with timeit

Re: Comparisons of computation timing

Akand Islam wrote: I have run my codes (written in Python) in my Notebook (3 GB Ram, Dual- core CPU T4500 @ 2.3 GHz) and in my lab machine (11.57 GB Ram, i7-920 CPU @ 2.67 GHz). However, I have found execution time in Notebook 250.3 seconds, and in Lab machine 333.2 seconds. How is it

Re: Comparisons of computation timing

About the codes: Basically it simply solves some non-linear equations using fsolve along with some other calculations. Looks like you are using some third party libraries like numpy/scipy. Do these libraries have the same version on both platforms? What about python interpreter versions - are

Comparisons of computation timing

I have run my codes (written in Python) in my Notebook (3 GB Ram, Dual- core CPU T4500 @ 2.3 GHz) and in my lab machine (11.57 GB Ram, i7-920 CPU @ 2.67 GHz). However, I have found execution time in Notebook 250.3 seconds, and in Lab machine 333.2 seconds. How is it possible? Good configuration

Re: List comprehension timing difference.

MRAB pyt...@mrabarnett.plus.com writes: On 02/09/2011 01:35, Bart Kastermans wrote: graph = [[a,b] for a in data for b in data if d(a,b) ==1 and a b] graph2 = [] for i in range (0, len(data)): for j in range(0,len(data)): if d(data[i],data[j]) == 1 and i j:

Re: List comprehension timing difference.

On Sep 2, 9:54 am, Bart Kastermans bkast...@gmail.com wrote: if d(a,b) == 1 and a b: It will probably be faster if you reverse the evaluation order of that expression. if ab and d(a,b)==1: That way the d() function is called less than half the time. Of course this assumes that ab is a faster

Re: List comprehension timing difference.

t...@thsu.org writes: On Sep 2, 9:54 am, Bart Kastermans bkast...@gmail.com wrote: if d(a,b) == 1 and a b: It will probably be faster if you reverse the evaluation order of that expression. if ab and d(a,b)==1: That way the d() function is called less than half the time. Of course this

List comprehension timing difference.

(281 seconds VS 305 seconds on my dell mini). Is the right interpretation of this timing difference that the comprehension is performed in the lower level C code? As this time I have no other conjecture about the cause. - import time import

Re: List comprehension timing difference.

, the list comprehension is faster though (281 seconds VS 305 seconds on my dell mini). Is the right interpretation of this timing difference that the comprehension is performed in the lower level C code? As this time I have no other conjecture about the cause

Re: multiprocessing timing issue

On 8/10/2011 11:36 PM, Philip Semanchuk wrote: On Aug 9, 2011, at 1:07 PM, Tim Arnold wrote: Hi, I'm having problems with an empty Queue using multiprocessing. The task: I have a bunch of chapters that I want to gather data on individually and then update a report database with the results.

Re: multiprocessing timing issue

On Aug 9, 2011, at 1:07 PM, Tim Arnold wrote: Hi, I'm having problems with an empty Queue using multiprocessing. The task: I have a bunch of chapters that I want to gather data on individually and then update a report database with the results. I'm using multiprocessing to do the

Re: multiprocessing timing issue

Tim Arnold tim.arn...@sas.com wrote: The task: I have a bunch of chapters that I want to gather data on individually and then update a report database with the results. I'm using multiprocessing to do the data-gathering simultaneously. Each chapter report gets put on a Queue in their separate

multiprocessing timing issue

Hi, I'm having problems with an empty Queue using multiprocessing. The task: I have a bunch of chapters that I want to gather data on individually and then update a report database with the results. I'm using multiprocessing to do the data-gathering simultaneously. Each chapter report gets

wxpython 2.8 -- timing and latency issues when displaying widgets

Dear all, in an application window (subwindow of a Notebook-control) I'm trying to do the following: 1. Create a StaticText control kind of Please wait until processing has finished 2. Do some processing (e.g. vacuuming an sqlite database) 3. Create a 2nd StaticText control with the

Re: timing

You could use pycallgraph module Regards, Alex Abushkevich -- http://mail.python.org/mailman/listinfo/python-list

timing

Hello: If I want to calculate the runtime of a section of a program. How can I do it? Thank you, Jia -- http://mail.python.org/mailman/listinfo/python-list

Re: timing

On Fri, Jul 16, 2010 at 5:52 PM, Jia Hu huji...@gmail.com wrote: Hello: If I want to calculate the runtime of a section of a program. How can I do it? Taking you extremely literally: from time import time start = time() run_section_here() end = time() runtime = end-start Assuming you're

Re: timing

Thank you, it is so straightforward. On Fri, Jul 16, 2010 at 9:58 PM, Chris Rebert c...@rebertia.com wrote: On Fri, Jul 16, 2010 at 5:52 PM, Jia Hu huji...@gmail.com wrote: Hello: If I want to calculate the runtime of a section of a program. How can I do it? Taking you extremely

Socket packet timing on Windows 2000

hi *Tim Janick,* I encountered same problem, did you ever get some resolution? Brent Jiang, -- http://mail.python.org/mailman/listinfo/python-list

[issue1252001] Issue with telnetlib read_until not timing out

Jack Diederich jackd...@gmail.com added the comment: This was fixed in r47215 -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1252001 ___

[issue1252001] Issue with telnetlib read_until not timing out

Jack Diederich jackd...@gmail.com added the comment: assigning all open telnetlib items to myself -- assignee: - jackdied nosy: +jackdied ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1252001

[issue1252001] Issue with telnetlib read_until not timing out

Changes by Daniel Diniz aja...@gmail.com: -- dependencies: +Issue with telnetlib read_until not timing out ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1252001

[issue1252001] Issue with telnetlib read_until not timing out

Changes by Daniel Diniz aja...@gmail.com: -- dependencies: +telnetlib expect() and read_until() do not time out properly -Issue with telnetlib read_until not timing out ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1252001

[issue1252001] Issue with telnetlib read_until not timing out

Changes by Daniel Diniz aja...@gmail.com: -- stage: - test needed type: - behavior versions: +Python 2.6 -Python 2.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1252001 ___

Re: Managing timing in Python calls

Interesting stuff - I hadn't come across the 'with' syntax before, so I've learned something already. I was briefly excited to learn about the callLater command which is just a convenience class for the wxTimer class. It seems to be pretty much a parallel of the var t = window.setTimeout(

Re: Python music sequencer timing problems

), which from the sound of it also applies to your requirement - IOW, you _can_ use it just to start notes at the right time, because the note-playing loop sleeps till then. And as I realized after having a good sleep myself, this is only useful for timing events which occur sequentially and do

Managing timing in Python calls

I'm porting some ugly javascript managed stuff to have an equivalent behaviour in a standalone app. It uses events that arrive from a server, and various small images. In this standalone version, the data is local in a file and the images in a local directory. My AJAX code managed a timely

Re: Managing timing in Python calls

On 15 Dic, 16:21, Ross nos...@forme.thks wrote: I'm porting some ugly javascript managed stuff to have an equivalent behaviour in a standalone app. It uses events that arrive from a server, and various small images.  In this standalone version, the data is local in a file and the images in a

Re: Managing timing in Python calls

bieff...@gmail.com wrote: Python has in its standard library a timer class which actually is implemented as a thread (I think) ... however, when using a GUI package, I think it is better to use gui- specific functions for event-driven programming, to make sure that your code do not mess with

Re: Managing timing in Python calls

I believe WxTimerEvent is handled using the event queue, which isn't going to do what you want. An event which goes through the queue does not get processed until you return to the queue. What you want to do is actually a rather difficult task to do generically. Should the task be interrupted

Re: Python music sequencer timing problems

John O'Hagan wrote: On Wed, 10 Dec 2008, badmuthahubbard wrote: I've been trying to get the timing right for a music sequencer using Tkinter. First I just loaded the Csound API module and ran a Csound engine in its own performance thread. The score timing was good, being controlled

Re: Python music sequencer timing problems

On Sun, 14 Dec 2008, Bad Mutha Hubbard wrote: John O'Hagan wrote: On Wed, 10 Dec 2008, badmuthahubbard wrote: [...] from time import time, sleep start = time() for event in music: duration=len(event) #Really, the length of the event play(event) while 1: timer

Python music sequencer timing problems

I've been trying to get the timing right for a music sequencer using Tkinter. First I just loaded the Csound API module and ran a Csound engine in its own performance thread. The score timing was good, being controlled internally by Csound, but any time I moved the mouse I got audio dropouts

Re: Python music sequencer timing problems

On Wed, 10 Dec 2008, badmuthahubbard wrote: I've been trying to get the timing right for a music sequencer using Tkinter. First I just loaded the Csound API module and ran a Csound engine in its own performance thread. The score timing was good, being controlled internally by Csound, but any

[issue4255] timing module refers to non-existent documentation

New submission from Steven D'Aprano [EMAIL PROTECTED]: import timing help(timing) = MODULE DOCS http://www.python.org/doc/current/lib/module-timing.html but there doesn't appear to be any such page: the URL gives Error 404: File Not Found. Searching the reference library for timing

[issue4255] timing module refers to non-existent documentation

Andrii V. Mishkovskyi [EMAIL PROTECTED] added the comment: Well, it's listed in Undocumented modules: http://docs.python.org/library/undoc.html#obsolete so I wouldn't call this a bug. -- nosy: +mishok13 ___ Python tracker [EMAIL PROTECTED]

[issue4255] timing module refers to non-existent documentation

Benjamin Peterson [EMAIL PROTECTED] added the comment: Agreed. This is a deprecated module and is gone in Python 3.0. -- nosy: +benjamin.peterson resolution: - wont fix status: open - closed ___ Python tracker [EMAIL PROTECTED]

Re: Interesting timing issue I noticed

En Tue, 15 Apr 2008 23:24:01 -0300, Jonathan Shao [EMAIL PROTECTED] escribió: I've written up a stripped down version of the code. I apologize for the bad coding; I am in a bit of a hurry. First things first: I think you will gain inmensely using NumPy: http://numpy.scipy.org/ My

Interesting timing issue I noticed

*Gabriel Genellina* gagsl-py2 at yahoo.com.ar python-list%40python.org?Subject=Interesting%20timing%20issue%20I%20noticedIn-Reply-To= *Wed Apr 16 08:44:10 CEST 2008* Another thing would be to rearrange the loops so the outer one executes less times; if you know that borderXsizeX and borderYsizeY

Re: Interesting timing issue I noticed

En Wed, 16 Apr 2008 10:36:14 -0300, Jonathan Shao [EMAIL PROTECTED] escribió: *Gabriel Genellina* gagsl-py2 at yahoo.com.ar python-list%40python.org?Subject=Interesting%20timing%20issue%20I%20noticedIn-Reply-To= *Wed Apr 16 08:44:10 CEST 2008* Another thing would be to rearrange the loops so

Re: Interesting timing issue I noticed

On Wed, Apr 16, 2008 at 2:54 PM, Gabriel Genellina [EMAIL PROTECTED] wrote: En Wed, 16 Apr 2008 10:36:14 -0300, Jonathan Shao [EMAIL PROTECTED] escribió: *Gabriel Genellina* gagsl-py2 at yahoo.com.ar python-list%40python.org?Subject=Interesting%20timing%20issue%20I%20noticedIn-Reply-To=

Re: Interesting timing issue I noticed

I've written up a stripped down version of the code. I apologize for the bad coding; I am in a bit of a hurry. import random import sys import time sizeX = 320 sizeY = 240 borderX = 20 borderY = 20 # generates a zero matrix def generate_zero(): matrix = [[0 for y in range(sizeY)] for x in

Re: Interesting timing issue I noticed

two inside = 0.062362396 time two outside = 0.125 Why is a large percentage of the time, the execution time for the (ostensibly smaller) first loop is actually equal to or LARGER than the second? First of all, your method of timing is not the best. Use the timeit module instead: http

Re: Interesting timing issue I noticed

= 0.1876376 time two inside = 0.062362396 time two outside = 0.125 Why is a large percentage of the time, the execution time for the (ostensibly smaller) first loop is actually equal to or LARGER than the second? First of all, your method of timing is not the best. Use the timeit

Re: Interesting timing issue I noticed

of the time, the execution time for the (ostensibly smaller) first loop is actually equal to or LARGER than the second? First of all, your method of timing is not the best. Use the timeit module instead: http://docs.python.org/lib/module-timeit.html Second of all the number

Interesting timing issue I noticed

The project I'm working on is motion detection, involving a bit of image processing. No worries: no image processing background needed. Suffice to say that I initially wrote a script that goes through every pixel of a 320x240 picture (turned into an array using PIL) and performs some

Re: Interesting timing issue I noticed

The project I'm working on is motion detection, involving a bit of image processing. No worries: no image processing background needed. Suffice to say that I initially wrote a script that goes through every pixel of a 320x240 picture (turned into an array using PIL) and performs some

Re: Unexpected timing results with file I/O

It doesn't matter how many doors opening and closing there are, it matters the order in which the opening, walking through, and closing are done. That's my point. In the second example, all of the disk operations are done at the same time. That's what I meant by people going through the doors.

  1   2   >