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 eric.araujo
Recipients eric.araujo
Date 2009-04-25.19:12:37
SpamBayes Score 0.00013884735
Marked as misclassified No
Message-id <1240686759.57.0.0410680082249.issue5843@psf.upfronthosting.co.za>
In-reply-to
Content
Docstring for urlunparse says:
    """Put a parsed URI back together again.  This may result in a
    slightly different, but equivalent URI, if the URI that was parsed
    originally had redundant delimiters, e.g. a ? with an empty query
    (the draft states that these are equivalent)."""

“Draft” here refers to RFC 1808, superseded by 3986. However, RFC 3986
(section 6.2.3) states:
“Normalization should not remove delimiters when their associated
component is empty unless licensed to do so by the scheme  
specification.  For example, the URI "http://example.com/?" cannot be  
 assumed to be equivalent to any of the examples above.  Likewise, the 
  presence or absence of delimiters within a userinfo subcomponent is  
 usually significant to its interpretation.  The fragment component is 
  not subject to any scheme-based normalization; thus, two URIs that   
differ only by the suffix "#" are considered different regardless of   
the scheme.”

I guess we need some tests here to check compliance.
History
Date User Action Args
2009-04-25 19:12:39eric.araujosetrecipients: + eric.araujo
2009-04-25 19:12:39eric.araujosetmessageid: <1240686759.57.0.0410680082249.issue5843@psf.upfronthosting.co.za>
2009-04-25 19:12:38eric.araujolinkissue5843 messages
2009-04-25 19:12:37eric.araujocreate