On Fri, Oct 10, 2008 at 2:14 PM, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > 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.
Chris's current problem is "module 'middleware.py' not found". The traceback doesn't say which middleware.py, in which package, or who's asking for it. This happens sometime while loading the application. I've sometimes had a similar problem where it tells you what it can't find, but not why it's looking for that in the first place. The information is buried in local variables which aren't displayed, and sometimes it's difficult to get pdb running at that point to find out. In this case, the problem only happens when running the py2app-generated version of the application, not when running it from the command line. And py2app creates its own top-level executable, so it's a bit difficult to run the application under pdb. The specific function seems to be ``entry.load()``, where ``entry`` is something that was returned by ``pkg_resources.require()``. But the exception is several levels below that. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
