Changes between Version 1 and Version 2 of Ticket #71163, comment 15
- Timestamp:
- Nov 2, 2024, 11:19:44 PM (3 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #71163, comment 15
v1 v2 3 3 I don't think so, at least not by the documentation and intended use cases that I'm aware of. You're welcome to ask on the discourse post I started. 4 4 5 I agree with your preference to use the same base vtk libraries. I'm noticing a trend in open-source software where it is common practice to duplicate dependencies for each minutely different situation, and Python is a leading offender by promoting virtual environments. So bundling a separate set of vtk libraries in the vtk-python wheel build is simply going along with that trend. Oh, and Paraview is another situation where it builds and uses its own set of vtk libraries. At least, the last time I looked into building paraview, using already existing vtk libraries was "in development". So I'm not sure pythoners and vtkers will even understand what we are asking.5 I agree with your preference to use the same base vtk libraries. But I'm noticing a trend in open-source software where it is common practice to duplicate dependencies for each minutely different situation, and Python is a leading offender by promoting virtual environments. So bundling a separate set of vtk libraries in the vtk-python wheel build is simply going along with that trend. Oh, and Paraview is another situation where it builds and uses its own set of vtk libraries. At least, the last time I looked into building paraview, using already existing vtk libraries was "in development". So I'm not sure pythoners and vtkers will even understand what we are asking.