> More generally, whenever there's a major refactor (or even a minor
> one if it involves renaming or deleting files), it's a good idea to
> delete .pyc files before updating from svn. The .pyc files are not
> stored in svn, so they won't be deleted by update even when the
> corresponding source file is deleted. Leaving the outdated .pyc
> files hanging around can cause problems as they get loaded when they
> really shouldn't be any more, plus deletion of directories by svn
> update won't happen since the delete is 'obstructed' by what svn
> sees as locally-modified files. (If you are not updating from svn
> but rather using a standard install, it's best to first remove all
> traces of the old code...the install won't do that either.)
>
> Karen
I had some problems with old .pyc-files after upgrading too.
I found those helpful commands to delete all .pyc-files in a certain
directory at once:
Find all .pyc-files (just to be sure what you will delete in the next
step):
find /path/to/the/directory/ -type f -name "*.pyc" -exec ls -f {} \;
Then delete all .pyc-files (just replace ls with rm):
find /path/to/the/directory/ -type f -name "*.pyc" -exec rm -f {} \;
Use it with caution, I'm no wizard with the terminal, just wanted to
share this because it's been useful to me.
I found it somewhere on the net, can't find it again, so no link to
the original post...
-benjamin
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
