[vtk-developers] Incorrect checkins into Wrapping/Python: a, plea for communication!

[Prabhu Ramachandran]

>>>>> "Utkarsh" == Utkarsh Ayachit <utkarsh.ayachit at kitware.com> writes:

    Utkarsh> I apologize for any inconvieniences that the recent
    Utkarsh> Wrapping/Python may have caused.  Here is a brief summary
    Utkarsh> of what I wanted to do. I would appreciate any feedback.

There is no inconvenience currently but a heads up would always help
so some of us are alerted.  IMHO, it would be a problem if something
like this creeps up in the last minute and 5.0 is released.

    Utkarsh> Basically, all the added stuff (which I agree I should
    Utkarsh> have been put away in a package: I'll put it away as
    Utkarsh> "vtktesting", is that ok?) is a quick script to convert
    Utkarsh> most of the Tcl tests to Python. (I wasn't aware of
    Utkarsh> Utilities/tcl2py.py. On a quick attempt, it seems to fail
    Utkarsh> for quite a few tests
    Utkarsh> eg. Graphics/Testing/Tcl/Delaunay3D.tcl). No VTK user is
    Utkarsh> supposed to use any of these scripts. The sole purpose is
    Utkarsh> to convert VTK tcl tests to python.

If it is not something that VTK users should be importing *at all*
then I'd argue that there is no need to put it inside
Wrapping/Python/vtk/.  Instead it should go into Utilities.  The
trouble with making it a package is that people might start using it
and relying on it.  If that is acceptable, then sure, making a package
called vtktesting sounds good.  If not, Utilities is the place for it,
IMO.  I do not know what the others think.

tcl2py.py is a hack, I was curious to know if you were aware of it and
how it fared.  Since your solution is much better, it only makes sense
to use it.

Thanks for taking the time to increase the test coverage of
VTK-Python!

cheers,
prabhu