On Wed, Jun 18, 2008 at 2:19 PM, Chris <[EMAIL PROTECTED]> wrote: > > On Jun 17, 2:41 am, "Mike Orr" <[EMAIL PROTECTED]> wrote: >> On Mon, Jun 16, 2008 at 3:48 PM, Chris Spencer <[EMAIL PROTECTED]> wrote: >> >> > Turns out "easy_install PasteDeploy" installs to >> > site-packages/PasteDeploy-1.3.1-py2.5.egg/paste/deploy instead of >> > site-package/paste/deploy. Not sure why that's the default behavior... >> >> It's installing it as an egg. It puts an entry in >> site-packages/easy_install.pth to make python add the egg to sys.path. >> That's what easy_install always does. > > Sorry, but this still seems unintuitive. I have a fairly vanilla > setup, and it failed to add the appropriate path to sys.path.
Then easy_install either failed to finish it's work, or you're getting interference from some other Python environment installed on the system. Neither of these is easy_install's fault per se. As I said, we'll need to see the output from easy_install in order to troubleshoot what went wrong. If you're complaining that the whole design of the egg system and easy_install.pth is overly complex, I agree. I don't like every single package getting a separate entry in sys.path; the old short sys.path was much more convenient. But the egg developers insisted they wanted it this way, and since projects with dependencies (like Pylons) need eggs and auto-installation or they'd never get off the ground, there's no alternative to the complexity. -- 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 -~----------~----~----~----~------~----~------~--~---
