[issue16713] "tel" URIs should support params

2012-12-24 Thread Senthil Kumaran
Senthil Kumaran added the comment: Fixed in all codelines. Thank you! -- assignee: -> orsenthil resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue16713] "tel" URIs should support params

2012-12-24 Thread Roundup Robot
Roundup Robot added the comment: New changeset d002a2e46383 by Senthil Kumaran in branch '3.2': Fix issue16713 - tel url parsing with params http://hg.python.org/cpython/rev/d002a2e46383 New changeset 727f26d1806f by Senthil Kumaran in branch '3.3': Fix issue16713 - tel url parsing with params h

[issue16713] "tel" URIs should support params

2012-12-21 Thread Éric Araujo
Éric Araujo added the comment: It’s easy sure, but I think it’s still a bug :) -- nosy: +eric.araujo ___ Python tracker ___ ___ Python

[issue16713] "tel" URIs should support params

2012-12-18 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: I don't know whether 'tel' is a common scheme, but it's easy to add it to urlparse from the outside: >>> urlparse.uses_param.append('tel') >>> urlparse.urlparse('tel:7042;phone-context=example.com') ParseResult(scheme='tel', netloc='', path='7042', param

[issue16713] "tel" URIs should support params

2012-12-18 Thread Antoine Pitrou
New submission from Antoine Pitrou: RFC 3966 (http://tools.ietf.org/html/rfc3966) defines the tel URI and its parameters. However, urlparse / urllib.parse doesn't recognize "tel" URIs as taking parameters: >>> urlparse.urlparse('tel:7042;phone-context=example.com') ParseResult(scheme='tel', ne