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 amrith, eric.smith, martin.panter, orsenthil
Date 2016-12-01.00:31:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480552271.92.0.614790089808.issue28841@psf.upfronthosting.co.za>
In-reply-to
Content
The Python documentation refers to RFC 3986, which allows an empty port string introduced by a colon, although it recommends against it: <https://tools.ietf.org/html/rfc3986#section-3.2.3>

The “port” subcomponent of “authority” is designated by an optional port number in decimal following the host and delimited from it by a single colon. . . . URI producers and normalizers should omit the port component and its “:” delimiter if “port” is empty . . .

What problem are you trying to solve by raising an error?

See also Issue 20059, where accessing the “port” field now raises ValueError for out-of-range values, and Issue 20271, discussing invalid URL handling more generally.
History
Date User Action Args
2016-12-01 00:31:11martin.pantersetrecipients: + martin.panter, orsenthil, eric.smith, amrith
2016-12-01 00:31:11martin.pantersetmessageid: <1480552271.92.0.614790089808.issue28841@psf.upfronthosting.co.za>
2016-12-01 00:31:11martin.panterlinkissue28841 messages
2016-12-01 00:31:11martin.pantercreate