On 10/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I was inititally excited to look at TG. I have recently evaluated > Django, RubyOnRails, and Zope. However, installing this toolkit is a > nightmare. Here are some notes: > > 1. TG does -not- install with python2.3, despite some notes that this > might be possible. The Kid egg: kid-0.7adev_r186-py2.4.egg requires > py2.4, and this is the only version of kid >= 0.7, the version required > by setuptools.
This is what the website says about 2.3: Python 2.3 TurboGears builds rely on 2.4, and there are some 2.4 features used in TurboGears. If you would like TurboGears on Python 2.3, please speak up on the mailing list. If there are enough people who need 2.3 support (especially if they're willing to help iron out the kinks with 2.3!), we can certainly consider it. For now, the out-of-the-box experience requires 2.4. -- To me that doesn't read that you can install it under 2.3. It's just that the number of 2.4-specific bits are small enough that it may be possible to make a 2.3 compatible version, if someone's willing to work it out. > 2. TG does (obviously) install with python2.4. But there are many > unresolved dependency issues. > a. psycopg2.4 is not yet in debian testing, so postgres access is out > b. the biggest nit of all is that if an egg has dependencies, and you > subsequently install those depenencies, (sqlite, python2.4-sqlite, > python2.4-sqlite2), then you -must- 'rm -rf' the > site-packages/SQLObject-0.7b1dev-py2.4.egg and perform a subsequent > easy install in order for the dependency to be recognized (python > ez_setup.py -f http://www.turbogears.org/download/index.html > --script-dir /usr/local/bin TurboGears) I didn't do anything special to make sqlite run on my machine... it's not even an egg on my machine. > c. after fighting thru all that, i am finding that i still cannot get > TG to operate: > > [EMAIL PROTECTED]:~/working/turbogear/wiki20$ turbogears-admin.py sql > create > Traceback (most recent call last): > File "/usr/local/bin/turbogears-admin.py", line 4, in ? > pkg_resources.run_script('TurboGears==0.5.1', > 'turbogears-admin.py') > File > "/usr/local/lib/python2.4/site-packages/setuptools-0.6a5-py2.4.egg/pkg_resources.py", > line 407, in run_script > self.require(requires)[0].run_script(script_name, ns) > File > "/usr/local/lib/python2.4/site-packages/setuptools-0.6a5-py2.4.egg/pkg_resources.py", > line 914, in run_script > raise ResolutionError("No script named %r" % script_name) > pkg_resources.ResolutionError: No script named 'turbogears-admin.py' Something must not have installed properly... until today's 0.8 release, there was definitely a turbogears-admin.py script. (Now, there's a tg-admin command that is generated by setuptools). > In summary, although I really like the simple MVC representation in TG, > the simple fact is that I have had 10x more trouble installing this > suite than I have had with Django, RubyOnRails, and Zope put together. > I'm putting TG back on the shelf and looking into Quiote next. I'm sorry to hear that installation's been a problem for you. Most people who've had troubles have had those problems because of non-root installations and the like. I didn't see a "sudo" in your installation command, but it also sounds like you didn't have permissions troubles when installing. You might try a quick attempt at installing 0.8 and see if it runs for you. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
