# Wheels for python 3.10 available on pypi?
**URL:** https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649
**Category:** Support
**Tags:** python
**Created:** [June 2, 2022, 3:52pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649 "2022-06-02T15:52:18Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@johmue](https://discourse.vtk.org/u/johmue)
#### Post date: [June 2, 2022, 3:52pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/1 "2022-06-02T15:52:18Z")
May I suggest putting vtk-9.1.0 wheels for python-3.10 to pypi? I have to say it is meanwhile quite some limitation for python packages depending on vtk to be tied to python-3.9. Any chance that this will happen soonish?
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [June 2, 2022, 4:24pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/2 "2022-06-02T16:24:57Z")
3.10 broke APIs that VTK used to initialize the interpreter, so it is untestable without backporting a lot of code. Wheels could be made, but they would be completely untested under 3.10.
---
### Author:  [@johmue](https://discourse.vtk.org/u/johmue)
#### Post date: [June 2, 2022, 6:16pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/3 "2022-06-02T18:16:52Z")
Wooh, that does not sound too encouraging. Is there any publicly readable more detailed discussion about that in some issue tracker? I would like to make up my opinion whether it might be an option for us to tackle that problem. No promises at this point, though.
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [June 2, 2022, 6:38pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/4 "2022-06-02T18:38:23Z")
[https://gitlab.kitware.com/vtk/vtk/-/issues/18317](https://gitlab.kitware.com/vtk/vtk/-/issues/18317)
MRs related to this support until we finally got it right:
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8738](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8738)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8741](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8741)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8779](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8779)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8910](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8910)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8829](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8829)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8821](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8821)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8784](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8784)
- [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8789](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8789)
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [June 2, 2022, 6:39pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/5 "2022-06-02T18:39:40Z")
The interpreter initialization for 3.10 has already been fixed in the master branch. But it involved a lot of changes to the code, much more than could be comfortably backported to VTK 9.1.
The main tracking issue was [#18317](https://gitlab.kitware.com/vtk/vtk/-/issues/18317).
---
### Author:  [@johmue](https://discourse.vtk.org/u/johmue)
#### Post date: [June 2, 2022, 6:55pm UTC](https://discourse.vtk.org/t/wheels-for-python-3-10-available-on-pypi/8649/6 "2022-06-02T18:55:01Z")
Ah. So that means there is land in sight. That’s good news.
Thanks guys.