➜

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 martin.panter
Recipients Serhiy Int, SilentGhost, martin.panter, orsenthil
Date 2016-02-19.01:37:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455845879.03.0.569363119491.issue26381@psf.upfronthosting.co.za>
In-reply-to
Content 
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().
History
Date User Action Args
2016-02-19 01:37:59martin.pantersetrecipients: + martin.panter, orsenthil, SilentGhost, Serhiy Int
2016-02-19 01:37:59martin.pantersetmessageid: <1455845879.03.0.569363119491.issue26381@psf.upfronthosting.co.za>
2016-02-19 01:37:59martin.panterlinkissue26381 messages
2016-02-19 01:37:58martin.pantercreate