Revision history [back]
I think the problem is that you need to upgrade to the latest Wing 5.1 and then apply all patches from the Help menu. Python 3.5 changed its byte code version mid-stream for some reason and this broke things.
Or, better yet, use Wing 6 which has a different way the debugger works internally that avoids this kind of Python version compatibility problem.
Sorry, somehow we did not receive notice of this post 22 days ago (or at all).
I think the problem is that you need to upgrade to the latest Wing 5.1 and then apply all patches from the Help menu. Python 3.5 changed its byte code version mid-stream for some reason and this broke things.
Or, better yet, use Wing 6 which has a different way the debugger works internally that avoids this kind of Python version compatibility problem.
Sorry, somehow we did not receive notice of this post 22 days ago (or at all).
I all).I think the problem is that you need to upgrade to the latest Wing 5.1 and then apply all patches from the Help menu. Python 3.5 changed its byte code version mid-stream for some reason and this broke things.
Or, things.Or, better yet, use Wing 6 which has a different way the debugger works internally that avoids this kind of Python version compatibility problem.