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.
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
Python3.7 not able to identified. #113
Comments
@Alexey-T |
I use Linux with Py 36 and 37, all ok. |
@Alexey-T |
none, these are just some names - different linuxes use different names. |
In CudaText I have
|
Hi Alex and Pyscripter, |
@mamin27 I will merge your demo2..demo6 into my repo. Just delete programs "project1" (file size 20M) |
Ok I got it. https://www.python.org/dev/peps/pep-3149/. |
Hi pyscripter, I did not understood your link.
|
@mamin27 This PEP says that library files are marked with m if they are compiled with PyMemAloc which is the default. Apparently this only applies to non-Window distributions. |
@mamin27 |
@Alexey-T
I think is should show garbage. Then can you please check my fix? |
On Linux CudaText console panel shows that sys.argv is |
Ah! Because of:
Could you please test my fix? |
Thanks! |
I tested code at Ubuntu 19.04 with Python 3.7 and library
/usr/lib/x86_64-linux-gnu/libpython3.7m.so
I changed PythonEngine.pas file to
Then the python3.7 was recognized but at least not correctly initialized.
at line 3057
With error message:
Project Project1 raised exception class 'External: SIGABRT'.
In file '../sysdeps/unix/sysv/linux/raise.c' at line 50
Currently is recognized only Python 2.7.
Maybe you will know how to fix it.
The text was updated successfully, but these errors were encountered: