On 1/24/06, Victor Kryukov <[EMAIL PROTECTED]> wrote: > On the positive note - comments in the turbogears.util helps a lot!
Hopefully, there will be more of that soon enough (that's what the API docs discussion is all about). > The whole process of getting the latest version of TurboGears via SVN > still has a lot of mystery in it, though: I didn't quite get the > relationship between SVN and easy_install (is there any doc which > explains this relationship)? > > In particular, am I right that: > > 1) After svn update in turbogears root dir, I'll get the latest trunk > version of turbogears AND the latest trunk versions of corresponding > thirdparty modules (true/false?) Not exactly. The thirdparty directory is a set of svn:externals. You can see them by running this at the top level directory of the project: svn propget svn:externals . I set the externals to follow whatever it is we're targeting at that point. For a couple of projects (CP and Kid), we're following the trunk now. For others, we're using a specific release. > 2) After each svn update, I should manually run 'python setup.py > develop' in turbogears root dir in order to have in installed > (true/false?) It's not always absolutely necessary, but it's also not a bad idea. I usually don't. Sometimes, by not running setup.py develop, I end up getting an error when I run tg-admin (a DistributionNotFound error, I think). Then I'll run setup.py develop and all is well. > 3) And after that, I should manually run 'python setup.py develop' > inside each thirdparty module directory (true/false?) If you've already run setup.py develop in there, you won't generally need to do this again. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
