Bug: submit-package-job failing on macOS when Deadline CLI is installed via submitter installer

[viknith]

Describe the bug

Before the macOS submitter installer was released, Mac users had to do pip install deadline, and then they would be able to submit conda package build jobs using the conda_recipes/submit_package_job shell script.

However, once I installed Deadline CLI via submitter installer, the else case in the shell script that represents the Unix handling case no longer works. Current workaround is to uninstall Deadline CLI and reinstall it via pip.

Expected Behaviour

I should be able to submit a package build job on my Mac machine regardless of how I've installed Deadline CLI to my machine.

Current Behaviour

$ sh submit-package-job aftereffects-25.1
cut: stdin: Illegal byte sequence

Reproduction Steps

1. Install Deadline Cloud CLI via submitter installer on a Mac, do not have Deadline installed via pip. Uninstall it if you have it.
2. Go conda_recipes and run ./submit-package-job aftereffects-25.1, no intial setup necessary.

Environment

At minimum:

1. Operating system: MacOS
2. Output of python3 --version: 3.13.2
3. Versions of relevant Deadline Cloud tooling that you're using (e.g. deadline --version, if using the CLI): 0.50.1

Please share other details about your environment that you think might be relevant to reproducing the bug.

[lucaseck]

Thanks for the report @viknith. This does appear to be a case that could be handled more gracefully. In general though I don't believe Windows, Linux or MacOS work when deadline is installed via the installer. The scripts are assuming that the cli was pip installed and using that to find the Python to use. There is no full Python interpreter bundled with the installer that we could use in those cases. Still, there's likely something that can be done here to make that more clear through better warnings or allowing people to specify their own python interpreter to use.