yea, my knowledge from python is like larry and you told, the pyc-files get rebuild if the timestamp of the py and pyc files differs. But, because in my case it seems to be handled different, I wondered if django handles this in another way. I'll delete them on every rebuild and hope that this solves my problem (or other upcoming problems related to this).
thank you guys. bg Johannes On 07.04.2013 22:31, Alexis Roda wrote: > Al 07/04/13 21:35, En/na Johannes ha escrit: >> I get again to different results. >> the shell accesses the settings.py while from the testserver the >> settings.pyc is accessed. After I deleted the pyc-file. the testserver >> uses the settings.py too. >> When and in which cases the pyc-file gets (re)-build? > > Johannes, > AFAIK python rebuilds them automatically if they are older than the > corresponding '.py' file. Probably the first time they are imported, but > not sure about that. > > You can trigger a manual compilation with the 'compileall' module > included in the stdlib: > > python -m compileall <path_to_package_or_module> > > To be in the safe side I'd recommend deleting all '.pyc' files before > rebuilding them. > > > Regards > -- 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.
