Paraview installs its internally bundled VTK python modules to the same path as this feedstock, creating a conflict.
I used the method described here to define a conflict.
Checklist
[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.
This came up in the course of investigating #83, which I think is an issue with the Paraview feedstock rather than this one.
Paraview installs its internally bundled VTK python modules to the same path as this feedstock, creating a conflict.
I used the method described here to define a conflict.
Checklist
conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)This came up in the course of investigating #83, which I think is an issue with the Paraview feedstock rather than this one.