Senthil Kumaran added the comment: On Saturday, January 3, 2015 at 12:46 AM, Julian Reschke wrote: > An example URI for this issue is: > > http://example.com/; > > The RFC 3986 path component for this URI is "/;". I think, a stronger argument might be desirable (something like a real world scenario wherein a web app can construct such an entity) for a path that ends in a semi-colon for breaking backwards compatibility.
OTOH, making it RFC 3986 compliant itself is a good enough argument, but it should be applied in total and the whole module should be made compatible instead of pieces of it. There is a bug to track it. You can mention this instance for the desired behavior in that ticket too (and close this ticket if this desired behavior is a subset). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23150> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
