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.

Title: Add 'geo' URI scheme (RFC 5870) to urllib.parse.uses_params
Type: enhancement Stage: needs patch
Components: Library (Lib) Versions: Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Serhiy Int, SilentGhost, martin.panter, orsenthil
Priority: normal Keywords:

Created on 2016-02-18 12:27 by Serhiy Int, last changed 2022-04-11 14:58 by admin.

Messages (2)
msg260475 - (view) Author: SilentGhost (SilentGhost) * (Python triager) Date: 2016-02-18 18:50
Here is the spec:
msg260495 - (view) Author: Martin Panter (martin.panter) * (Python committer) Date: 2016-02-19 01:37
Sounds reasonable to me, and thanks for the reference.

But it would be nice to find a way for this to work sensibly with arbitrary schemes, in the same spirit as Issue 18828. Would it break anything if we removed the uses_params list altogether? I notice it already works if you omit the scheme:

>>> urlparse("48.198634,16.371648;crs=wgs84")
ParseResult(scheme='', netloc='', path='48.198634,16.371648', params='crs=wgs84', query='', fragment='')

If a programmer doesn’t want to split of the “params” they can always use urlsplit() instead of urlparse().
Date User Action Args
2022-04-11 14:58:27adminsetgithub: 70569
2016-02-19 01:37:59martin.pantersetnosy: + martin.panter
messages: + msg260495

type: enhancement
stage: needs patch
2016-02-18 18:50:06SilentGhostsetnosy: + SilentGhost, orsenthil
messages: + msg260475
2016-02-18 12:27:14Serhiy Intcreate