This is an automated email from the ASF dual-hosted git repository. tomaz pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/libcloud.git
commit e0b0c0a71fc9612f6089b62231d417dd1b3eec82 Author: Tomaz Muraus <[email protected]> AuthorDate: Sat Dec 19 12:19:15 2020 +0100 Add upgrade notes entry. --- docs/upgrade_notes.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/upgrade_notes.rst b/docs/upgrade_notes.rst index c26abbc..e7b3048 100644 --- a/docs/upgrade_notes.rst +++ b/docs/upgrade_notes.rst @@ -64,6 +64,17 @@ Libcloud 3.3.0 cls = get_driver(Provider.EQUINIXMETAL) driver = cls('api_key') +* New ``libcloud.common.base.ALLOW_PATH_DOUBLE_SLASHES`` module level variable + has been added which defaults to ``False`` for backward compatibility reasons. + + When set to ``True``, Libcloud code won't perform any URL path sanitization + and will allow URL paths with double slashes (e.g. + ``/my-bucket//foo/1.txt``). + + This may come handy to the users who have S3 paths which contains double + slashes or similar and are upgrading from Libcloud ``v2.3.0`` or older where + no path sanitization was performed. + Libcloud 3.2.0 --------------
