Traceback (most recent call last): File "Mattricks\Main.pyc", line 289, in OnFetch File "Mattricks\Main.pyc", line 361, in __do_fetch File "Mattricks\Main.pyc", line 334, in __new_xmls File "Mattricks\Playerlist.pyc", line 445, in ChangeXML File "Mattricks\Playerlist.pyc", line 336, in UpdateColumns File "Mattricks\Playerlist.pyc", line 218, in PopulateList File "Mattricks\MatchInfo.pyc", line 342, in __init__ File "Mattricks\MatchInfo.pyc", line 457, in __extract_data KeyError: 44385156
Oscar Gustafsson wrote:
A new release seems closer and closer...
Can I ask something (potentially) stupid?
As far as I knew earlier, Python was sort of same as the other P-languages (perl, php, pike and so on) which meant that it would handle error conditions better than C for instance, because it would be a higher level language. Still, whenever it crashes for me on windows, it almost always leaves an app that won't respond and which I have to use the OS to kill afterwards.
Is it something you do in Mattricks (perhaps the wxstuff or something) or is it Python that makes it hang so "hard"?
Usually most interpreted languages handle errors far better and have the interpreter put up some error dialog and then more or less gracefully exit, but this app (which is one of the few python apps I do use on win) seems to be very hard to exit in a nice way.
No offense meant, just curious.
On Wed, 17 Nov 2004, Janne Johansson wrote:
Can I ask something (potentially) stupid?
Yes!
Is it something you do in Mattricks (perhaps the wxstuff or something) or is it Python that makes it hang so "hard"?
You are right (afaIk). I think it has to do with the wxstuff, causing the event loop to stop/hang. Sometimes Mattricks crashes gracefully (popping up the error dialog, allowing you to continue afterwards), sometimes it crashes hard. I haven't really looked into it, but I would expect this to be the reason.
And it wasn't a stupid question!
/Oscar
ons 2004-11-17 klockan 13.14 skrev Janne Johansson:
Oscar Gustafsson wrote:
A new release seems closer and closer...
Can I ask something (potentially) stupid?
Of course, those are most often the best questions. ;)
As far as I knew earlier, Python was sort of same as the other P-languages (perl, php, pike and so on) which meant that it would handle error conditions better than C for instance, because it would be a higher level language. Still, whenever it crashes for me on windows, it almost always leaves an app that won't respond and which I have to use the OS to kill afterwards.
That is unfortunate. It shouldn't happen ideally.
Is it something you do in Mattricks (perhaps the wxstuff or something) or is it Python that makes it hang so "hard"?
I think it's a combination of Mattricks and wx. Python does have very good exception handling. Unfortunately, we have a tendency to not use it to it's full potential.
Usually most interpreted languages handle errors far better and have the interpreter put up some error dialog and then more or less gracefully exit, but this app (which is one of the few python apps I do use on win) seems to be very hard to exit in a nice way.
That indeed is the intended behaviour. Any suggestions on how to improve our handling of exceptions are very welcome.
No offense meant, just curious.
No offense taken.
/Ragnar
mattricks@lists.lysator.liu.se
-
Janne Johansson -
Oscar Gustafsson -
Ragnar Ouchterlony -
Ulf Lagerholm