No Python 3 engine found on MacOS

[tonydunn]

I'm running Mojave 10.14.6 and trying to get CudaText 1.136.0.1 to find my Python 3 library so plugins work. I'm offered /Library/Frameworks when I do Plugins -> Find Python Library, but that finds nothing. I've tried searching from / but no joy.

Python 3.9.6 is installed from the Python site, no issues as far as I can tell. Doing 'type python3' returns: python3 is /Library/Frameworks/Python.framework/Versions/3.9/bin/python3

Can't see what I'm doing wrong, but must be something. Anyone give me some pointers on this one, otherwise I'm pretty much finished before I start?

Thanks

Tony

[uvviewsoft]

Pls try to find the file libpython3.x.dylib, CudaText assumes it must be in the
'/Library/Frameworks/Python.framework/Versions/3.9/lib/libpython3.9.dylib'
What is your path of this file?

[tonydunn]

Here is what I found:
tony@Tonys-MacBook-Air/L/F/P/V/3/lib> pwd
/Library/Frameworks/Python.framework/Versions/3.9/lib
tony@Tonys-MacBook-Air/L/F/P/V/3/lib> la libpython3.9.dylib
Permissions Size User Group Date Modified Name
lrwxr-xr-x 9 root admin 2 Jul 15:56 libpython3.9.dylib -> ../Python

The file is there, and symlinked to ../Python.

Does that help?

Thanks for quick reply,

Tony

[uvviewsoft]

yes, that helps, that filename must not be symlinked to a folder name. that is (I am 70% sure) the bug in Python installation.
can you try to uninstall and reinstall the Python?

[tonydunn]

I could uninstall and reinstall Python but it was a 100% clean install just today, so I don't understand how a fresh install would do anything different? I can and will do as you ask, but why would it do any good please?

[uvviewsoft]

Then don't reinstall. I am puzzled now why that useful python3.9.dylib filename is a symlink to a folder... google cannot help me.

[tonydunn]

It's strange, but the symlink does not point at a folder. The symlink goes to a file called Python in the directory immediately above. The symlink has a size of 9 bytes, the object it is linked to has a size of 7,622,368 so it is the object called Python which is the library file I think? Look at this:

Code: Select all

tony@Tonys-MacBook-Air/L/F/P/V/3.9> ls -la Python
-rwxrwxr-x  1 root  admin  7622368 28 Jun 16:37 Python
tony@Tonys-MacBook-Air/L/F/P/V/3.9> file Python
Python: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64]
Python (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
Python (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64
tony@Tonys-MacBook-Air/L/F/P/V/3.9> cd lib/
tony@Tonys-MacBook-Air/L/F/P/V/3/lib> file libpython3.9.dylib
libpython3.9.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64]
libpython3.9.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
libpython3.9.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64

That any clearer?

Thanks

Tony

[uvviewsoft]

I now tried it on old Macbook and confirm it. I installed different Python 3.9- not 'universal' but 'Intel', and it was detected by Cud and works OK. maybe try to remove your 'universal' one and get 'Intel' one?

[uvviewsoft]

Python 3.9.6 - June 28, 2021

Download macOS 64-bit Intel installer
Download macOS 64-bit universal2 installer

[tonydunn]

That sounds like the fix - I'll remove the universal, install the Intel, and try again.

Thanks - will post what happens