On Thu, Dec 15, 2011 at 12:20 PM, Christoph Zwerschke <[email protected]> wrote: > > I guess the actual difficulties of raw recruits is that they don't > understand the Python packaging system and virtual envs, and may not even > have setuptools or virtualenvs installed. In TG1 we tried to solve this > problem with a tgsetup.py script which also installed setuptools. But this > caused more problems than it solved. >
I agree, tgsetup.py causes only more confusion. > I still think it's better if the docs properly explain and motivate only one > recommended way of installing. If we provide two different methods or even > two different variants of the package, I fear it will evoke confusion and > maintenance trouble. > I still think that making install process as easy as possible is a really important issue, but I can see your point. If we really want to be stuck with the private index only solution we should update the TG Book as quickly as possible so that people won't follow the wrong install guide. And I would also suggest to add to the quickstart template a new command on setup.cfg like "python setup.py tg-install" that installs the right TurboGears version for the project from the private index. So that installing a project is as easy as: python setup.py tg-install python setup.py develop -- 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.
