gdcm,vtk@8.2: migrate to python@3.10#106947
Conversation
|
Seems to crash when it tries to run |
|
I was looking into We could try to backport it to v8 or just keep on |
|
I don't mind keeping it on |
|
I also think I would like to get For current # Fix vtkpython support for Python 3.10. Remove in the next release.
# First patch backports part of older commit so we can directly patch in upstream commit.
patch :DATA
patch do
url "https://gitlab.kitware.com/vtk/vtk/-/commit/3eea0e12acfb608a76d6ae36fb36566a4a6b0e9b.diff"
sha256 "1c1c4622a58f8c852d196759c8d9036e4d513a5ebe16fe0bfa14583832886572"
end
...
__END__
diff --git a/Documentation/release/dev/python-3.10-wheels.md b/Documentation/release/dev/python-3.10-wheels.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4e81411c73f30724ad420ccb7f3c6c07a6f8e3d
--- /dev/null
+++ b/Documentation/release/dev/python-3.10-wheels.md
@@ -0,0 +1,7 @@
+## Python 3.10 wheels
+
+VTK now generates Python 3.10 wheels. Note that `vtkpython` and other tools
+using `vtkPythonInterpreter` still do not support the new initialization
+behaviors introduced in Python 3.10. See [this issue][vtk-python-3.10-support].
+
+[vtk-python-3.10.support]: https://gitlab.kitware.com/vtk/vtk/-/issues/18317 |
| depends_on "openssl@1.1" | ||
| depends_on "python@3.9" | ||
| depends_on "python@3.10" | ||
| depends_on "vtk@8.2" |
There was a problem hiding this comment.
May be worth checking what features we lose by dropping VTK support. Fedora and AUR (and maybe FreeBSD, not sure of DSL they use) has disabled VTK. NixOS defines VTK as optional.
|
Closing in favor of #107657 |
brew install --build-from-source <formula>, where<formula>is the name of the formula you're submitting?brew test <formula>, where<formula>is the name of the formula you're submitting?brew audit --strict <formula>(after doingbrew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?