Problems updating an old install

[Vincent LADEUIL]

Please accept my apologies for the noise.

The explanation was clear, there is no problem.

I just had to understand  the problem before the explanation make
sense :-/

>>>>> "Aaron" == Aaron Bentley <aaron.bentley at utoronto.ca> writes:

    Aaron> Vincent LADEUIL wrote:
    >> Trying to install that I get :

    >> | File "/home/vila/src/bzr.dev/bzrlib/branch.py", line 23,
    >> in ?  | import xml.sax.saxutils | ImportError: No module
    >> named sax.saxutils

    Aaron> This is a problem with in-place upgrades, because they
    Aaron> don't usually delete old pyc files.  

Neither in build directory, nor in lib/python tree.

    Aaron> We used to have bzrlib/xml.py, which meant that you
    Aaron> couldn't use xml.* from the standard library.  We've
    Aaron> renamed that file, but if you still have the old .pyc
    Aaron> file, you'll experience that bug.

And  clearing once the  lib/python/bzrlib but  not the  build and
then the  build but not  the lib/python/bzrlib are  not solutions
because the wrong xml.pyc survived :-) Both have to be cleared.

    >> I have the feeling that using 'python setup.py clean' and
    >> 'python setup.py install --home $HOME' is not sufficient
    >> when it comes to switch between 0.7 version and 'bzr.dev'
    >> version...
    >> 
    >> Am I right ?

    Aaron> This isn't normally true, bug for 0.7 and the current
    Aaron> bzr.dev, I guess it is.

And reading the  patch to Makefile in another  thread should have
rung a bell.

    >> Anyway, is 'sax.saxutils' a new requirement ?

    Aaron>  Not   really.   Yes,  we   weren't  previously  using
    Aaron> sax.saxutils, but it  is part of the standard library.
    Aaron> So that's an old requirement.

"standard library", "old requirement" (as  in "it was and is still
a requirement", not "it *was* a requirement" !).

      Vincent  (feeling stupid,  but  less ignorant :-)