# Nightly Python Releases on Anaconda

**URL:** <https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739>\
**Category:** Development\
**Created:** [September 10, 2019, 4:33pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739 "2019-09-10T16:33:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![banesullivan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/banesullivan/32/7143_2.png) [@banesullivan](https://discourse.vtk.org/u/banesullivan)\
**Post date:** [September 10, 2019, 4:33pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/1 "2019-09-10T16:33:39Z")

</div>

Would anyone be interested in helping set up an Anaconda recipe to build VTK from the master branch on a nightly/periodic basis to keep the Python wheels up to date with the latest developments in VTK?

I’ve also posted an issue [here](https://github.com/conda-forge/vtk-feedstock/issues/90) but I think a new feedstock might have to be created.

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)\
**Post date:** [October 10, 2019, 8:19pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/2 "2019-10-10T20:19:19Z")

</div>

@danlipsa Can the recipes you worked on be reused for this?

---

<div class="post-metadata">

**Author:** ![danlipsa](https://discourse.vtk.org/user_avatar/discourse.vtk.org/danlipsa/32/390_2.png) [@danlipsa](https://discourse.vtk.org/u/danlipsa)\
**Post date:** [October 10, 2019, 8:27pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/3 "2019-10-10T20:27:38Z")

</div>

Yes, I think it could. VTK does not need python-optional-link.patch anymore but besides that it should work fine.

[https://github.com/CDAT/conda-recipes/tree/master/vtk-cdat](https://github.com/CDAT/conda-recipes/tree/master/vtk-cdat)

I can help setting this up.

---

<div class="post-metadata">

**Author:** ![banesullivan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/banesullivan/32/7143_2.png) [@banesullivan](https://discourse.vtk.org/u/banesullivan)\
**Post date:** [October 11, 2019, 9:03pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/4 "2019-10-11T21:03:56Z")

</div>

Aha, the recipes you have there are awesome, thanks for making those!

@danlipsa, I just pinged you on the GitHub issue for the conda-forge build of VTK. It appears we can’t even build dev releases on conda-forge until [https://github.com/conda-forge/conda-forge-enhancement-proposals/pull/3](https://github.com/conda-forge/conda-forge-enhancement-proposals/pull/3) is resolved.

---

<div class="post-metadata">

**Author:** ![banesullivan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/banesullivan/32/7143_2.png) [@banesullivan](https://discourse.vtk.org/u/banesullivan)\
**Post date:** [October 11, 2019, 9:09pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/5 "2019-10-11T21:09:00Z")

</div>

Perhaps, we could set up a [pre-release on PyPI](https://packaging.python.org/guides/distributing-packages-using-setuptools/#pre-release-versioning) instead where wheels are automatically uploaded on a periodic basis.

Is there a current CI service for building [the PyPI wheels](https://pypi.org/project/vtk/)? Also why are the PyPI wheels still on 8.1.2 and not 8.2?

---

<div class="post-metadata">

**Author:** ![banesullivan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/banesullivan/32/7143_2.png) [@banesullivan](https://discourse.vtk.org/u/banesullivan)\
**Post date:** [October 26, 2019, 11:56pm UTC](https://discourse.vtk.org/t/nightly-python-releases-on-anaconda/1739/6 "2019-10-26T23:56:09Z")

</div>

It might be a good idea to just make a VTK channel on anaconda where we can have regular builds of VTK and specialized builds that enable things like OpenVR (ref [Python rendering scene to VR](https://discourse.vtk.org/t/python-rendering-scene-to-vr/340))