Author pitrou
Recipients eric.araujo, ezio.melotti, ivan_herman, orsenthil, pitrou, python-dev, r.david.murray
Date 2013-01-07.16:58:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357577887.62.0.172220983957.issue14072@psf.upfronthosting.co.za>
In-reply-to
Content
For the record, urlparse still doesn't handle bare "tel" URIs such as "tel:1234":

>>> parse.urlparse("tel:1234")
ParseResult(scheme='', netloc='', path='tel:1234', params='', query='', fragment='')

This is not terribly important since these URLs are not RFC 3966-compliant (a tel URI must have either a global number starting with "+" - e.g. "tel:+1234" - or a local number with a phone-context parameter - e.g. "tel:1234;phone-context=python.org"). Yet, there actual telecom systems producing such non-compliant URIs, so they might be nice to support too.
History
Date User Action Args
2013-01-07 16:58:07pitrousetrecipients: + pitrou, orsenthil, ezio.melotti, eric.araujo, r.david.murray, python-dev, ivan_herman
2013-01-07 16:58:07pitrousetmessageid: <1357577887.62.0.172220983957.issue14072@psf.upfronthosting.co.za>
2013-01-07 16:58:07pitroulinkissue14072 messages
2013-01-07 16:58:07pitroucreate