May-14-2024, 07:46 AM
(This post was last modified: May-14-2024, 08:03 AM by Gribouillis.)
It seems like the issue with the accept(*toktypes) function in IDLE might be related to the interactive nature of the IDLE environment, especially when considering how this function interacts with game app development.
When you define a function interactively in the game app environment, IDLE expects a complete function definition before it executes. The use of nonlocal might be causing confusion because it's used inside a function, which might not be fully supported in interactive mode within the Link Removed game app[/url].
When you define a function interactively in the game app environment, IDLE expects a complete function definition before it executes. The use of nonlocal might be causing confusion because it's used inside a function, which might not be fully supported in interactive mode within the Link Removed game app[/url].
Gribouillis write May-14-2024, 08:03 AM:
Clickbait link removed. Please read What to NOT include in a post
Clickbait link removed. Please read What to NOT include in a post