As a slight aside, I use a shell script for starting turbogears proper, which sets PYTHONPATH to a local directory (externals/lib) and I have another script I use to construct the externals bin and lib using easy install. This allows me to define the required support modules and versions (including turbogears itself) in the setup script, and commit that to svn, rather than commiting the actual libraries themselves.
It makes it easier when it comes time to move onto a production platform, since the system-level dependencies are fewer, usually just python itself - and there's no chance that a system update will screw with the library versions you've tested your application on. My latest project uses the following: #!/bin/bash # # Run from the main directory to create the external dir with the right deps # needs setuptools installed # export PYTHONPATH="external/lib" easy_install-2.4 -d external/lib -s external/bin TurboGears lxml TurboMail SQLObject==0.8.2 iCalendar easy_install-2.4 -d external/lib -f http://cheeseshop.python.org/pypi/Routes/1.6.2 Routes==1.6.2 On Jun 19, 5:12 pm, iain duncan <[EMAIL PROTECTED]> wrote: > It's about time I got to using source control properly for my tg > projects. Wondering if anyone has put any tips up anywhere on how to > best go about this for someone new to subversion. Or if anyone wants to > share what they do, perhaps I could make a wiki page out of the results. > > Thanks > iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
