[issue38843] Document argparse behaviour when custom namespace object already has the field set

Ivan Kurnosov added the comment: > I have not seen many questions about the use of a preexisting namespace > object (here or on StackOverflow) as typing was added to the language natively - it should become more and more frequently used. I personally see no reason anymore to NOT

[issue38843] Document argparse behaviour when custom namespace object already has the field set

New submission from Ivan Kurnosov : At this moment it's impossible to explain the behaviour of this script using documentation. Given it was explicitly coded to behave like that - it should be somehow noted in the documentation, that as long as a `CliArgs.foo` field has a default value