[SOLVED] Problem between Pyscripter 4 and the Python engine

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 17, 2021 - 2:05 PM

Hello,

since updating PyScripter to v4, it can no longer find the Python path in the Wapt installation folder. See the screenshot below:

Picture

Do you have any suggestions?

Thank you
Last edited by olaplanche on May 19, 2021 - 2:15 PM, edited 1 time.
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

May 17, 2021 - 2:45 PM

32-bit PyScripter? (Wapt is 32-bit, so it needs 32-bit PyScripter, not 64-bit)
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 17, 2021 - 3:43 PM

yes version 4.0.0.5 x86, I used the pyscripter package from the wapt store.
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

May 17, 2021 - 3:55 PM

The package has a problem; it's installing the x64 version. :roll:
I'll look into it.
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 17, 2021 - 3:59 PM

Ah, that's reassuring. :mrgreen:

I'll wait for your reply to do the update.

Thanks.
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

May 17, 2021 - 6:13 PM

Hello,
I've tested again on several environments and the PyScripter package installs correctly on x86.
Could you completely remove PyScripter and install it from the package, then test again?

Regards,
Jimmy
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 18, 2021 - 11:29

Hello,

I'm having the same problem after reinstalling v4, and the same after reinstalling v3 (and removing v4 from my local store).
v4 is no longer available on the Wapt store, so I can't reinstall it from there.

Thanks
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 19, 2021 - 2:14 PM

OK, I just solved my problem!

After analyzing the pyscripter v3 package (v4 is "broken") available on the store, it seems that the modifications made to the pyscripter.local.ini file are not taken into account during installation (at least not on my system).

I copied the following Python version modifications to the end of the pyscripter.local.ini file in my machine's local administrator profile:

Code: Select all

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

[PythonVersions-x86\Custom Versions]
Path0=C:\Program Files (x86)\wapt
Count=0
After this modification, pyscripter is working properly again (I just updated a package)
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
olaplanche
Messages: 178
Registration: January 26, 2017 - 11:11

May 19, 2021 - 2:23 PM

After using PyScripter, the pyscripter.local.ini file changed as shown below:

Code: Select all

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

[PythonVersions-x86]
InstallPath=C:\Program Files (x86)\wapt
- Installed WAPT version: 2.6.0.16795 Enterprise
- Server OS: Linux / Debian Bookworm
- Administration/package creation machine OS: Windows 10
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

May 20, 2021 - 09:47

Actually, it's quite simple:

pyscripter4 is no longer compatible with Python 2.7.

Therefore, you'll have to wait for the discovery to use pyscripter4.
Locked