Senthil orsent...@gmail.com added the comment:
Georg, shall I take up this one?
--
nosy: +orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5650
___
Georg Brandl ge...@python.org added the comment:
Yes, you've probably a better understanding of what differentiates an
URL and URI than me :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5650
Éric Araujo mer...@netwok.org added the comment:
More precisely, RFC 1738 and 1808 are updated by RFC 2396, which is in
turn obsoleted by RFC 3986 (which obsoletes 1808 too but only updates
1738). Eliminating the obsoleted ones leaves us with two references,
RFC 1738 and RFC 3986. I’m going to
Éric Araujo mer...@netwok.org added the comment:
Sorry, my logic was flawed: RFC 1808 is not obsoleted either, so it
leaves us with 1738, 1808 and 3986.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5650
Éric Araujo mer...@netwok.org added the comment:
Included patch for this issue. There is some diff noise because of
paragraph wrapping. I don’t know whether my seealso addition is
correctly formatted (the title spans two lines) because of a Sphinx bug
on my machine. Thanks for reviewing.
Changes by Daniel Diniz aja...@gmail.com:
--
keywords: +easy
stage: - needs patch
type: - behavior
versions: -Python 2.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5650
___
New submission from Mitchell Model m...@acm.org:
The documentation of urlparse in Python2 and urllib.urlparse in Python3
refers to three RFC's, the last of which (RFC 2396) says that it
supersedes the other two and, in fact, clicking on the links to the other
two doesn't work; the link and
