Maybe, but as I remember this is a PITA to do it that way.
MSFT Visual Studio Code: You can setup multiple configurations.
Each configuration identifies the type (python, js, others?)
The path to the script to debug.
The Arguments to use when starting the script.
etc.
This is a *much* better way that Slick currently has.
I have to do Build->Python Options and set the correct version of Python to use.
Then to edit the script arguments I can set them in Project Properties, where the arguments are mixed in with stuff necessary for Slick
%(SLICKEDIT_PYTHON_EXECUTE_ARGS) "%f" %~other ....My args go here ...
Or use Debug->Start with Arguments.
But, then I also have to be careful to set the correct *.py file as the current file or I start debugging in some random library *.py file from the last debug session.
Overall, a lot less than ideal.