Evaluate vs Start/Continue button

retag add tags

I'm trying to help my daughter who just started a computer science class. I know the very basics of python but never used Wing-IDE.

Her instructions state to def a function and then hit the green play button. Then go to the Python shell and type the function to see the output. This doesn't work. She states she saw this happen in class. Work fine using the evaluate command. Am I missing something? Could they have remapped the school play buttons to run evaluate instead?

I think she's using Wing Personal or Wing Pro, while in class they were using Wing 101. In the latter, the green play button runs the code in the Python Shell. In the others, it starts the debugger which in the absence of a breakpoint or exception will just run to completion.

To get the same thing she was seeing in class in Wing Personal or Pro, she can use Evaluate File in Python Shell in the Source menu. To bind a key to that, use the User Interface > Keyboard > Custom Key Bindings preference and the command evaluate-file-in-shell.

Also, in Wing Pro you can set a breakpoint on the last line and run to that with the debugger and then interact with the module's contents in the Debug Probe. But it may be best to keep things simple!

Wingware Support

answered 2019-01-16 08:06:00 -0500

231

Wingware Admin

updated 2019-03-06 22:24:01 -0500

edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer

Evaluate vs Start/Continue button edit

Comments

1 Answer

Comments