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 martin.panter
Recipients gvanrossum, martin.panter, orsenthil, serhiy.storchaka, vstinner, yselivanov
Date 2015-03-02.01:10:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I suspect the proposed patch here would make some of the special error handling for the “port” property redundant, and would compete with my patch for Issue 20059, which raises ValueError in more cases when “port” is accessed, rather than returning None.

There should also be test cases (and maybe documentation or fixes?) to illustrate the behaviour of parsing:

* http://[fe80::a%25en1] (RFC 6874-style scoped IPv6 address with zone identifier)
* http://[v1.fe80::a+en1] (RFC 3986 IPvFuture format, using <> style address)
Date User Action Args
2015-03-02 01:10:53martin.pantersetrecipients: + martin.panter, gvanrossum, orsenthil, vstinner, serhiy.storchaka, yselivanov
2015-03-02 01:10:53martin.pantersetmessageid: <>
2015-03-02 01:10:53martin.panterlinkissue20271 messages
2015-03-02 01:10:53martin.pantercreate