Quoting "Tony S Yu" <[email protected]>:
Just a word of warning to those using the trunk: SVN doesn't clean
up compiled files.
The reason this matters concerns a change in the trunk (recently?
not sure how long it's been since I updated).
This was, indeed, a recent change.
It appears that fipy.tools.inline got changed from a package to a module.
:
:
importing fipy.tools.inline is ambiguous. In this case, the old
files were used and my code was failing all over the place.
Deleting the fipy/tools/inline/ directory did the trick. I just
thought people would be interested.
Thanks very much for pointing this out to the list. I was aware of the
issue and should have said something.
I had thought that there was an option to pass to svn that would clear
this up in a working copy, but it turns out that I was thinking of the
-P[rune] option to `cvs update`. There is no equivalent in svn (mostly
because svn isn't nearly as broken as cvs in this respect (but still
broken enough)) and it wouldn't have worked anyway. -P only works on
empty directories, and because of the .pyc files, fipy/tools/inline/
would have been seen as empty, even though it has been `svn delete`d.
From the discussion on "Merges and Moves", it turns out that this
sort of refactoring is a known weakness in svn.
