# Provide additional binaries for Windows with Python 3 support

**URL:** https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270
**Category:** ParaView Support
**Created:** [July 20, 2019, 1:50pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270 "2019-07-20T13:50:20Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![godaygo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/godaygo/32/1779_2.png) [@godaygo](https://discourse.paraview.org/u/godaygo)
#### Post date: [July 20, 2019, 1:50pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/1 "2019-07-20T13:50:20Z")

</div>

I apologize ☹, I did not know that the topic will be removed if I delete and then reassign my account. So I will repeat the question here: _Do you plan to provide ParaView binaries for Windows with Python 3 support? And if yes, what timeframe do you expect?_.

[Mathieu Westphal (Kitware) wrote]

> ParaView 5.8 will be shipped with Python3.

[Kirill Balunov]

> Wow, it was fast! Thank you. Can you specify which minor version of Python will be there, or it is currently not settled down?

[Cory Quammen (Kitware) wrote]

> We are aiming to make this available in ParaView 5.7, due out this summer. It’s not clear which minor version we will use - it might be that we provide binaries with Python 3.5, 3.6, and 3.7, but it depends on what customers need. Do you have a vote for which version?

---

<div class="post-metadata">

### Author: ![godaygo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/godaygo/32/1779_2.png) [@godaygo](https://discourse.paraview.org/u/godaygo)
#### Post date: [July 20, 2019, 1:55pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/2 "2019-07-20T13:55:24Z")

</div>

Sorry one more time for inconveniences.

@cory.quammen although I will answer that my preference is to provide binaries with the latest stable version (3.7 currently, 3.8 - in 3 months). I understand that the answer to this question is completely subjective, but if you choose the 3.6 (because of f-strings and dict ordering), I would be totally ok 😃.

Perhaps you can make it so that there will be a setting during installation to select the Python version that is already installed on the system. But of course it opens up a whole can of worms…and I really don’t know if it is doable. But for the end users - variant with system`s python will ease to install other python packages through wheels and to use other stuff from cpython’s ecosystem.

Also I need to admit, that I’m completely new to the ParaView, and at the moment I am trying to understand what can be done with Python in ParaView. In other words, what is its status here - just as an addon scripting extension, or as a somewhat first class resident which have access to the majority of the application’s capability (gui control, widgets).

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [July 22, 2019, 3:52pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/3 "2019-07-22T15:52:21Z")

</div>

The packages have the Python version in them. Linux will be 3.5 to start (and is looking to likely ship their own Python until 5.8 when we have a better solution). I think macOS will have 3.7 and Windows probably 3.7 as well. Each package will only support a single Python version and for 5.7, we’ll only have one for each platform.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [July 22, 2019, 3:53pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/4 "2019-07-22T15:53:09Z")

</div>

> [@godaygo](#):
>
> I apologize ☹, I did not know that the topic will be removed if I delete and then reassign my account.

I’m actually kind of concerned that any thread (not just their own message contents) can be deleted by the original poster. I wonder if there’s a way to prevent that…

---

<div class="post-metadata">

### Author: ![godaygo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/godaygo/32/1779_2.png) [@godaygo](https://discourse.paraview.org/u/godaygo)
#### Post date: [July 22, 2019, 7:15pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/5 "2019-07-22T19:15:59Z")

</div>

I was also a little surprised by the consequences. I understand that it may not be interesting and is off topic, but I will describe how it happened. I usually register through a Google account, but for some reason I cannot log in from my computer at work this way (but the habit has remained). I decided to re-register in the _traditional way_. In addition, in the preferences there is an option to link to another account, but when logging in via a third-party account (Google, GitHab) this linking does not work. So in the end, I did as I did 😆.

Unfortunately, when you click on the button to delete an account, the question appears something like: “Are you sure? This will lead to a permanent deletion of account.” And since for me it looked exactly what I wanted and also since there was not a single warning to change my mind, I pressed it without any doubt.

Maybe there is an opportunity to at least change the warning message?

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [July 22, 2019, 7:42pm UTC](https://discourse.paraview.org/t/provide-additional-binaries-for-windows-with-python-3-support/2270/6 "2019-07-22T19:42:40Z")

</div>

It’s a Discourse bug. I’ll add a note to track something with upstream. Thanks for the process description from your side.
