buggy python interpretter or am I missing something here?
me
noone at all.net
Mon Jan 27 02:30:06 EST 2014
On Sun, 26 Jan 2014 23:12:18 -0800, Gary Herron wrote:
> On 01/26/2014 10:46 PM, me wrote:
>> In any case, thanks for the answers guys. I'm satisfied that the
>> except:
>> syntax yields undefined behavior, and in my mind it shouldn't be
>> syntactically allowed then.
>>
>> Updating to Exception,e or Exception as e fixes the problem.
>>
>>
> That's an irksome habit you have there, this jumping to (incorrect)
> conclusions so quickly. We'd like to get to the bottom of this. (And
> correct your mis-interpretations while we're at it :-) But we need to
> see your test *and* the results.
>
> Gary Herron
Problem solved. I understand what was happening now with the "raise"
following the bare except:
Since this code is for a personal research project I'm not as concerned
about code quality as I would be if I was getting paid to write
production code...and if it was production code I'd only prototype a
proof-of-concept in python and then rewrite in c++.
The project is to take advantage of all 16 CPU cores to process A LOT of
GPS data for a 3d map-making and visualization project. Now my
bottleneck may end up being the python global lock when doing concurrent
processing...but we'll see.
More information about the Python-list
mailing list