Quote:
Originally Posted by wallcraft
I think the latter (not registered), or perhaps only registered for a particular user (i.e. not for the administrator).
|
For version 2 of the script I added error-checking for all the common cases I could think of, such as not activated, and for an unexpected error it will display the exception and stack trace in a text box one can easily copy-paste from. I literally cannot see any code path which would lead to the "no output at all" case Sydney's Mom is seeing.
Quote:
Originally Posted by JSWolf
There's no need to type anything other than adeptkey.pyw as Python sets up the association. I have my copy as adeptkey.py and that worked fine. Maybe it's the .pyw that is the problem?
|
The .pyw extension associates the script with a non-console version of the interpreter. I want to make certain this gets run with the
console version so that any uncaught exceptions will generate a stack trace in the console. Plus I'm not sure what's happened with SM's file associations as she seems to have installed multiple Python distros at some point. Just trying to control all variables.