Jason R. Coombs

> > Why do we need the module and filename as multiple args instead of just two? > > I'm catching myself up on this. I think the answer is...

Early in the design, I'd deemed it infeasible implement `path` for anything that's expecting subdirectories, because what does it mean to get a `path` for a directory? And indeed, the...

One issue that was discussed in comments leading up to [this comment](https://github.com/python/importlib_resources/issues/58#issuecomment-713901792) was that, by adding support for subdirectories, functions like `path` and `read_text` could be providing access to content...

> I don't see how - you shouldn't be accepting untrusted input to the `Traversable` API in just the same way as for the functional API. `joinpath("..")` is no more...

> But I believe it uses a different type anyway and only converts to an actual path at the very end In actuality, all `importlib.resources.files()` returns in most cases is...

Apologies for the breakage. It was unintended, but you're right - had we realized there was a dependency on that behavior, we would have released it as a backward-incompatible change...

As I maintain hundreds of projects in the Python ecosystem, maintaining an accurate and meaningful system for tracking attribution and copyright is crucial, and a simple notice "Copyright (year) (person)"...

From pwdyson in #194: > First, let me say thanks for continuing to maintain this project. Without your work to keep this package up to date, what I state below...

And jayaddison: > The way I'd think of it is: think of a book, document or article that has someone's name attached to it as one of the authors. If...

I've been pondering this issue and I have some thoughts. > Copyright, however, is something that large corporations respect and will not remove. I reject this rationale as a good...