argparse v2.2.3

• Character values are now passed as "raw" strings to Python (#51).

  • In particular this avoids triggering an error in Python 3.12
    when creating a string with escapes not supported by
    Python e.g. default = "\\D" will continue to return a
    default value of "\\D" instead of triggering an error.

  • However, this also means that any Python accepted escape
    sequences will no longer be interpreted as an escape sequence.
    If relying on such behaviour you may need to instead use
    the appropriate R escape sequences or Unicode values instead of Python escape sequences:

    • E.g. default = "\\t" will now return a default value of
      "\\t" (a t preceded by an (escaped) backslash)
      instead of "\t" (a horizontal tab).
    • https://docs.python.org/3/reference/lexical_analysis.html#escape-sequences
    • https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)

  • Thanks Matthew Hall (@mdhall272) for bug report.

argparse v2.2.2

• Fixes bug when add_argument() help values ended in a " (#46).
  Thanks Oliver Dreschel (@oliverdreschel) for bug report.

argparse v2.2.1

• We now support the following ArgumentParser() methods:

  • format_help()
  • format_usage()
  • parse_intermixed_args() (#45)
  • parse_known_intermixed_args() (#45)
  • set_defaults() (#43). Suggestion of @oliverbothe.

• When an error is thrown by ArgumentParser()$parse_args() and interactive() is FALSE
  and getOption("error") is NULL then
  we now use a quieter default error handler that doesn't output a trailing "Execution halted".

• add_argument() now allows "numeric" as an alias for "double" for the type argument (#42).
  Suggestion of @dariober.

• ArgumentParser() now handles description arguments with newlines in them (#44).
  Thanks Arthur Gilly (@agilly) for bug report.

argparse v2.1.6

• The errors raised by ArgumentParser()$parse_args() are now of class "argparse_parse_error".

  They are now less verbose when interactive() is FALSE (#40).

  There may still be a trailing "Execution halted" line output by R's default error handler
  (when interactive() is FALSE).
  This can be silenced by setting a new error handler near the top of your Rscript e.g.

  if (!interactive())
      options(error=function(e) quit('no', status = 1, runLast = FALSE))

argparse v2.1.5

• add_argument now uses as.logical() logic to cast variables
  to logical values if type = "logical" and action = "store" or action = "append"
  instead of using Python's bool() logic (#39).

  • We throw an error if we would get an NA by coercion.
  • We no longer throw a warning when using type = "logical" and action = "store"
    suggesting users instead use action = "store_true" or action = "store_false".

argparse v2.1.3

• Prevents extraneous error message from being included in usage message
  when using Python 3.10 (#36).
  Thanks @dariober for bug report.

argparse v2.1.2

• Fixes bug when using an argument with action == "append"
  and a non-NULL default value (#35).
  Thanks @miker985 for bug report.

argparse v2.1.1

• Parsers now support parse_known_args() (#34).
  Suggestion of David Lacalle Castillo (@WaterKnight1998).

argparse v2.0.4

• May now specify a named formatter_class argument (as a string)
  to a subparsers$add_parser() method.
  Thanks Regina (@oyxf) for bug report.
• May now specify positional arguments in ArgumentParser().

argparse v2.0.3

• Fixes bug when accidentally passing a positional argument
  to ArgumentParser() when using Python 3.9.
  Thanks Kurt Hornik for bug report.