This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yuhl
Recipients orsenthil, yuhl
Date 2009-01-19.09:50:08
SpamBayes Score 0.0052155056
Marked as misclassified No
Message-id <1232358609.79.0.478133208006.issue4962@psf.upfronthosting.co.za>
In-reply-to
Content
> Do you encounter any errors or weird behaviors while using nfs url?

Do you mean: Do I have problem using the python module in conjunction of
urlparse ?
No, because, I'm not yet using it. But I would like to do it. And I find
it strange that it can not find the host by itself.

>('nfs', '', '//server//a/b/c/d/e/f', '', '', '')
>If you have done the research already, can you please explain what
>difference will adding 'nfs' to uses_netloc do in urlparse.py.

As much as I've looked at the code, the uses_netloc provide an easy way
to tell urlparse.py if such scheme as nfs is composed
by a net location (host[:port]). Which is the case. Modifying
uses_netloc by addind 'nfs' into it will transform the following:
nfsurl : 'nfs://server//a/b/c/d/e/f'
in  urlparse from:
('nfs', '', '//server//a/b/c/d/e/f', '', '', '')
to
('nfs', 'server', '//a/b/c/d/e/f', '', '', '')
History
Date User Action Args
2009-01-19 09:50:11yuhlsetrecipients: + yuhl, orsenthil
2009-01-19 09:50:09yuhlsetmessageid: <1232358609.79.0.478133208006.issue4962@psf.upfronthosting.co.za>
2009-01-19 09:50:08yuhllinkissue4962 messages
2009-01-19 09:50:08yuhlcreate