[issue23150] urllib parse incorrect handing of params
New submission from Julian Reschke: urllib.parse tries to special-case params, which have been dropped from the general URI syntax back in RFC 2396 (16 years ago). In most cases this can be worked around by reconstructing the path from both path and params; however this fails for paths that *end* in a semicolon (because it's not possible to distinguish an empty param from an absent param). -- components: Library (Lib) messages: 233312 nosy: julian.resc...@gmx.de priority: normal severity: normal status: open title: urllib parse incorrect handing of params type: behavior ___ Python tracker <http://bugs.python.org/issue23150> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23150] urllib parse incorrect handing of params
Julian Reschke added the comment: An example URI for this issue is: http://example.com/; The RFC 3986 path component for this URI is "/;". After using urllib's parse function, how would you know? (I realize that changing behavior of the existing API may cause problems, but this is an information loss issue). One ugly, but workable way to fix this would be to also provide access to a "RFC3986path" component. -- ___ Python tracker <http://bugs.python.org/issue23150> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
