sftp urls are interpreted as a local paths

[John Arbash Meinel]

Matthieu Moy wrote:
> Haakon Riiser wrote:
> 
>> Btw, shouldn't bzr report this problem to the user when
>> encountering sftp:// urls, instead of just converting it to a
>> local path?
> 
> I think this was the initial behavior (raise an error, saying that
> paramiko is needed). It was IMHO better (I can't imagine someone typing
> sftp://something for a local path).
> 

I agree. The specific issue is if we had multiple sftp handlers.

What happened is that we ended up with multiple http handlers, so we
needed a way to fall back after trying the first one. Because we support
decorators, and other such things, it isn't quite as trivial to just
check for the protocol (we support stuff like readonly+sftp:// for instance)

However, I did fix up some of that in my encoding branch, since I am
working on fixing up how Transport uses URLs instead of whatever mix it
is using now.

So if it gets something that looks like a URL (has :// in it), then it
will complain about an unsupported protocol, rather than trying it as a
local path.

But it could use a little bit more work, so that it would give the
proper error saying what needs to be installed.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060516/a3305490/attachment.pgp