Alex Kaszynski

> it's just with the notebook that the new labels wont play nice. Interesting. That's the edge case we didn't consider. I'll have it such that when displaced within the...

Yes, that would be best. @germa89, can you take care of this? Effectively, when we create labels we should just set `always_visible=True` in our `general_plotter`. See [add_point_labels](https://docs.pyvista.org/api/plotting/_autosummary/pyvista.Plotter.add_point_labels.html)

Suggest separate docs page. Agree that it’s too long.

We've received confirmation that the internal XML files are now permitted to be rendered to Python. We now need an automated way of doing that per release, noting deprecated methods,...

Agreed, and this would help with conversion examples. Since the `=` operator appears to only be used when setting parameters within a mapdl script, we could simply literally convert and...

Played around with this for a bit. Turns out the trick here is to just use CubeAxesActor2D as suggested in https://github.com/pyvista/pyvista/issues/699 ```py import vtk import pyvista as pv p =...

> I agree with using `CubeAxesActor2D`. However, some methods such as `SetXAxisMinorTickVisibility` are not present, so we need to think carefully about how to migrate to `CubeAxesActor2D`. Agreed. I think...

`conda` is fairly popular, and we should (ideally) support it. We should also require python

> Maybe just plain `.txt` file is better? I think .txt is the right option for simple points writer.

Can you turn on `faulthandler` with: ```py import faulthandler faulthandler.enable() ``` My guess is there's symbol or library conflict when importing `tensorflow` and enabling `faulthandler` will hopefully tell us where.