Author: andrew.kuchling Date: Fri Apr 30 02:49:09 2010 New Revision: 80642 Log: Always add space after RFC; reword paragraph Modified: python/trunk/Lib/urlparse.py Modified: python/trunk/Lib/urlparse.py ============================================================================== --- python/trunk/Lib/urlparse.py (original) +++ python/trunk/Lib/urlparse.py Fri Apr 30 02:49:09 2010 @@ -8,21 +8,22 @@ 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. +RFC 2396: "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 2368: "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. +RFC 1738: "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 +RFC 3986 is considered the current standard and any future changes to +urlparse module should conform with it. The urlparse module is +currently not entirely compliant with this RFC due to defacto +scenarios for parsing, and for backward compatibility purposes, some +parsing quirks from older RFCs are retained. The testcases in test_urlparse.py provides a good indicator of parsing behavior. """