From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Antoine Pelisse <apelisse@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] remote-hg: fix path when cloning with tilde expansion
Date: Fri, 09 Aug 2013 22:18:32 -0700 [thread overview]
Message-ID: <7vioze2kev.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s1Q2x9uz5Ajr=BgVjSjO88XD5UYzVSEqgMeK5_YAYSa5A@mail.gmail.com> (Felipe Contreras's message of "Fri, 9 Aug 2013 18:43:09 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
>> Hmph, do you mean the third example of this?
>>
>> $ python
>> >>> import os
>> >>> os.path.expanduser("~/repo")
>> '/home/junio/repo'
>> >>> os.path.expanduser("~junio/repo")
>> '/home/junio/repo'
>> >>> os.path.expanduser("~felipe/repo")
>> '~felipe/repo'
>>
>> which will give "~felipe/repo" that is _not_ an absolute repository
>> because no such user exists on this box?
>>
>> It is true that in that case fix_path() will not return early and
>> will throw a bogus path at "git config", but if the "~whom" does not
>> resolve to an existing home directory of a user, I am not sure what
>> we can do better than what Antoine's patch does.
>
> I was thinking something like this:
>
> if url.scheme != 'file' or os.path.isabs(url.path) or url.path[0] == '~':
> return
That did cross my mind.
I know ~/ and ~who/ are expanded on UNIXy systems, and I read in
Python documentation that Python on Windows treats ~/ and ~who/ the
same way as on UNIXy systems, so the "begins with ~" test would work
on both systems. But it is probably a better design to outsource
that knowledge to os.path.expanduser(), with the emphasis on "os."
part of that function. That way, we do not even have to care about
such potential platform specifics, which is a big plus. The only
possible difference that approach makes is the above example of
naming a non-existent ~user, but that will not work anyway, so...
next prev parent reply other threads:[~2013-08-10 5:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 20:12 [PATCH] remote-hg: fix path when cloning with tilde expansion Antoine Pelisse
2013-08-05 20:30 ` Felipe Contreras
2013-08-05 20:32 ` Antoine Pelisse
2013-08-09 17:13 ` Antoine Pelisse
2013-08-09 18:49 ` Junio C Hamano
2013-08-09 20:09 ` Antoine Pelisse
2013-08-09 20:53 ` Junio C Hamano
2013-08-09 21:19 ` Antoine Pelisse
2013-08-09 21:45 ` Junio C Hamano
2013-08-09 21:55 ` Antoine Pelisse
2013-08-09 21:55 ` Felipe Contreras
2013-08-09 22:15 ` Junio C Hamano
2013-08-09 22:28 ` Felipe Contreras
2013-08-09 23:39 ` Junio C Hamano
2013-08-09 23:43 ` Felipe Contreras
2013-08-10 5:18 ` Junio C Hamano [this message]
2013-08-10 6:39 ` Felipe Contreras
2013-08-10 6:50 ` Junio C Hamano
2013-08-10 7:07 ` Felipe Contreras
2013-08-10 15:15 ` Antoine Pelisse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vioze2kev.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apelisse@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).