Comment 5 for bug 1214098

Revision history for this message
Simon Davis (davis-decent) wrote :

Sorry, figured it out a second later. It was caused by a wrong use of virtualenv by the application here. Everything works just fine now.