[SOLVED] Pyscripter - Unable to connect to remote Python engine

[mviale]

Good morning,

I get an error message every time I launch pyscripteur stating that "connection to the remote Python engine failed. The remote process console and debugger are not accessible."

I am on enterprise version 2.0.0.9428.
I installed pyscripteur via the package available on the WAPT self-service, version 4.0.
I already have:

• Uninstall/delete the pyscripteur folder in %appdata%/reinstall: same result

• Check that the "Always use sockets" box in the IDE options is checked.

• and check the following lines in pyscripteur.local.ini:

[PythonVersions-x86\Custom Versions]
Path0=Python 3.8 (32bit)=C:\Program Files (x86)\wapt
Count=1

[PythonVersions-x86]
InstallPath=C:\Program Files (x86)\wapt

Does anyone have any ideas?

Mathieu

[mviale]

The problem is solved...

Comparing it to another machine, the Python paths in Pyscripteur (Tools -> Python path) weren't identical.
I also didn't have the same files in C:\Program Files (x86)\wapt\Scripts.

So I uninstalled Pyscripteur, the Wapt agent, and the Wapt console, then reinstalled everything, and it works.

Mathieu

[lfkl]

Hello,

I have the same problem, however your procedure did not allow me to solve it.

Furthermore, when I add the missing paths in PyScripter (Tools -> Python paths), after comparing them to a machine where it works correctly, they disappear...

Is there a configuration file where I can save them permanently?

Thank you for your help, sincerely.

[t.heroult]

Same problem, I can't get PyScripter 4 to work.

A little help would be greatly appreciated!

[Gaetan]

Hello,

the issue is fixed in version 2.1.2.10652.

[t.heroult]

Absolutely not, it's not fixed with the latest version.

I have this problem on almost every machine where I try to install PyScripter 4.
I'm on Windows 10, and that's already the agent version installed on all the machines.

[Gaetan]

Hello,

you need to use pyscripter3.

The best option is to use the waptdev package: https://wapt.tranquil.it/store/tis-waptdev

[t.heroult]

Yes, I confirm, I ended up going back to version 3. There are too many problems with 4.0 or 4.1.1.
Even when the Python engine is running, autocompletion isn't always available. When it is, there's also something strange happening when generating the package:
- Package generation: signature OK
- After generation and before requesting credentials for upload, a message appears saying there's a problem with the "CONTROL" file, which is open (indeed, it's open in PyScripter). So you have to close the "CONTROL" file before exporting.
That said, despite the two windows it opens saying something's wrong, it still works; the package is created and sent correctly.

Anyway! PyScripter 3 still has a bright future ahead of it with WAPT.

[Gaetan]

Great.

For uploading, I recommend the new method via the console: https://www.wapt.fr/fr/doc-2.1/wapt-cre ... apt-server

This reduces some inconveniences and simplifies operation.