On 12/03/2012 10:28 PM, Chris Angelico wrote:
> On Tue, Dec 4, 2012 at 1:28 PM, Dave Angel wrote:
>> On 12/03/2012 03:33 PM, Chris Angelico wrote:
>>>
>>> Is it possible that the error actually came from further up (with a
>>> faulty line number) and was actually because communicate() somehow
>>>
On Tue, Dec 4, 2012 at 1:28 PM, Dave Angel wrote:
> On 12/03/2012 03:33 PM, Chris Angelico wrote:
>>
>> Is it possible that the error actually came from further up (with a
>> faulty line number) and was actually because communicate() somehow
>> returned an empty list? That's the only place in the
On 12/03/2012 03:33 PM, Chris Angelico wrote:
>
> Is it possible that the error actually came from further up (with a
> faulty line number) and was actually because communicate() somehow
> returned an empty list? That's the only place in the code quoted that
> I'm seeing indexing, but communicate(
On Tue, Dec 4, 2012 at 4:37 AM, wrote:
> Traceback (most recent call last):
> File "./Connection_Monitor.py", line 146, in
> Google_up, Google_summary, Google_RTT, Google_stddev =
> Google.connection_test()
> File
> "/Users/wrw/Dev/Python/Connection_Monitor/Version2.2/WorkingCopy/netwo
On Dec 3, 2012, at 1:27 PM, Ian Kelly wrote:
> On Mon, Dec 3, 2012 at 10:37 AM, wrote:
> if found_0 == True or found_1 == True:
>
> Not related to your problem, but this line would be more pythonic as:
>
> if found_0 or found_1:
>
Thanks Ian - yes, Steven pointed out the same th
On Dec 3, 2012, at 1:12 PM, Steven D'Aprano
wrote:
> On Mon, 03 Dec 2012 12:37:42 -0500, wrw wrote:
>
>> So far in my experience with Python, it's error messages have been
>> clear, concise, and quite good at fingering my errors. However, the
>> message below has me stumped. The routine in qu
On Mon, Dec 3, 2012 at 10:37 AM, wrote:
> if found_0 == True or found_1 == True:
>
Not related to your problem, but this line would be more pythonic as:
if found_0 or found_1:
My puzzle two-fold. First: how could that code generate an "index our of
> range" error, and second: lin
On Mon, 03 Dec 2012 12:37:42 -0500, wrw wrote:
> So far in my experience with Python, it's error messages have been
> clear, concise, and quite good at fingering my errors. However, the
> message below has me stumped. The routine in question has been running
> for weeks with no problems, then ye
