> Second, I have been using windows XP for training and development but I now 
> need to move the application to staging and production. I want to run this on 
> Linux and have tried to install on Centos. I had some initial issues 
> concerning Python 2.4 and have been delaying installation until TG2 is 
> stable. My question now is Centos / Red Hat a good platform for TG2 or should 
> I look at Ubuntu?

I wouldn’t consider Ubuntu for a server environment.  I’ve run Red Hat ES 
servers, and CentOS servers, but to date my favourite continues to be Gentoo.  
More heavily optimized for the hardware architecture, better configuration of 
optional package components, and multi-versioning (install Python 2.3 + 2.4 + 
2.5 + 2.6 + 3.1, or PHP 4 + 5 on one box, etc.)

> This really drives me crazy.  I like TurboGears, and I hate TurboGears, 
> because it is always a nightmare to install TurboGears.

Historically this has been a problem, too.  This is how I have to install 
TG2.0b3 to get my projects working:

        http://gist.github.com/287670

A script like the above may be useful for you.  (Include Extremes in the 
pre-TurboGears easy_install line.)

> Victor, I want to reply in a very sarcastic fashion to your rant. I won't, 
> though.

Awesome.

> I’ll simply say that getting TG working is very easy for me, and always has 
> been. The only times I've ever had issue are when something happens outside 
> of TG control, such as what appears to have happened with you.

This is a non-answer.  The ‘it works for me’ defence doesn’t improve customer 
relations.

> Now, looking at your error report, you've left out pretty much everything you 
> can possibly leave out, and still claim to have submitted a trouble report. 
> You’ve left out which version of Linux you're using, and which version of 
> Python you're using. Both of those are normally quite important to include, 
> since they can tell us what's going on.

At least there isn’t a screenshot attached as a word document.  Obviously you 
didn’t need the above information, however, to help solve the problem.

> The decision to date has been that it is more important to provide a 
> consistent  environment that can be repeatably installed than to fix this 
> issue, since other people and companies are using and relying on this private 
> PyPI.

A broken release is a broken release, and there is no obvious mention of the 
problem or work-around in the docs or site.  (Esp. considering a large number 
of developers use Macs, and the current version of the operating system 
includes 2.6.)

        — Alice.

-- 
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.

Reply via email to