# vtkSphere : passing a null parameter in ComputeBoundingSphere from Python

**URL:** https://discourse.vtk.org/t/vtksphere-passing-a-null-parameter-in-computeboundingsphere-from-python/14473
**Category:** Support
**Created:** [August 25, 2024, 10:37am UTC](https://discourse.vtk.org/t/vtksphere-passing-a-null-parameter-in-computeboundingsphere-from-python/14473 "2024-08-25T10:37:00Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![dgobbi](https://discourse.vtk.org/user_avatar/discourse.vtk.org/dgobbi/32/18_2.png) [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [August 26, 2024, 11:20pm UTC](https://discourse.vtk.org/t/vtksphere-passing-a-null-parameter-in-computeboundingsphere-from-python/14473/7 "2024-08-26T23:20:23Z")

</div>

Though this won’t help people using the current version of VTK, vtkSphere should add an overload that defaults `hints` to `nullptr`:

```auto
template <class T>
void ComputeBoundingSphere(T* pts, vtkIdType numPts, double sphere[4])
{
  return ComputeBoundingSphere(pts, numPts, sphere, nullptr);
}

```

Edit: I see this has already been suggested above.

---

_[View the full topic](https://discourse.vtk.org/t/vtksphere-passing-a-null-parameter-in-computeboundingsphere-from-python/14473)._