targetcli stops parsing command at caret character

[Craig Putnam]

targetcli stops parsing a command at a caret "^" character. This makes it impossible to include a password with a caret in it.

Example:

/> set global logfile=foo^bar garbage junk
Parameter logfile is now 'foo'.

In this case, we should get an error that there are extra positional parameters. If we excise "garbage junk", we would expect the parameter "logfile" to be set to "foo^bar". Obviously I don't care about setting the log file to a weird name, but this is the simplest way I could find to reproduce the bug. :)

Single and double quotes around the parameter or parameter name make no difference, nor does escaping the caret character with \ or ^.

/> version
Using configshell version 1.1
Using rtslib version 2.1
Using targetcli version 2.0rc1

Packages versions:
targetcli 2.0rc1-2
python-urwid 1.0.1-2

$ cat /proc/version
Linux version 3.5.0-17-generic (buildd@allspice) (gcc version 4.7.2 (Ubuntu/Lina
ro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012