On Sunday, November 23, 2014 4:30:51 AM UTC-8, Ron Kyle wrote: > > Wow, I really just have to delete the setup.py from the /plugins > directory? I didn't think it mattered cause it wasn't an .egg... >
Yes, it sounds like you just need to delete the file. Trac can also load single-file plugins, which are just a single .py file, and that's why it's trying to load setup.py. It's likely that Trac should be more robust and it should not bring the whole application down when the .py file is not a valid single-file plugin. That is the reason why #11846 was opened. > "And never try "installing" Trac plugins without a clue on the underlying > system layout again but read more on TracPlugins ASAP." > > Haha, you said it there. I've been reading up on it a bit and was > wondering a few things... > All this easy_install stuff is just downloading the egg and putting it in > the plugins directory, right? If I put an .egg in /plugins and enable it in > the trac config file then it's installed? Just reset the server and go? > I > If I have the source, I just bulid the .egg, put it in /plugins and enable > it? I know, pretty much same question... > Thanks for the help Both of the scenarios you describe should work. You can also install plugins in the Python site-packages directory, so it is not even required to drop them into the "plugins" dir. Some advise against doing this, but it may not matter in your case, and in particular if you are using a virtual environment that is dedicated to your Trac instance. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
