# Disambiguating Catalyst API version 2.0 and Catalyst Python Script version 2.0

**URL:** https://discourse.paraview.org/t/disambiguating-catalyst-api-version-2-0-and-catalyst-python-script-version-2-0/7266
**Category:** Development
**Created:** [May 20, 2021, 4:41pm UTC](https://discourse.paraview.org/t/disambiguating-catalyst-api-version-2-0-and-catalyst-python-script-version-2-0/7266 "2021-05-20T16:41:09Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 20, 2021, 4:53pm UTC](https://discourse.paraview.org/t/disambiguating-catalyst-api-version-2-0-and-catalyst-python-script-version-2-0/7266/2 "2021-05-20T16:53:12Z")

</div>

My reply to this question in another thread: [Proposal: Catalyst V2 Bidirectional API - #4 by utkarsh.ayachit](https://discourse.paraview.org/t/proposal-catalyst-v2-bidirectional-api/7258/4)

My only comment would be I strongly dislike using “Catalyst 2.0” vs “CatalystV2” to represent different things. May I propose that the new Catalyst+Conduit API be called “CatalystAPI 2.0”? The other one is harder for me, how about “CatalystScript 2.0” or CatalystTrace 2.0?

---

_[View the full topic](https://discourse.paraview.org/t/disambiguating-catalyst-api-version-2-0-and-catalyst-python-script-version-2-0/7266)._