Vincent Polite wrote:
Thanks, Noah. It does appear that I should (if I am understanding the documentation) use VirtualEnv to create isolated Python environments for different applications. The idea being that I can set up one VirtualEnv install the dependencies for my Trac 0.10 install and then another VirtualEnv for Trac 0.11, correct? I'm not quite sure how this all plays with Apache vs. tracd, but I'll walk through the documentation and if I have any further questions, I'll post back. (Any gotchas that you see up front if you could call to my attention would be appreciated, however)
You will just need to alter sys.path (either in the FCGI/WSGI script, or via PythonPath depending on your frontend) to include the correct virtualenv's library folder.
As a tangential question, what have people done using Trac 0.10.x to get around the problems that spawned configurableWorkflow in Trac 0.11? Specifically I have a newly minted QA guy who wants to have issue tickets move to a QA queue of sorts. Obviously this is handled in Trac 0.11, but at least in one case they "need" the PrivateTicketPlugin which, last I looked was only still available at 0.10.x. My recommendation to my client if they needed the PrivateTicketPlugin that was only available for 0.10 was to either contact coderanger and bribe him or just instill in the engineers the workflow of assigning their tickets to a QA user for validation - it being a small company that seemed realistic.
There is an initial port to 0.11, but its not quiiiite functional. Give it about a week or so.
--Noah
signature.asc
Description: OpenPGP digital signature
