Problem setting Python executable

[Dex]

So I've installed the trial because I'd like to try it before I buy the full version. However, I can't even set it up properly. After launching I get the following error message:

A supported version of Python could not be found. If you have a recent Python, be sure you also have a recent version of Wing. If you do not have Python on your system, you will need to install it before most of Wing's features will function properly. If Python is already installed, use Project Properties in the Project menu to select the Python Executable to use.

Then when trying to set the correct executable:

Could not launch or inspect Python executable '/usr/bin/python3'. It should be the name of a Python interpreter that is on your PATH (such as python, python3.4, python.exe) or the full path to the Python interpreter you wish to use.

I'm on Manjaro 17 and using Python 3.6.2.

[76561198135123592]

Can you run /usr/bin/python3 outside of Wing? The drop down to the right of Python Executable should list the Python installations that Wing found automatically on your system. It may be empty, given what you wrote above, in which case please email the file ~/.wingide6/ide.log to [e-mail] or submit a bug report from the Help menu and include the error log (which is that file) so we can see why Wing is not able to use Python on that system.

It may be that the Python is 32-bit, which Wing 6 does not support on Linux except via remote development. But it would be odd to have /usr/bin/python3 be 32-bit on a Linux system where Wing can run -- it should only start at all on a 64-bit system.

[Dex]

I can run it outside of Wing without any problems. Wing is also showing me a few other executables in the dropdown menu (for example /usr/bin/python, /usr/bin/python2.7 and /usr/bin/python3.6) but none of those work :(

And yeah, I'm on a 64-bit system.

[Tapasvi]

Just a thought, have you tried to input all paths manually?
Both executable and directory. The ones you can get from the terminal.
For some reason, Wing doesn't detect the right Python for me, there were only Python 2 default options, while i was using Anaconda Python in other path. But inputing it manually and restarting the shell in Wing solved this.

[Dex]

You mean setting the Python path? Yeah, I've tried that. However, I can't even apply the changes I've made because when I click the Apply button in the settings window, it just throws me that error message about the executable.

I've tried running Wing on other Linux distros yesterday, with the same result. I just can't get it to work.

[76561198135123592]

This is pretty strange... What is the value of sys.maxsize (after 'import sys') in your Python versions that are not working with Wing? Also do you have more information about the error when you try to set the Python Path? Emailing ~/.wingide6/ide.log and ~/.wingide6/segfault.log (if it exists) to [e-mail] may show us more about what is going wrong.

[Dex]

python2 -c "import sys; print sys.maxsize"
9223372036854775807

and

python3 -c "import sys; print(sys.maxsize)"
9223372036854775807

I'll be sending over the logfiles. Hopefully we can resolve this - I've tried Wing on Windows and it seems nice, so I'd love to be able to use it on Linux as well!

[SquidCell]

I have the same issue. ..was looking at wing as a speedy alternative to PyCharm.

[SquidCell]

Ubuntu 16.04, same issue with system executable or virtualenv.

[SquidCell]

Setting up a remote instance to localhost works, but after an install of test environment -- 32/64 bit issue?

[76561198135123592]

Ah, yes, Wing 6 doesn't support 32-bit Python on Linux except through remote development. We didn't expect people to be able to install Wing on machines with 32-bit Python, so didn't include the 32-bit debugger support with the IDE installation. Is it a problem to use 64-bit Python instead? I'm wondering if we need to rethink this limitation.

[SquidCell]

My system is 64-bit, and I'm pretty sure the default Python for Ubuntu 16.04 is 64-bit on a 64-bit system, and that I don't have a 32-bit Python executable installed.

[76561198135123592]

Can you verify that sys.maxsize is 9223372036854775807 in the Python you're trying to use? I ask because the fact that it works to set up remote to the local host but not otherwise seems to indicate it could be 32-bit...

But if not, then what do you get for output in the Python Shell if set WINGDB_PRINT_ALL_TRACEBACKS=1 in the Environment in your Project Properties in Wing and then restart the shell from its Options menu?

That may show us why Wing can't run the Python instance.

[SquidCell]

Yep. Definitely 64-bit -- sys.maxsize verified.
The 32-bit message that popped up seems to have to do with the steam overlay (tried disabled and enabled). This is the error:
----
Connecting to host id local failed.

Output received:

ERROR: ld.so: object '/home/silver/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
SSH client exited errno=0
----



This is the errror that I get when I select one of the python executables from the 'custom' entry in project properties:

----
Some values are invalid:

- Could not launch or inspect Python executable '/usr/bin/python3.3'. It should be the name of a Python interpreter that is on your PATH (such as python, python3.4, python.exe) or the full path to the Python interpreter you wish to use.

Please correct the values and try again.
----

I'll look into running this from the console, then give you info re: output

[SquidCell]

Actually, I'm getting a lot of segfaults from wing on steam, and it may be related to steam somehow -- however, I don't have this problem with other programs. I'll see if I can get some debug info for you.

[76561198135123592]

Try installing the off-Steam version of Wing from {LINK REMOVED}wingware.com. It'll run using the license set up by Steam and will help rule in or out whether the Steam client's environment is messing with Wing. They do leave some envs set that can cause problems like this despite our attempts to ignore those envs. Not sure why they do this... seems like a bug to send their own private env on to the app/game.

You can also inspect the os.environ from the Python Shell if that'll start, or from an OS Command, and reset or clear items that might be a problem in Environment in Wing's Project Properties. Using ENVNAME= (without any value after the =) to clear an env. It's probably LD_* envs that are causing this by listing 32-bit libraries or library directories.