Éric Araujo <mer...@netwok.org> added the comment: >From RFC 3986, section 6.2.3 “Scheme-Based Normalization”:
The syntax and semantics of URIs vary from scheme to scheme, as described by the defining specification for each scheme. Implementations may use scheme-specific rules, at further processing cost, to reduce the probability of false negatives. For example, because the "http" scheme makes use of an authority component, has a default port of "80", and defines an empty path to be equivalent to "/", the following four URIs are equivalent: http://example.com http://example.com/ http://example.com:/ http://example.com:80/ IOW, the empty string is not an invalid port. The patch fixes that. It includes tests but lacks a doc update. I think it works for https URIs too, but I’d like a test to make sure. ---------- resolution: invalid -> stage: needs patch -> patch review status: pending -> open versions: +Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10860> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com