bzr-0.1-rc1: selftest bug (windows specific): problem with os.sep

[Martin Pool]

On 24/10/05, Matthew Hannigan <mlh at zip.com.au> wrote:
> On Sun, Oct 23, 2005 at 06:47:54PM +0200, Wouter van Heyst wrote:
> > On Sun, Oct 23, 2005 at 04:27:16PM +1000, Robert Collins wrote:
> > > What I'd like us to use is:
> > > 'os.sep' in user output
> > > '\\' or '/' in user input is translated to '/'.
>
> By '\\' are you including \ ?   I think os.sep should be allowed
> in user input.  I suspect you mean this too, just want to be clear.
> I wouldn't expect win users to type in c:\\Some Where\\Over The Rainbow
> (if in fact they actually type in full pathnames anywhere)

I think they meant just a single \ or if you prefer r'\' in python
syntax.  So you would be able to say "bzr log src\foo.c" or "bzr log
src/foo.c" on Windows.

Everyone seems to agree on this.  The question is what to do on output.

> The upshot of the two above would result in being able
> to copy and paste bzr output to (some other) bzr input,
> which is a nice user-friendly feature.

Well, if we accept both forms, then this will be true whatever we
produce.  However, if we produce / then people will not be able to
paste output into other commands because they might not accept it.  On
the other hand copying and pasting in shells seems less common on
Windows than Unix (but maybe not?).

Would anyone else prefer the \ form - particularly regular Windows
users?  I'm inclined to go for consistency across platforms but I
definitely see Alexander's point about / being only partially
supported by windows programs.

--
Martin