[issue23759] urllib.parse: make coap:// known

2015-03-24 Thread chrysn
New submission from chrysn: The CoAP protocol (RFC 7252) registers the new URI schemes coap and coaps. They adhere to the generic RFC3986 rules, and use netloc and relative URIs. Therefore, please add the 'coap' and 'coaps' schemes to the uses_relative and uses_netloc lists in urllib.parse.

[issue23759] urllib.parse: make coap:// known

2015-03-24 Thread Martin Panter
Martin Panter added the comment: I would like to see these hard-coded white lists of URL schemes eliminated as much as possible. Here’s some related issues: * Issue 16134: rtmp, rtmpe, rtmps, rtmpt * Issue 18828: redis, also proposing to urljoin() arbitrary schemes * Issue 15009: yelp * Issue

[issue23759] urllib.parse: make coap:// known

2015-03-24 Thread chrysn
chrysn added the comment: i wholeheartedly agree that a generic solution would be preferable, but as you pointed out, that needs to be well-researched. until there is a concrete plan for that, please don't let the ideal solution get in the way of a practical update of the uri scheme list.

[issue23759] urllib.parse: make coap:// known

2015-03-24 Thread R. David Murray
R. David Murray added the comment: I too would like to see this issue dealt with generically. I believe the last time we discussed it the barrier was backward compatibility and which RFCs we actually support :(. Fixing it generically will require a well thought out and well researched

[issue23759] urllib.parse: make coap:// known

2015-03-24 Thread Demian Brecht
Demian Brecht added the comment: I'm also +1 to handling this generically and agree that a well thought out and researched proposal would be required. I did mention in #18228 (http://bugs.python.org/issue18828#msg238363) that I think that a short term solution to this problem could be to