At 11:27 PM 3/26/2009 +0000, Paul Moore wrote: >> What I'd really like is essentially some form of "virtual filesystem" >> access to stuff addressed relative to a Python package name, P.J. Eby responded: > Note that relative to a *Python package name* isn't quite as useful, > due to namespace packages. To be unambiguous as to the targeted > resource, one needs to be able to reference a specific project, and > that requires you to go off the name of a module *within* a > package. For example, 'zope.somemodule' rather than just 'zope'. I would expect it to be *most* important then. If I know for sure that an entire package is all together in a single directory, I can just use that directory. If I want all xxx files used by zope, then ... I *do* want information on the duplicates, and the multiple locations. -jJ
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4