JMP19.1.2 has an issue with running python script directly from addin.

[#1]

JMP19.1.2 has an issue with running python script directly from addin, upon running it will crash.

 - If it runs directly the same script using script window, no issue.

 - If a script window already ran, and then only you run the script from addin, no issue.

 - Same script run from addin directly using 19.0.1 and jmp18, no issue.

There is a bug in the JMP 19.1.2 version for running python from addin directly without script window.

[#2]

The support tab at the top will get you to the tech support staff and help get a bug report filed or create a track to help resolve this in the future. (Possibly the track already exists with a solution.)

Or some people here might try to help if you can provide a small example that demonstrates the problem.

The problem is most likely related to the namespace that holds global variables. When you run a script

• from a script window, the script window holds the namespace
• from a button in a window, the window holds the namespace
• from a table script, the data table holds the namespace
• from an addin, a namespace is created and kept...somewhere

Chances are the addin needs a small change to the way it is using namespaces and global data.

[#3]

Some clarification please.  Please correct me if I'm wrong, the way I read this:

• A JSL script calling a Python file such as Python Submit FIle("my_py.py");  works fine when run from a script window.
• This same script runs from an add-in just fine in 19.0.1 and JMP 18 without issue.
• When you indicate:  If a script window already ran, and then only you run the script from addin, no issue. Do you mean
  • The script has run in a script window prior to running the add-in. ( as Craige indicated, this would populate the normal scripting namespaces, and Python global environment variables.)

Which host? Windows 11?  macOS Tahoe, Sequoia, Golden Gate, ... ?  Intel x86_64? ARM64? Apple Silicon?

If you can share a stripped down representative script that exhibits the crash, please post here or send to JMP Technical Support, or myself directly.   Do not include any proprietary information in the scripts.

Did JMP on it's next start-up prompt you to send crash logs?  Or did JMP just exit 'cleanly' and start-up cleanly without JMP recognizing a crash.

What Python packages are in use by your Python code?  package and version.  If it's a crash from within Python it could be due to package / version conflicts.  If you are using pandas make sure it is not the latest 24.0.x there are issues, with their dataframe handling.  Pin your pandas to the be < 24.0