@rixx Hello! Thanks for reporting this. So, this appears to be an odd behavior related to how the library we use to parse the command-line arguments works. I think this is definitely worth fixing. For now, here is a workaround.

You can edit your mycli config file (defaults to ~/.myclirc) and set the audit_log config option to ~/.cache/mycli.log. I actually do something similar with my mycli config.

As for fixing this going forward, it looks like we need to change this from a click.File to click.Path. Marking as a bug 😄

@tsroten. When run

mycli mysql://root@10.6.112.32:3306 --logfile=~/mycli.log

will get

Error: Invalid value for "-l" / "--logfile": Could not open file: ~/mycli.log: No such file or directory

But run

mycli mysql://root@10.6.112.32:3306 --logfile ~/mycli.log

It will be ok.

~ is normally expanded by the shell. If use --logfile=~/mycli.log, it will not trigger. I find that someone wants to using os.path.expanduser to solve this problem in Click, but the pull request was rejected. Please see pallets/click#229.

And click.Path will not work too.