[issue20059] Inconsistent urlparse/urllib.parse handling of invalid port values?

[Robert Collins]

Robert Collins added the comment:

So, I think this is worth applying. The discussion around :ipp etc is irrelevant here: this patch changes large or negative ints to be a valueerror, as non-ints are.

The only question is where. I think this is in the category of 'will only break buggy applications' - applications that already handle ValueError to deal with bad inputs, will not be broken. Applications that depend on ports outside the valid range for ports will be broken, but thats the definition of the bug.

So I propose to apply to 2.7/3.4/3.5/3.6, but I'm going to seek a second opinion.

----------
nosy: +rbcollins

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20059>
_______________________________________