# Documentation should have link for reporting issues

**URL:** https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811
**Category:** Development
**Created:** [June 14, 2022, 5:43pm UTC](https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811 "2022-06-14T17:43:00Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![rweigel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/rweigel/32/7897_2.png) [@rweigel](https://discourse.paraview.org/u/rweigel)
#### Post date: [June 14, 2022, 5:43pm UTC](https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811/1 "2022-06-14T17:43:00Z")

</div>

I found an error in the documentation [5. Programmable Filter — ParaView Documentation 5.10.0 documentation](https://docs.paraview.org/en/latest/ReferenceManual/pythonProgrammableFilter.html#helix-source)  
and it is not clear where I should report the issue.

(Helix script will not work in ParaView versions that use Python 3+ because of the use of `xrange`)

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 15, 2022, 1:13am UTC](https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811/2 "2022-06-15T01:13:14Z")

</div>

Hi, thanks for the report. I have a fix here: [https://gitlab.kitware.com/paraview/paraview-docs/-/merge\_requests/45](https://gitlab.kitware.com/paraview/paraview-docs/-/merge_requests/45)

Could you please comment on whether you agree with the change there or in this post if you don’t want to get a GitLab account?

Thanks,  
Cory

---

<div class="post-metadata">

### Author: ![rweigel](https://discourse.paraview.org/user_avatar/discourse.paraview.org/rweigel/32/7897_2.png) [@rweigel](https://discourse.paraview.org/u/rweigel)
#### Post date: [June 15, 2022, 2:04pm UTC](https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811/3 "2022-06-15T14:04:40Z")

</div>

Looks good. I missed that second one. Also found another:

```auto
git clone https://gitlab.kitware.com/paraview/paraview-docs.git
cd paraview-docs
find . -name "*.rst" | xargs grep "range"

```

./source/UsersGuide/displayingData.rst: for i in xrange(view.GetNumberOfVisibleDataObjects()):

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 15, 2022, 2:55pm UTC](https://discourse.paraview.org/t/documentation-should-have-link-for-reporting-issues/9811/4 "2022-06-15T14:55:14Z")

</div>

Thanks, I changed that one, too: [https://gitlab.kitware.com/paraview/paraview-docs/-/merge\_requests/47](https://gitlab.kitware.com/paraview/paraview-docs/-/merge_requests/47)