Another way to switch between versions of packages is to use the --multi-version option in setuptools.
"In multi-version mode, no specific version of the package is available for importing, unless you use pkg_resources.require() to put it on sys.path" Here's the rest of the docs: http://peak.telecommunity.com/DevCenter/setuptools#develop-deploy-the-project-source-in-development-mode you could then add the following to your startup script: import pkg_resources pkg_resources.require('turbogears==1.1') I haven't tried this with turbogears but it works well with other packages when I'm testing things out on new versions. Stephen Emslie On 9/16/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > Take a look at: > > http://cheeseshop.python.org/pypi/workingenv.py > > This will let you set up separate working environments for various > TurboGears versions. > > --Mark Ramm > > On 9/16/07, Ivo Looser <[EMAIL PROTECTED]> wrote: > > Hi Together > > > > I try to use different Turbogears Projects for Development. I use on Version > > for my project witch goes nearly live. The new Version maybe 1.1 should also > > be avaible for Testings on my Projects. Currently when i switch the version > > with drop the egg folders and reinstall the newer or older Version. > > > > Is there a simpler way to switch between versions? > > > > Thanks for your support. > > > > Best regards Ivo > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
