From ddc3ddd5776091c54337436efedee508b59fd97c Mon Sep 17 00:00:00 2001 From: Senthil Kumaran Date: Sat, 17 Apr 2010 14:33:55 +0000 Subject: [PATCH] Merged revisions 80146 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r80146 | senthil.kumaran | 2010-04-17 20:00:53 +0530 (Sat, 17 Apr 2010) | 3 lines Fix Issue5650 - Update the RFC List in the urlparse module. ........ --- Lib/urlparse.py | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/Lib/urlparse.py b/Lib/urlparse.py index 15a394a0bed..ad7734eb907 100644 --- a/Lib/urlparse.py +++ b/Lib/urlparse.py @@ -1,7 +1,30 @@ """Parse (absolute and relative) URLs. -See RFC 1808: "Relative Uniform Resource Locators", by R. Fielding, -UC Irvine, June 1995. +urlparse module is based upon the following RFC specifications. + +RFC 3986 (STD66): "Uniform Resource Identifiers" by T. Berners-Lee, R. Fielding +and L. Masinter, January 2005. + +RFC 2732 : "Format for Literal IPv6 Addresses in URL's by R.Hinden, B.Carpenter +and L.Masinter, December 1999. + +RFC2396: "Uniform Resource Identifiers (URI)": Generic Syntax by T. +Berners-Lee, R. Fielding, and L. Masinter, August 1998. + +RFC2368: "The mailto URL scheme", by P.Hoffman , L Masinter, J. Zwinski, July 1998. + +RFC 1808: "Relative Uniform Resource Locators", by R. Fielding, UC Irvine, June +1995. + +RFC1738: "Uniform Resource Locators (URL)" by T. Berners-Lee, L. Masinter, M. +McCahill, December 1994 + +RFC 3986 is considered the current standard and any changes to urlparse module +should conform to this. urlparse module is not entirely compliant with this. +The defacto scenarios of parsing are considered sometimes and for backward +compatiblity purposes, older RFC uses of parsing are retained. The testcases in +test_urlparse.py provides a good indicator of parsing behavior. + """ __all__ = ["urlparse", "urlunparse", "urljoin", "urldefrag",