And in case you needed another reason to read that, note the author line: Neal Stephenson

There's also nargs=argparse.REMAINDER instead of nargs="+", but that won't work for this actual use case.

Is this a bug in argparse, or is that behavior documented anywhere?

I'd kinda hate having to document quirks like that in the docs for a CLI tool... E.g. "don't put an argument with quoted spaces after --foo" is an unfortunate thing to need to add to docs...

That unexpectedly produces:
['bar', 'baz', '--some-other-arg="foo bar"']
for the first argument order and
['bar', 'baz']
as expected for the second

Using a non-quoted argument or leaving out the = sign works and produces the latter expected result.

And also, SLC is kinda pretty too...

Also, one of the things I love about living in SLC is that this was just our morning dog walk... We did drive to the trailhead in this case, but it's a five minute drive.

Also, Copper does not like this tradition.....

Even better, you can _charge_ the embodied AGI for its own training!

On my deathbed, I will regret not mobilizing my actionables in order to maximize my market impact.

He's summoning the legions of maddened holiday travelers to descend on the airport. Chaos will reign.