Fix TypeError in MultiplexedPath.joinpath calls#11188
Conversation
Change `path.joinpath(*multiple_args)` to iterative `.joinpath()` calls. In newer Python versions, `epath.resource_path` returns an `importlib.resources.readers.MultiplexedPath` whose `joinpath` method only accepts a single positional argument in some execution environments (or via certain compatibility patches). Unpacking multiple path components into it results in a TypeError. Iteratively calling `.joinpath` resolves the error and remains fully compatible with standard `pathlib.Path` objects. Co-authored-by: tomvdw <4160552+tomvdw@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Fix TypeError in MultiplexedPath.joinpath calls
Change
path.joinpath(*multiple_args)to iterative.joinpath()calls.In newer Python versions,
epath.resource_pathreturns animportlib.resources.readers.MultiplexedPathwhosejoinpathmethod onlyaccepts a single positional argument in some execution environments (or via
certain compatibility patches). Unpacking multiple path components into it
results in a TypeError.
Iteratively calling
.joinpathresolves the error and remains fullycompatible with standard
pathlib.Pathobjects.PR created automatically by Jules for task 16329133361061968178 started by @tomvdw