This should not be a .pyc problem, since upon startup python compares the modified time of the .pyc to that of the .py, if available.
python will use the .pyc if it can't see the .py . I don't know what it will do if the .py is there, but it doesn't have permission to read it (possible permissions issue). The other way this could be a .pyc problem is if the .py file was updated in such a way that the modified time is left older than that of the .pyc (differences in time setting on the two machines, some funky transfer mechanism that sets the target modified time to match that of the source, where the .pyc is newer, or the machine time was messed up the first time the app was started, yielding a .pyc modified time far in the future). When I've had troubles like this it has more often been that I've had two copies of the site on the deployment box, and I've been fixing the wrong one. Bill On Mon, Mar 4, 2013 at 9:03 AM, frocco <faro...@gmail.com> wrote: > That's good to know. > > > On Monday, March 4, 2013 8:12:15 AM UTC-5, Venkatraman.S. wrote: > >> Always prefer to delete the .pyc fie for issues such as these wherein >> changes are not reflected despite server restart. >> >> On Sun, Mar 3, 2013 at 9:59 PM, Serge G. Spaolonzi <se...@cobalys.com>wrote: >> >>> Maybe the server is loading an old .pyc file. try to delete the urls.pyc >>> file and restart the server. >>> >>> >>> On Sun, Mar 3, 2013 at 11:16 AM, Asier Hernández Juanes < >>> asier...@gmail.com> wrote: >>> >>>> Hi everyone, >>>> >>>> i have a remote Linux server with a Django application running in a >>>> nginx server but when I make a change in urls.py like adding a new >>>> urlpattern the server is not applying the changes. I have restarted nginx >>>> server but the new url is not loading. >>>> >>>> Does anyone know what may be the problem? >>>> >>>> Thanks a lot! >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django-users...@**googlegroups.com. >>>> To post to this group, send email to django...@googlegroups.com. >>>> >>>> Visit this group at >>>> http://groups.google.com/**group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>>> . >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Serge G. Spaolonzi >>> Cobalys Systems >>> http://www.cobalys.com >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-users...@**googlegroups.com. >>> To post to this group, send email to django...@googlegroups.com. >>> >>> Visit this group at >>> http://groups.google.com/**group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>> . >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
