CLI debugger (--debug) does not work with standalone scripts (--script)

[wyattbiker]

Godot version:
3.2.alpha1.official

OS/device including version:
Mac OS X Mojave

Issue description:
As per documentation from godot -h:

Debug options:
  -d, --debug                      Debug (local stdout debugger).
  -b, --breakpoints                Breakpoint list as source::line comma-separated pairs, no spaces (use %20 instead).

I am trying to use the -b and -d options from the command line, but it's as if nothing happens.
godot -s somescript.gd --debug --breakpoints somescript.gd::3

Steps to reproduce:
Create somescript.gd script and execute above CLI command.

extends SceneTree
var somevar = 20
var foo1='abcd'
func _init():
	print(foo1)

[akien-mga]

It works fine when you are running an actual scene, but it doesn't seem to work together with the --script option indeed.

[wyattbiker]

I don't think it runs 100% correct even with scene only.

https://docs.godotengine.org/en/3.1/getting_started/editor/command_line_tutorial.html#debugging

There is some confusion as to what is supposed to happen when you run -d.
E.g.
godot TestScript.tscn -d

It seems, if there is no syntax/runtime error, it does not break into the debugger prompt even when using a scene. But introduce an error in the scene attached script, e.g. x = somevar / 0 then it will break.

[KoBeWi]

Still valid in 3.2.3