I can second this. I'm currently using a server with RHEL, and changing the system Python is Bad, but installing it in /usr/local and using eg "python2.4 start-myapp.py" has been fine with no problems.
I also had to make sure that the first time I setup turbogears (or setup-tools) I use "python2.4 setup.py", but after that easy_install works fine. However I am thinking of moving to a Debian based server instead. Ed On 01/02/07, Karl Guertin <[EMAIL PROTECTED]> wrote: > > On 2/1/07, Michael Hannon <[EMAIL PROTECTED]> wrote: > > I played briefly with TG on an Scientific Linux 4.4 (similar to CentOS, > > derived from RHEL) and had some strange problems too. I don't recall > > the details, but I think I kept getting Python 2.3, even though 2.4 > > appeared first in my PATH. > > In general, you should NOT change the system Python on a linux box. > I'm not sure about RHEL*, but it's generally a bad. You should type > out the full ``python2.4`` or, if that's annoying, alias ``python`` to > python2.4 in your shell. In bash, that's a ``alias > python='python2.4'`` in your bashrc. > > * I'm boycotting RPM distros and have been since 1999. I hear so many > "Linux is a PITA, I'm having (packaging problems) on my (RPM distro) > and ...". The only packaging system I've never had a problem with is > Gentoo's portage, but debs are acceptable on a reasonably updated > machine. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
