I noticed that, when setting up dependencies in setup.py, subsequent RPM builds (which do not use eggs) were causing the application to fail, citing a failed resource dependency. I traced this down to pkg_resources, which explciitly checks to see if the dependency has a matching egg by checking the easy-install.pth file. Since RPMs can't/ don't manage this file, its failing to find any of the dependencies.
Is there anyway to just outright skip this check? I.e., a config flag or such? I didn't notice any, but that doesn't mean its not there-- and I was wondering if anyone else may have run into and solved this issue. Andrew -- 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.
