# Multiple major versions from one Python script?

**URL:** <https://discuss.elastic.co/t/multiple-major-versions-from-one-python-script/42657>\
**Category:** Elasticsearch\
**Created:** [February 24, 2016, 11:54pm UTC](https://discuss.elastic.co/t/multiple-major-versions-from-one-python-script/42657 "2016-02-24T23:54:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jay\_Swan](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@Jay\_Swan](https://discuss.elastic.co/u/Jay_Swan)\
**Post date:** [February 24, 2016, 11:54pm UTC](https://discuss.elastic.co/t/multiple-major-versions-from-one-python-script/42657/1 "2016-02-24T23:54:23Z")

</div>

The official Python clients require different versions for different Elasticsearch major versions.

Is there a way to talk to clusters running different major Elasticsearch versions from the same Python script?

---

<div class="post-metadata">

**Author:** ![Michael\_Hart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_hart/32/65937_2.png) [@Michael\_Hart](https://discuss.elastic.co/u/Michael_Hart)\
**Post date:** [June 22, 2016, 1:06pm UTC](https://discuss.elastic.co/t/multiple-major-versions-from-one-python-script/42657/2 "2016-06-22T13:06:13Z")

</div>

I'm interested in the same thing. Officially the major version of the python library has to match the major version of the Elasticsearch cluster, which is a huge pain when I have one python app trying to connect to two different Elasticsearch clusters at different versions. The official lack of backwards compatibility in python pip version is going to be a huge problem for us.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:41pm UTC](https://discuss.elastic.co/t/multiple-major-versions-from-one-python-script/42657/3 "2017-07-05T22:41:25Z")

</div>