On 7/14/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > *shudder*. Please don't. pkg_resources needs to be a singleton, partly > because sys.path is a singleton, and partly because there needs to be a > single place to register adapters for PEP 302 loaders and importers, and in > the future, egg listeners.
Ahh, OK. I hadn't looked closely at all that was going on in there. > If you guys *really* want to do this, what we need to do is create a > super-simple "mini-Me" form of pkg_resources, that provides exactly two > functions: resource_string and resource_stream. I don't really want to do this. I consider it entirely likely that I'll produce a couple of patches for other projects to make them zip-safe. I don't know yet if those projects will take the patches and the setuptools dependencies... we'll see when that time comes. Being a believer in YAGNI, I wouldn't have brought this up until someone actually told me "nope, I won't do that." The pkg_resources_lite idea seems reasonable, should this discussion leave the hypothetical. Kevin _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
