Hi Lucy, the problem is with the use of triple quotes. I just found this stack 
exchange question 
<http://stackoverflow.com/questions/7057450/specific-reason-why-python-uses-triple-quotation-marks-for-comments>
 
that should give you more background.

When I used # to comment out those lines I didn't get a syntax error.

Hope everything works now :)

Adam

On Sunday, November 6, 2016 at 4:29:50 AM UTC-6, Lucy FJ wrote:
>
> Hi everyone,
>
> This is a basic technical question which I am asking as a not particularly 
> technical person. 
>
> We are customising Arches and are changing forms.py because we have added 
> new nodes to the Heritage Resource graph. 
> I have copied forms.py from the Arches HIP directory, changed it and put 
> it into our custom directory. I opened Arches and found that the changes 
> had not taken effect and noticed that a .pyc file had not been created in 
> the custom directory. I assume that the .pyc file in the HIP directory is 
> being read instead? (It is still there). I have tried stopping and 
> restarting our server and still the .pyc file fails to be created. The file 
> resource.py has been changed as suggested by the Arches documentation to 
> pick up the correct version of 'forms' (*from arches_hip.models import 
> forms *has been changed to *import forms*) and is also located in the 
> custom directory. What is the mechanism that causes the .pyc file to be 
> created? I was wondering if it was a permission/ownership problem. All our 
> Arches programs are owned by Root. is this normal in an Arches 
> installation? 
>
> Thank you very much for your help.
>
>
>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to