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 terry.reedy
Recipients daenney, orsenthil, r.david.murray, terry.reedy
Date 2013-11-01.23:39:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383349180.57.0.632966909102.issue19451@psf.upfronthosting.co.za>
In-reply-to
Content
The 3.4 urllib.parse.urlparse doc says "The module has been designed to match the Internet RFC on Relative Uniform Resource Locators. It supports the following URL schemes: <list of 24, including 'file:'>".

To me, 'support' means 'accept every valid URL for the particular scheme' but not necessarily 'reject every URL that is invalid for the particular scheme'.

The other RFCs references are these: 
"Following the syntax specifications in RFC 1808, urlparse recognizes a netloc only if it is properly introduced by ‘//’." and
" The fragment is now parsed for all URL schemes (unless allow_fragment is false), in accordance with RFC 3986."

I currently see this, at best, as a request to deprecate 'over-acceptance', to be removed in the future. But if there are urls in the wild that use _s, then practicality says that this should be closed as invalid.
History
Date User Action Args
2013-11-01 23:39:40terry.reedysetrecipients: + terry.reedy, orsenthil, r.david.murray, daenney
2013-11-01 23:39:40terry.reedysetmessageid: <1383349180.57.0.632966909102.issue19451@psf.upfronthosting.co.za>
2013-11-01 23:39:40terry.reedylinkissue19451 messages
2013-11-01 23:39:40terry.reedycreate