Patchwork Update Errors

Jeff Kirsher tarbal at gmail.com
Tue Oct 26 17:35:54 EST 2010


5010 at 05:35, Jeremy Kerr <jk at ozlabs.org> wrote:
> Hi Jeff,
>
>> Any more idea's Jeremy?
>
> Sorry about the delay, I've just been travelling to the US.
>
>> I have tried adding the follwing:
>>
>> export
>> PYTHONPATH='/srv/pathwork/apps';'/srv/parthwork':'/srv/patchwork/apps/patc
>> hwork'
>
> I'm guessing this isn't the exact 'export' statement, as there are a few typos
> here. With those corrected though, I would assume that this PYTHONPATH would
> be sufficient (I don't think you'd need the last two, but they shouldn't do
> any harm).
>
> Try the following to see if there are any problems importing the patchwork
> module manually:
>
> PYTHONPATH=/srv/patchwork/apps/ python -c 'import patchwork; print patchwork'
>
> Alternatively, grab me on IRC (jk- on irc.freenode.net) and I'll see if I can
> help more interactively :)
>
> Cheers,
>
>
> Jeremy
>

Problem fixed.  Just as an FYI export PYTHONPATH-'/srv/patchwrok'apps'
did not resolve the issue.
in the patchwork.wsgi file I printed out the sys,path afterword.  I
found that even though I exported /srv/patchwork/apps what showed up
was /srv/patchwork.

The solution was to add the followng line to the patchwork.wsgi file
sys.path.append('/srv/patchwork/apps/')
after it imports sys.  This resolved the issue and all appears to
working just fine now.



-- 
Cheers,
Jeff


More information about the Patchwork mailing list