It's been brought up a few times, I'd quite interested in patches that implemented this.
It probably seems that it could be dealt with my seeing if the file was binary (run 'file' or something better) and take care of business.
There's definitely *not* a reason why this shouldn't be solved, the 'old style" (non Python) module path will still pass in a "key=value" arguments line to the file passed to $ARGV[1] of the module, however. There's a bit of a hack in there to tell if the module indicates it wants JSON data.
I suspect that if we detect the module is binary it should assume it wants JSON, since that's going to be the better way to pass variables almost all of the time -- what's included there is for compatibility reasons and ease of use from bash more so than anything.
Does this make sense?
I'm definitely interested in patches for this, one or two people have been interested in modules written in Go, in particular.
Thanks!
--Michael