-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tom Tobin wrote: > shlex is likely the wrong solution; it's quite old (introduced in 1.5.2) > and doesn't understand Unicode.
Yes, but we've already worked around that. See bzrlib.commands.shlex_split_unicode
Consistency is a virtue, so we should use the same mechanism for splitting commandlines everywhere we can.
Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIDgE40F+nu1YWqI0RAiWWAJ4j/2U+UHiJhsA/RmlFIihZ/MJtwgCfRd0g 7mKqjzwZeGjV5R+fC70nE1g= =to1M -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom Tobin wrote:
> shlex is likely the wrong solution; it's quite old (introduced in 1.5.2)
> and doesn't understand Unicode.
Yes, but we've already worked around that. See commands. shlex_split_ unicode
bzrlib.
Consistency is a virtue, so we should use the same mechanism for
splitting commandlines everywhere we can.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFIDgE40F+ nu1YWqI0RAiWWAJ 4j/2U+UHiJhsA/ RmlFIihZ/ MJtwgCfRd0g fC70nE1g=
7mKqjzwZeGjV5R+
=to1M
-----END PGP SIGNATURE-----