Optional dependencies discussion: numba, py-triangle

[github-actions]

The file setup.cfg was modified in napari/napari. This might mean the conda-recipe in
napari/packaging needs adjusting! Please check!

Calculated diff:

diff --git a/setup.cfg b/setup.cfg
index 6560f1e6..d2ac6e45 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -114,7 +114,7 @@ all =
     napari-plugin-manager >=0.1.0a1, <0.2.0
 # optional (i.e. opt-in) packages, see https://github.com/napari/napari/pull/3867#discussion_r864354854
 optional =
-    triangle
+    triangle ; platform_machine != 'arm64'  # no wheels
     numba>=0.57.1
 testing =
     babel>=2.9.0

cc @jaimergp

[jaimergp]

We are not including triangle (in conda-forge, py-triangle) in the conda package, so I think I won't add this. That said, the conda-forge package is indeed built for osx-arm64. Any thoughts here @Czaki?

[jaimergp]

For now I have added them to the meta.yaml file, but commented out. At some point we can resume the discussion if we want to consider a policy change for 0.5.0.

[psobolewskiPhD]

My vote would be that the conda-forge install be the fully monty everything working tiptop and easiest.
triangle has the licensing issue for the bundle but here for a dependency it should be ok?
cc: @jni

[jni]

Well, currently I am battling segfaults with the triangle macOS package from conda-forge, so I'm not super convinced that it should be our default...