Thanks to David Gobbi again, these still need to be in WRAP_EXLUDE
so that the wrappers ignore them, and then added to WRAP_SPECIAL so
that the Python wrappers can wrap them. This should fix the issues
seen on the dashboards introduced by this branch.

Thanks to David Gobbi for the suggestion, and Jean Favre for raising
the issue on our mailing list.

Added an event that fires when the shader updsates so that
programs can use it to update any uniforms they want to

Part of this fix is an application of a patch by Sascha van Vliet (bug report
0015681). During IntersectWithLine, points within a local instance of a
QuadraticTriangle are updated to perform the operation. These points were not
being set properly. An additional visual test of intersections for quadractic
cells has been added, and a bug in vtkQuadraticWedge was found and fixed.

The vtkTemplateMacro is useful for dispatching to filter implementations
that use one template argument.  Add a new vtkTemplate2Macro to dispatch
filter implementations that use two template arguments.  Use a single
switch over two VTK type ids packed into a single integer.

Suggested-by: Will Schroeder <will.schroeder@kitware.com>

This was removed from usage in an earlier commit, but a dead
argument was left behind.

This fix is in reference to bug report 0014340, and is an extension of the
change made in commit 84b126f9. vtkAbstractArray and its children have the
convention of a fast, unsafe method for setting elements (SetXXX) and a safer,
slower method (InsertXXX). In the prior commit, this convention was extended to
setting with variant values. In vtkAbstractArray, InsertVariantValue was not a
pure virtual method, and it called the unsafe SetXXX method (which led to
problems, see the bug report). By making this method pure virtual, we ensure
that InsertXXX is indeed safe for each container. It also enforces the pattern
in place for SetXXX vs InsertXXX with other variable types.

Added the widget and representation (vtkImplicitCylinderWidget and
vtkImplicitCylinderRepresentation). Modified the implicit function
vtkCylinder to support arbitrary center and rotation axis.

This fix is in response to bug report 0015375. vtkLine::EvaluatePosition() and
vtkLine::DistanceToLine() do not logically imply the need for a closest point,
so if a null pointer is passed in its place, the computations will still
execute.

The tp_new slot was unconditionally checking the constructor args,
looking for a swig-style pointer.  This meant that if a vtk class
was subclassed in Python, the subclass constructor args were checked
in the same way regardless of whether it defined its own __init__
method.

Since the GetMappedExtentValue is based on PointExtent,
 it can return an out of bound value in case of i == IMAX or j == JMAX or k == KMAX
so we decrement the value when it is different from 0 to stay bounded.

This fixes http://www.paraview.org/Bug/view.php?id=15470, which saw
the dataset shrink each time the timestep was changed.

Specify private inheritance explicitly to avoid a compiler warning:
class vtkAtomic : private vtk::atomic::detail::IntegralType<T>

This fix is in reference to bug report 0015582. In cases where a single cell
is cut into multiple cells, it is necessary to return disjoint polygon elements
in vtkPolygonBuilder. Additionally, a test provided by Andreas Buykx has been
included that tests the ability of vtkPolygonBuilder to construct multiple
disjoint polygons.

Minimum SDK and deployment is now 10.6.

Convert double-quote includes to angle brackets:

 git grep -l '#include "sstream"' | xargs sed -i 's/"sstream"/<sstream>/'

For Python 2, this method operated like the cmp(a,b) method.  In
Python 3, there is no cmp(a,b) method, so instead this method now
returns (a < b) like the original C++ method.

We no longer need this compatibility layer for the compilers we support.
Use the following commands to switch to standard header and namespace:

 git grep -l vtksys/ios/ | xargs sed -i 's|vtksys/ios/||'
 git grep -l vtksys_ios | xargs sed -i 's|vtksys_ios|std|g'

We no longer need this compatibility layer for the compilers we support.
Use the following commands to switch to standard header and namespace:

 git grep -l vtksys/stl/ | xargs sed -i 's|vtksys/stl/||'
 git grep -l vtksys_stl | xargs sed -i 's|vtksys_stl|std|g'

Previously, extent ranges would always start at 0. This makes sense for
downsampled extractions, but for dimensions where SampleRate was 1, it's
more intuitive to keep the existing sample ranges.

This fix is in reference to bug report 0013143.

This fix is in reference to bug report 0015582. vtkPolygonBuilder manifested
two problems: triangles that were not adjacent to any triangles that were
previously added to the builder were discarded, and polygons with internal
vertices resulted in overlapping cells (the class was explicitly not designed
to handle polygons with internal vertices). The new version fixes these two
issues, and test TestCutter has been added to check these issues as well.

This fix is in reference to bug report 0015557.

This commit is in reference to the following discussion:
vtk/vtk!505 (comment 27173)

This fix is in reference to bug report 0015518. This fix enables
vtkPeriodicDataArrays to be written to XML, albeit inefficiently.

1) Change unicode string unicode string check in TestTemplates.py.
2) Eliminate some obsolete imports (like "exceptions").
3) Convert string to bytes in TestDataEncoder.py.

This reverts commit 50d2a986.
The vtkInfovisBoostGraphAlgorithms module uses these forward
declarations and friendship.

The python "buffer" and "memoryview" objects do not expose the pointer
to the underlying memory, they only expose the contents of the memory.
Likewise, if you check (buffer1 == buffer2) within python, then python
will iterate through both buffers to see if they have the same contents!
After all, for python, that's how equality is defined for sequence types.

This commit adds a method called buffer_shared(ob1, ob2) that checks to
see if two objects (e.g. arrays) expose the same block of memory via
their buffer interface.  It assumes that the "buf" pointer is the lowest
address of the buffer (i.e. the strides must be non-negative).

It also adds two changes to dataset_adapter.py:
1) The adapter now uses buffer_shared() instead of using "==" to compare
buffers, because as stated above "==" does the wrong thing.
2) It repairs an infinite recursion where __getattr__ called hasattr().
The infinite recursion was caught silently by hasattr() itself in python2,
but is exposed as a RuntimeError in python3.

On Mac OS 10.7.5, GCC 4.2.1 the compil for the test TestDayaArrayAPI
never completes. This patch breaks up ExerciseDataArray into into two
methods: ExerciseDataArrayAPI and ExerciseGetRange.