LORD-MicroStrain
MSCL API 3.6+ Python Version
Is there any way we can update the MSCL API to take on python 3.6+? Currently the API is in python 3.6. 3.6 is an outdated version of python and it'd be very helpful to use newer versions of python for more development. Wondering if this is possible.
I definitely understand the frustration, 3.6 has been end-of-life'd. I'm going to look into a couple options for getting a build for a newer version of Python and get back to you in the next few days.
Is there a specific Python version that would be most ideal for you?
Are there any updates on this? I have had no luck using the 3.6 version.
So sorry for the delay on this! I've just added a link to a build for Python 3.11 to the Pre-Built MSCL Binaries/Packages section of the README. There shouldn't be any difference in how the API is installed or used.
Please let me know if you run into any issues or if this Python version won't work for you!
I have only Python 3.11.4 installed and am not running into any issues importing. It looks like it can't find the _mscl.pyd file - are both mscl.py and _mscl.pyd in the VibrationSensorAutomation\msclNuc folder? It might be worth confirming that both files were updated from the 3.11 download by deleting the existing and re-copying them into the location.
You might also try putting the mscl.py and _mscl.pyd files directly in the same folder as the script you're running temporarily just to be sure they can find them.
The MSCL 3.11 zip seems to only support 3.6.
Does this mean that when you run your script with Python 3.6 and the Python 3.11 MSCL files it works fine? Is it possible there are Python 3.6 MSCL files still somewhere on the system in a directory Python will search for modules?
I've just installed Python 3.6.8, when I try to import the Python 3.11 MSCL files I get the following error:
Traceback (most recent call last):
File "c:/dev/MSCL-PythonTest/main.py", line 1, in <module>
import mscl
File "c:\dev\MSCL-PythonTest\mscl.py", line 15, in <module>
import _mscl
ImportError: Module use of python311.dll conflicts with this version of Python.
I'll add one more thing here. If you're using Windows, be sure that the .pyd file isn't being deleted by your virus protection software. It should be pretty obvious if this is happening, but this is one issue that I have run into.
im running in 3.11.4, running into this issue
I've tried the 2.7 and the 3.6 versions and windows and getting this same DLL message. It's not supposed to be a DLL it's supposed to be *.pyd what is going on here?
