`--archive-less-mature` is defined to expect an `int`, and is given a `None` by default. Which, works fine in `click<8.3`, and fails in `click>=8.3`

[omad]

Update
This has been reported as a bug against click 8.3 (linked below), I've had a go at working around it, and, it's not trivial, so we should just wait for a new click release and stick with 8.2.1 for now.

That said, the allowed values for archive less mature are confusing and error prone (None = disable, Positive Int = allowed difference in time values).

Also, I think that click is too flexible and confusing here too, allowing optional and flag values is documented and used to work, but also strange and confusing. I'm not entirely convinced it's not an anti-feature that should be deprecated and removed.

Bug

The failure message from fs-to-dc in the tests is:

Usage: fs-to-dc [OPTIONS] INPUT_DIRECTORY
Try 'fs-to-dc --help' for help.

Error: Invalid value for '--archive-less-mature': '--env' is not a valid integer.

It looks like --archive-less-mature is defined to expect an int, and is given a None by default. Which, erroneously works fine in click<8.3, and fails in click>=8.3. See pallets/click#3084

Originally posted by @omad in #674 (comment)