Senthil Kumaran orsent...@gmail.com added the comment:
Fixed the wordings in r86296(py3k), r86297(release31-maint) and
r86298(release27-maint).
David, for the examples you mentioned, the first one's parsing logic follows
the explanation that is written. It is correct.
For the second example,
R. David Murray rdmur...@bitdance.com added the comment:
Senthil, no it isn't. There is no way to know a priori that ':80' represents a
port number rather than a path, absent the // introducer for the netloc.
This bug is fixed; I ought to open a new one for the path thing but perhaps I
will
R. David Murray rdmur...@bitdance.com added the comment:
How about this:
- If the scheme value is not specified, urlparse following the syntax
- specifications from RFC 1808, expects the netloc value to start with '//',
- Otherwise, it is not possible to distinguish between net_loc and path
Georg Brandl ge...@python.org added the comment:
I think this is correct: it is the new behavior after the fix for #754016 was
committed.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10226
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Fri, Oct 29, 2010 at 2:15 AM, Georg Brandl rep...@bugs.python.org wrote:
..
I think this is correct: it is the new behavior after the fix for #754016 was
committed.
I agree. I kept the issue open because I cannot
Georg Brandl ge...@python.org added the comment:
That's for Senthil to rephrase as intended :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10226
___
Senthil Kumaran orsent...@gmail.com added the comment:
- Otherwise, it is not possible to distinguish between netloc and path
- components, and would the indistinguishable component would be classified
- as the path as in a relative URL.
+ If the netloc does not start with '//', the
Éric Araujo mer...@netwok.org added the comment:
// is not part of the netloc in RFC terms, it’s a delimiter between components
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10226
New submission from Alexander Belopolsky belopol...@users.sourceforge.net:
The following example in Doc/library/urlparse.rst is wrong
urlparse('www.cwi.nl:80/%7Eguido/Python.html')
ParseResult(scheme='', netloc='', path='www.cwi.nl:80/%7Eguido/Python.html',
params='', query='',
Changes by Georg Brandl ge...@python.org:
--
assignee: d...@python - orsenthil
nosy: +orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10226
___
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
Looks like I've been beaten again by make doctest picking up older python, but
something is not right here:
In Python 2.6.5:
urlparse('www.cwi.nl:80/%7Eguido/Python.html')
ParseResult(scheme='www.cwi.nl', netloc='',
11 matches
Mail list logo