On 04/08/2012 11:25 AM, shacker wrote:
alias delpyc='find . -name "*.pyc" -print0 | xargs -0 rm -rf'
Then you safely run "delpyc" from the top level of your project at any
time to remove them all, ensuring that whatever problem you're
experiencing isn't a result of them.
This is probably not true; you'll have to run your delpyc script on your
virtualenv (or Python site-packages) folder to ensure that the problem
you have isn't being caused by a zombie .pyc file in an installed
package. Running it in the project folder only deletes .pyc files you wrote.
Just a nitpicky point, but I wanted to point it out in case anyone else
followed this thread, deleted .pyc files in their project and wrongly
went on to a frustrating wild goose chase assuming they already ruled
out this problem.
Shawn
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
