I'm sure I'm using the expected method - so this is a workaround, not a solution:
I usually add the plugin path to the PYTHONPATH by the time I run setup.py develop --install-dir. BTW I got several issues with the site.py file that is installed w/ this command: the python interpreter gets mad and enter an infinite loop (100% CPU time...) when I run tracd. I got used to remove the site.py and site.pyc files to make it work. I should admit I'm not a fan of setuptools and the less time I have to deal with it, the better. So you'd better not to follow my workaround here, it's definitely not a good idea - but it works ;-) I hope someone will post a better and safer answer... Cheers, Manu On 11/7/06, datenimperator <[EMAIL PROTECTED]> wrote: > > Hi all, > > can anybody help, please? I've read all the docs I could find, but > don't get it to work. Has anybody a working development environment on > Windows? How do you test your plugins without rebuilding the egg and > restarting tracd after every change? > > Any hint is greatly appreciated. Regards, > > Christian > > > > > -- Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
