new status output

[Jan Hudec]

On Tue, Oct 25, 2005 at 20:33:20 -0500, John A Meinel wrote:
> Does that make sense? Basically, I'm saying right the command line
> interface such that it plays well with shells. And maybe have a switch
> to turn on cmd.exe compatibility, which disables most of the shell
> friendliness.

Default value of that switch could be dependent on whatever os.name
is. Cygwin python returns 'posix' there, just as all unix versions,
while native windows python returns 'nt' on Windows NT/XP and maybe
some other specific value on Windows 95/98/2000.

Now users that use bzr from cygwin will probably use cygwin python too
(they will need to, so it handles the cygwin paths) and will get the
scripting interface. Those who have native python probably don't have
cygwin anyway and will get the windows interface.

There could be a '--compatibility' option, that would mean 'act as if
os.name was this'. So: --compatibility=posix for the scripting interface
and --compatibility=nt for the windows one.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051026/77c5dce8/attachment.pgp