Skip to content

Conversation

@FFY00
Copy link
Member

@FFY00FFY00 commented May 28, 2024

Fixes#309

Signed-off-by: Filipe Laíns <lains@riseup.net>
@FFY00
Copy link
MemberAuthor

@jaraco what do you think of this?

Copy link
Member

@jaracojaraco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me. We should add some tests to ensure the use-case is covered. And should we include type annotations?


@property
defpaths(self):
returnself._paths.copy()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we type-annotate this property to be a non-mutable Sequence, and because self._paths is not mutated internally (also treated like a non-mutable Sequence), there's no need to make a copy. But I'm okay either way.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose base paths of MultiplexedPath

2 participants

@FFY00@jaraco