Request for Python 3.13 Support in Logic2 Automation API

Dear Saleae Team,

Thank you for your excellent tools. I have been using them since the 2010 and can’t wait for the next gen of Pro analyzers!

I recently encountered a segmentation fault while compiling a script using the Logic2 Automation API with Nuitka on Python 3.13. Downgrading to Python 3.9 resolved the issue, but this underscores the need for support of newer Python versions.

Adding support for Python 3.13 would enhance compatibility and leverage its performance improvements. Could you consider including Python 3.13 in future update?

Many thanks,
JH

@Jiri_H We’ve got a few other users requesting this, particularly to allow for more features. Apologies we haven’t been able to work on this yet. We’re currently keeping track of all requests for Python updates in the feature request post below, and I added a comment for you to track your need for this as well.

Hi Tim,
many thanks for such swift reply. Any ROM estimate when you can implement/release this update? Can you also confirm the highest version of Python the current version supports (I haven’t experimented with other versions than 3.09)?
Jiri

@Jiri_H After reviewing your post again, we wanted to clarify that our Automation API should work with no issues on Python version 3.13. The feature request link I had posted above is for the Python version that is built-in to our software. In short, I wanted to make sure that was made clear to avoid confusion.

Having said that, I wanted to ask you about the issue you posted below.

Can you share more information about that? Python scripts do not need to be compiled, and can be run as-is to execute our software functions via automation. Hope to learn more about your use case!

Hi Tim,
Thank you for your response and for clarifying that the Logic2 Automation API should work with Python 3.13 for native script execution. I’ve confirmed that my script (importing saleae.automation) runs without issues when executed natively with Python 3.13. However, my issue occurs when compiling this script into a standalone executable using Nuitka with Python 3.13, resulting in a segmentation fault. Downgrading to Python 3.9 resolves the issue, suggesting a compatibility problem with Nuitka, Python 3.13’s C API, and dependencies like grpcio and protobuf.

My use case involves compiling scripts for distribution as standalone executables, which is common for automation workflows. Could you confirm if the API has been tested with Nuitka or similar compilers on Python 3.13? If not, I kindly request:

  1. Testing the API with Nuitka on Python 3.13 to identify compilation-specific issues.

  2. Documentation on supported Python versions and compatibility with compilation tools like Nuitka.

Many thanks,
Jiri

@Jiri_H Thanks for explaining your use case! I’m glad to hear the script is able to run natively. Our Automation API was designed for native execution only via Python. We do not test compilers like Nuitka.

Having said that, we’ll keep an eye our for anyone else that might have similar requests! Feel free to post your request on our ideas site below as well and we can start tallying votes for it.