While making pyaedt available in CPython3.12 (see #4759 and #4769) we faced a problem related to pyvista.
Indeed, this package has been officially available for CPython3.12 starting with release 0.43.0. However, starting from this release, problem started to arise (on our side) due to some inner problems related to the way pyvista and vtk. This problem also arise when using vtk-osmesa (in CICD) whatever the version we tried.
We should leave this issue open to track the state of the pyvista and the changes we have to perform (and discard later) to make the repo working with CPython3.12
While making
pyaedtavailable in CPython3.12 (see #4759 and #4769) we faced a problem related topyvista.Indeed, this package has been officially available for CPython3.12 starting with release
0.43.0. However, starting from this release, problem started to arise (on our side) due to some inner problems related to the waypyvistaandvtk. This problem also arise when usingvtk-osmesa(in CICD) whatever the version we tried.Here is a link to the issue opened in
pyvistarepo https://github.com/pyvista/pyvista/issues/6234.We should leave this issue open to track the state of the
pyvistaand the changes we have to perform (and discard later) to make the repo working with CPython3.12Tests impacted: