Previously Mike Orr wrote: > > On Thu, Oct 9, 2008 at 11:23 PM, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > > > > Previously Christopher Barker wrote: > >> So, is there a way to turn off the use of pkg_resources in paste? > > > > No, paste relies on it to handle entry points in various places. That is > > a very popular pattern that more and more things are starting to use. > > Popular, but it's still on unstable ground because Setuptools isn't > built into Python yet,. This is just one of a series of problems > people have when installing Pylons. It's worth remembering that there > aren't many packages that depend on others, much less a multilevel > dependency -- Pylons and TurboGears are about it.
The zope libraries are much larger and have much more (too many) dependencies than Pylons and Turbogears, by several factors. > Unfortunately that puts the onus on us to either fix the Setuptools > problems ourselves, complain to the developers, or make Pylons/Paste > less dependent on Setuptools. What exactly are 'the setuptools problems'? Entry points and namespaces are very practical and I wouldn't want to loose them. All the installation and index-handling logic in setuptools is probably best replaced. > The whole idea of importing an application by entry point when you > already know what the module is called and it's already been installed > is kind of funny. But in this case, the problem seems to be not entry > points or namespace packages but pkg_resources.require. > > The purpose of pkg_resources.require, according to its documentation, > is to guarantee version dependencies are satisfied and to activate > eggs that are along sys.path but not on it. I tend to think this > whole concept is obsolete now that you can install different versions > into different virtual environments. I don't know of anybody who has > installed multiple versions of a package into the same directory, and > then had two applications that each used pkg_resources.require to > activate a different version. On the other hand, I know people who > have hesitated to use pkg_resources.require because that makes the > application or library depend on Setuptools. I've never used multi-version support or resources.require, and I agree that we have better tools now. I think a problem of setuptools is that it does too many things, and not all of them very well: - namespace handling - entry points - multi-version egg installation - building and uploading eggs - egg installation - remote package searching and downloading pyinstall already does a better job at the last two. A simple implementation of the first two in the standard library would go a long way to improving things. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
