On Mon, 19 Aug 2013 10:32:35 -0400 micah <mi...@riseup.net> wrote: > Antoine Beaupré <anar...@anarcat.ath.cx> writes: > > On 2013-08-17 18:16:59, Micah Anderson wrote: > >> You can pass the full fingerprint, including spaces, to monkeysign for > >> the key to be signed. However, if you try to do this for -u, then it > >> gets rather confused and only takes the first 4 characters and then > >> assumes the remainder is a key that should be signed (an invalid key > >> that it will fail to find). > > > > This is a limitation of the "optparse" library - the number of arguments > > to an option is hardcoded, I believe. Logically, the commandline parser > > needs to know how many arguments after `-u` it needs to "eat" and pass > > to that option, and since we want to accept single uids, it seems to me > > we can't accept space-separated fingerprints there. > > > > I know it's inconsistent, but it's a limitation with the commandline > > parser built into python. The new "argparse" library supports variable > > length arguments, but that requires porting: > > Thanks for the explanation!
usually arguments in the unix world will only have one value that may have a special format to bring in more information. > > http://docs.python.org/2/library/argparse.html#nargs > > > > So for now, use a single userid or (non-space-separated) fingerprint. > > > > (Or is monkeysign -u choking on (non-space-separated) fingerprints?) > > Nope, it is just choking on the space-separated ones. have you tried quoting your fingerprint so that it's taken as "one blob" for the -u option? like this: monkeysign -u "1234 5678 9ABC ..." --other-options the above seems to be working for me with the 2.x branch. -- Gabriel Filion
signature.asc
Description: OpenPGP digital signature
