On Fri, 5 Nov 2010 20:05:58 -0400, "Field, Scott" <scott_field(a)brown.edu> wrote:
> I was about to send off the updated review, and when I grabbed staging I
> noticed vtk.py was deleted. This is causing some conflicts, so before
> merging staging with my active branch I wanted to double check that vtk.py
> is supposed to be deleted.
Yes, that was indeed intentional. The background to that is that I'm
using that vtk file writing functionality in my new project as well, so
I moved it out of hedge and into a more central location. That central
location is 'pyvisfile', which is also the new home for what used to be
'pylo' (as pyvisfile.vtk and pyvisfile.silo respectively).
In other words, if you clone pyvisfile as
git clone http://git.tiker.net/trees/pyvisfile.git
you should be fine. Pylo on the other hand is obsolete and can be
deleted, having been subsumed into PyVisfile.