Patch for texmanager.py

Development matplotlib-devel
1

shutil.move(dvibase, dvifile)

    > The shutil.move() is somewhat more robust than os.rename().
    > For more information see
    > http://mail.python.org/pipermail/python-list/2005-February/266553.html
    > and /266632.html.

Is this expected to work across platforms, eg win32, linux, os x and
unix?

JDH

2

I just verified that shutil.move works fine in Windows 98.

Gary R.

John Hunter wrote:

···

"Ed" == Ed Schofield <schofield@...265...> writes:

    >> shutil.move(dvibase, dvifile)

    > The shutil.move() is somewhat more robust than os.rename().
    > For more information see
    > http://mail.python.org/pipermail/python-list/2005-February/266553.html
    > and /266632.html.

Is this expected to work across platforms, eg win32, linux, os x and
unix?

JDH

3

   > The shutil.move() is somewhat more robust than os.rename().
   > For more information see
   > http://mail.python.org/pipermail/python-list/2005-February/266553.html
   > and /266632.html.

Is this expected to work across platforms, eg win32, linux, os x and
unix?

Yes, I believe so. Confirmed on Linux. The shutil.py source code implements move() by copying the file, including stat info, and then deleting it. On Mac filesystems it ignores resource forks, but the DVI file should be stored entirely in the data fork.