Closed schneidemar closed 7 months ago
See #77 for context. I'm not sure if we converged on the correct solution or not.
I merged a fix to master I'll update here after deploying new version
New Version deployed 0.5.1 with this card fix
Seems to be working in the new version, thanks!!!
When creating an S3Path object with a path, which contains characters not representable by URIs, the to_uri function apparently call urlencode to encode those characters. This is fine. But when using this URI to create a new instance of S3Path, it should call urldecode, to decode the URI to the correct path. This is currently not done and results in errors of S3 being not able to find the key (of course, the key is wrong.) Example
Workaround is of course to manually call urldecode on the string first, but IMO S3Path.from_uri should handle this, as it also calls urlencode when creating the URI.