Posted on October 25th, 2005 by Kevin Dangoor

TurboGears 0.8a4 released

This is a minor update to TurboGears, including 3 project upgrades and a fix. The use of setuptools 0.6a6 means that it should now be much easier to do a non-root installation of TurboGears on Unix-like systems.

Here’s the changelog entry:

0.8a4 (October 25, 2005)

Project Updates

  • setuptools 0.6a6
  • CherryPy 2.1 final
  • MochiKit 1.0

Fixes

  • On some servers, TurboGears can take a minute to start answering
    connections due to the way the OS handles incoming connections to
    ports that have nothing listening on them.

9 Responses to “TurboGears 0.8a4 released”

Baruch Even on October 25th, 2005 6:40 pm:

I’ve recently started up with TurboGears and it is a very nice framework which is a pleasure to work with, quite natural in most aspects.

The only trouble that I have is with SQLOjects. Need to drop the RDBMS mentality and understand how to work with it properly.

All in all, a job well done!

Dave on October 25th, 2005 8:00 pm:

Are you sure it’s updated to CherryPy-2.1.0 final? I don’t really know much about how setuptools works, but the download page lists a link to CherryPy-2.1.0_rc2-py2.4.egg. I don’t really know if that’s important though, since when I did an update from 0.5.1 it didn’t seem to get even that non-final version of CherryPy for me, leaving me with CherryPy-2.1.0_betadev-py2.4.egg in my site packages so I seem to be having weirdness all my own and can’t guess if others will get the latest CherryPy automatically. I guess I’ll just be grabbing CherryPy 2.1.0-final manually :) .

tazzzzz on October 25th, 2005 10:28 pm:

You’re right. I had uploaded the egg, but neglected to change the egg link.

setuptools, at this stage, doesn’t delete the old versions (you could even use them, if you want, by doing a multiversion install). So, you should make sure that you don’t have a newer one and the older one as well.

easy_install -f http://www.turbogears.org/download/index.html -U cherrypy

*should* get you CherryPy 2.1 final, if the standard TurboGears upgrade didn’t do it for you.

Sam on October 27th, 2005 1:04 am:

http://turbogears.org/download/windows.html

I just installed on a fairly clean Windows box.
1. Python 2.4.1
2. ez_setup
3. ez_setup call for TurboGears (no errors)

So far, not much difference from Debian other than downloading the Python 2.4.1 MSI instead of using apt-get.

I headed over to the “Getting Started” page:
http://turbogears.org/docs/gettingstarted.html

tg-admin worked just fine to create a new project “learnpy”.

However, trying to run the “python learnpy-start.py” script bailed straight away:

C:\Projects\learnpy>python learnpy-start.py

Traceback (most recent call last):
File “learnpy-start.py”, line 2, in ?
import pkg_resources
ImportError: No module named pkg_resources

I’m not new to programming, just Python. What step am I missing? I have TurboGears just fine on Debian.

Sam on October 27th, 2005 1:23 am:

You know, something about passing 1 AM turns me into an imbecile incapable of using Google to solve my own problems. In this case, it turns out my Windows box wasn’t as clean as I thought. I had Python22 lurking.

daf on October 27th, 2005 12:51 pm:

Hi.

Is there any other way to install TurboGears without using the .egg stuff? it breaks some of my existing apps. I’ve already tried to run tg-admin with the packages needed installed in a traditional fashion but it is unable tu run, it says it needs packages already installed but I think it needs them installed like eggs.. Sorry if this is already solved.

Actually my apps run ok in development but when trying to deploy (with py2exe) into an executable, seems to not find packages installed as eggs (which are mostly the same as the ones used by turbogears ;) ..

tazzzzz on October 27th, 2005 1:14 pm:

Things would be a mess without eggs. Troubleshooting anything would be a nightmare, because we wouldn’t know which versions of which packages are installed. Upgrading would be a pain, too. TurboGears *could* exist without eggs, but it would be a lot less pleasant.

I package up my own app with py2app/py2exe. I tossed some guidelines onto the py2exe wiki:
http://starship.python.net/crew/theller/moin.cgi/ExeWithEggs

New_to_Python on July 1st, 2007 9:11 am:

C:\Projects\Wiki20>pyhon start-wiki20.py
Traceback (most recent call last):
File “learnpy-start.py”, line 2, in ?
import pkg_resources
ImportError: No module named pkg_resources

I broke my head trying to figure this one out… It turns out that I had python22 previously installed…. Uninstalling this help me…
If this helps anyone…..
Thanks

Eluem on August 27th, 2007 12:21 pm:

I really need help…
I’ve been trying to figure this out all day. I’m not really new to python, just to compiling python stuff. As a test i wanted to try and make a simple python script that could print __file__ with this code:

print __file__
raw_input()

This works normally, but once compiled using py2exe it doesn’t. This is apparently because all names such as __file__ EXCEPT __name__ are not kept intact when compiling. This I understand. What I don’t understand is how to fix this. I’ve tried to do something like this instead:

from pkg_resources import resource_string
print resource_string(__name__, ‘print_test.exe’)
raw_input()

When I do this I get the following error:
ImportError: No module named pkg_resources

Any help at all would be appreciated, thank you.