Message262569
My support (or really, asking for a more generic callable) was to enable other use cases, not this one specifically -- e.g., allowing for constructing a pathlib Path or a twisted.python.filepath.FilePath without needing to write one's own argparse action.
For ~ specifically -- it's true if you're going to go via a shell it'd be expanded first, but I'm not sure that'd count as "conflicting" with the shell's expansion, it just won't be needed. Consider that twisted.python.filepath.FilePath for example, expands ~ in its constructor -- people often construct paths in other places and occasionally expansion is convenient. Like in test cases.
I certainly don't feel strongly about the patch though, especially as-is. |
|
Date |
User |
Action |
Args |
2016-03-28 12:19:49 | Julian | set | recipients:
+ Julian, berker.peksag, martin.panter, paul.j3, serhiy.storchaka, garthy |
2016-03-28 12:19:49 | Julian | set | messageid: <1459167589.89.0.0141571962987.issue19959@psf.upfronthosting.co.za> |
2016-03-28 12:19:49 | Julian | link | issue19959 messages |
2016-03-28 12:19:49 | Julian | create | |
|