On 8/15/07, Christoph Haas <[EMAIL PROTECTED]> wrote: > > On Wed, Aug 15, 2007 at 06:33:33PM -0000, __wyatt wrote: > > On Aug 15, 10:01 am, Christoph Haas <[EMAIL PROTECTED]> wrote: > > > On Wed, Aug 15, 2007 at 09:02:22AM -0400, Matt Feifarek wrote: > > > > On 8/15/07, Ian Bicking <[EMAIL PROTECTED]> wrote: > > > > > > > Yeah; weird stuff with site-packages or easy-install.pth, perhaps? > > > > Doing python -c "import pylons; print pylons.__file__" might help > > > > debug, > > > > and maybe if you install yolk it'll help explain stuff. > > > > > > > For the (future) record and the next person that has this problem... it > > > > turned > > > > out that one of the boxes was sticking some eggs in /usr/lib/python2.4 > > > > and some > > > > in /usr/local/lib. I don't know what the order of precedence is, but it > > > > fouled > > > > things up for me. > > > > > > > Probably an earlier misconfiguration with setuptools on my part. > > > > > > Morale: never install eggs on a Debian-based system. > > > > I'm curious why you say this, as I've never had a problem installing > > eggs on Ubuntu. > > Old story. I can virtually hear people sigh and say "oh, no, not that > again". :) > > Imagine what happens if you install both a Debian/Ubuntu package > containing a Python module and use setuptools/eggs. You'll have two > versions of the module installed and it depends on the faith of your > PYTHONPATH which of the versions get found. The Debian/Ubuntu package > can be removed. The egg can't (properly). I had such a situation here > because people tried to convince me there is no problem. But of course > there is. And I reinstalled my system since because many of the > Pylons-needing modules were half-borked on my system. Some people even > say they just install core modules but install Pylons and it's dependent > modules by using ez_setup/setuptools. Unless you are *very* careful > (speaking of tightrope walk) that will not work. Python packages in > Debian all have proper dependencies. One day you will install a Python > program and it will pull in the appropriate Debian/Ubuntu packages. Even > for those modules that you may have installed as eggs. > > Chritoph
I run Debian on all my machines and haven't had any problems. I *never* install eggs to the system directories though, only Debian packages are allowed to touch /usr/lib/python2.X, etc. What I do is to use a virtual-python setup in my home directory. It picks up system installed packages just fine, and if I need anything more, easy_install will put them in $HOME/lib/python2.X and not affect the rest of the system. It's easy to blow away $HOME/lib and start over again too if things get too bad. Cheers, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
