On Thu, Mar 26, 2009 at 12:22 PM, Barry Warsaw <ba...@python.org> wrote: > On Mar 26, 2009, at 1:54 PM, Guido van Rossum wrote: >> 2009/3/26 Toshio Kuratomi <a.bad...@gmail.com>: >>> Depending on the definition of a "resource" there's additional >>> information that could be needed. For instance, if resource includes >>> message catalogs, then being able to get the base directory that the >>> catalogs reside in is needed for passing to gettext. >> >> Well the whole point is that for certain loaders (e.g. zip files) >> there *is* no base directory. If you do need directories you won't be >> able to use PEP-302 loaders, and you can just use >> os.path.dirname(<some_module>.__file__). > > One thing that /would/ be helpful though is the ability to list all the > resources under a specific package path. This is (I think) one use case > that pkg_resource fails to support and it's the one place that I've had to > drop down to file system introspection. > > Think: the package-y flavor of os.listdir(os.path.dirname(package.__file__))
Good idea. Can I suggest that API this takes a glob-style pattern? (Or to be fully general, a list of patterns and a list of exclusion patterns.) -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
