On 5/20/07, px <[EMAIL PROTECTED]> wrote: > * Do you develop on the target installation or do you modify files in > your local directory and run the install process again?
For trunk, I now use: python setup.py develop -m I also use workingenv [1] to install all the requirements, including trac itself in development mode, in a sandbox. To set up my Trac development environment I'd do something like: $ svn co http://svn.edgewall.com/repos/trac/trunk trac You can put your workingenv and Trac test environment anywhere, but for the purposes of this mail I'll plonk it under the checked out trunk: $ cd trac $ mkdir sandbox $ workingenv -Z --site-packages sandbox/wenv $ . sandbox/wenv/bin/activate (wenv)$ python setup.py develop -m (wenv)$ trac-admin sandbox/trac initenv .... You can install your plugins into this working environment in exactly the same way: (wenv)$ cd ../myplugin (wenv)$ python setup.py develop -m Start Trac: (wenv)$ tracd -r -s --port 8000 ./sandbox/trac ... Edit Trac and/or plugins to your hearts content. When finished, deactivate the workingenv: (wenv)$ deactivate $ tracd -bash: tracd: command not found My actual environment is a bit more streamlined than that, but that's essentially how it works. Any of the other developers got useful tips? I know coderanger has a spectacularly large set of scripts to make his life easier :) [1] http://cheeseshop.python.org/pypi/workingenv.py -- Evolution: Taking care of those too stupid to take care of themselves. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
