obs-scripting: Replace deprecated PySys_SetArgv

[rebstrike-code]

Description

Updated the PySys_SetArgv(argc, argv); line to have a more modern way of setting the arguments.

Motivation and Context

PySys_SetArgv is depreciated and has already been removed in Python 3.13

How Has This Been Tested?

Ran in Visual Studio code
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.18.1-061801-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS

Types of changes

• Code cleanup (non-breaking change which makes code smaller or more readable)

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[RytoEX]

Commit message nits.

obs-scripting: Fix depreciated Python interpreter's command line arguments configuration

This commit title is too long. Use:

obs-scripting: Replace deprecated PySys_SetArgv

PySys_SetArgv has been deprecated since Python 3.11 and will be removed
in Python 3.15. Use PyConfig_InitPythonConfig instead, which was added
in Python 3.8.

References:
* https://docs.python.org/3.14/c-api/init.html#c.PySys_SetArgv

---

PR title nit:
depreciated -> deprecated

Or use the commit message title I have provided above.

---

Do not leave fixup commits in the PR. Do not use git merge to update branch history. Use git rebase to fix all of these issues.

[Rebstrike]

Commit message nits.

obs-scripting: Fix depreciated Python interpreter's command line arguments configuration

This commit title is too long. Use:

obs-scripting: Replace deprecated PySys_SetArgv

PySys_SetArgv has been deprecated since Python 3.11 and will be removed
in Python 3.15. Use PyConfig_InitPythonConfig instead, which was added
in Python 3.8.

References:
* https://docs.python.org/3.14/c-api/init.html#c.PySys_SetArgv

PR title nit: depreciated -> deprecated

Or use the commit message title I have provided above.

Do not leave fixup commits in the PR. Do not use git merge to update branch history. Use git rebase to fix all of these issues.

Apologies. I am fairly new to GitHub

[RytoEX]

This is incorrect. Per my original review:

PySys_SetArgv has been deprecated since Python 3.11 and will be removed
in Python 3.15. Use PyConfig_InitPythonConfig instead, which was added
in Python 3.8.

[RytoEX]

It's not clear that this is even necessary. We only support building against Python 3.8-3.12. We need to determine if this code is affected by the user's Python runtime at all.

[Rebstrike]

This was added in Python 3.8, which means explicitly dropping support for Python 3.6 and 3.7, which cannot be done until a major release.

I'm confused by this comment then. I interpreted this as you saying that the new API was introduced in 3.8 but my code still needs to support 3.6 and 7. Are you now saying to use the new API and not worry about backwards compatibility?

[RytoEX]

No. I'm saying that in this PR as it was originally submitted, it explicitly used Python 3.8 only code. For compile time dependencies, we only support Python 3.8-3.12 anyway, so this does not matter. For run time dependencies, we in theory support Python 3.6+, so it would need to be confirmed if a user can still load/use Python 3.6/3.7 with the original changes. If it is the case that users cannot use Python 3.6/3.7 at runtime with the original changes, then my comment was a note to mergers that "this cannot be merged until we're in a merge window for a major release as this would be a breaking change".

The open question is: does the code in this PR as it was originally or as it is now affect compile-time Python, run-time Python, or both?