8000 Fail to switch remote "Wx" engine · Issue #872 · pyscripter/pyscripter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fail to switch remote "Wx" engine #872

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
tapdo opened this issue Apr 23, 2018 · 4 comments
Closed

Fail to switch remote "Wx" engine #872

tapdo opened this issue Apr 23, 2018 · 4 comments
Labels
fixed

Comments

@tapdo
Copy link
tapdo commented Apr 23, 2018 •
edited
Loading

"Wx" engine is not work.
When I sellect "remote (Wx)" from right crick menu on interpreter, the below message is shown.

[ Error ]
Could not connect to the remote Python engine server. The remote interpreter and debugger is not available.
[ Abort ]

My PyScritor is 3.3.2.0 x64 on Windows 7.
Python is 3.6.3 64bit, Wx version is 4.0.1 msw (phoenix).

In my memory, when Python 2.7 environment of some years ago , I can use wx engine...maybe.
Can anyone use Wx engine now?
@pyscripter
Copy link
Owner
pyscripter commented Apr 23, 2018 •
edited
Loading

I will have a look regarding wx 4 compatibility.
However let me say that you can still use the standard Remote engine to run or debug your wx scripts. The Tk and Wx python engines are specialised ones allowing you to interactively build and test GUI applications from the command prompt. They are not recommended for normal use.
Please see https://github.com/pyscripter/pyscripter/wiki/RemoteEngines for details

@tapdo
Copy link
Author
tapdo commented Apr 24, 2018

Yes, I use standard remote engine. However there is another problem. I attached tiny sample code.
Please run on standard remote engine, after that, Reinitialize engine. Then "PyScripter is waiting for the remote engine..." message is shown but cannot escape running state. So I should kill PyScritor process in this case.
I often use "Reinitialize engine" when my application hung-up especially multi-thread.

tiny_sample.zip

@pyscripter
Copy link
Owner

It works fine if you close the wxApp normally first.
The next version of PyScripter will allow you to Reinitialize without problems even without closing the wxApp. (it will "kill" the running wxApp). This has already been implemented.

@pyscripter
Copy link
Owner

Fixed in PyScripter 3.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pyscripter @tapdo
0