I've just updated the contributing page to have a section about dealing with dependencies. The short of it is that CherryPy does not use setuptools and therefore doesn't generate an egg. (The other projects all use setuptools.)
I *believe* that, from the thirdparty directory, you can run easy_install cherrypy and it will build and install an egg for you from the cherrypy directory you have there. Kevin On 10/23/05, Robert Leftwich <[EMAIL PROTECTED]> wrote: > > I've just switched to working from an svn checkout as described in 'Developing > with eggs' from http://www.turbogears.org/community/contributing.html. > Although > the latest TG code is used when running apps it doesn't appear to use the code > from the thirdparty directory of the checkout, e.g. the version of CherryPy > used > when running apps is the 2.1.0_rc2 egg installed by TG 0.8a3 into > /usr/lib/python2.4/site-packages/CherryPy-2.1.0_rc2-py2.4.egg. > > Is there some step I've missed to make this 'just work'? > > Robert > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
