> I don't know how productive it is to dream up examples, but it's not Well, agreed, to be honest.
> very hard to do. Currently, e.g., the community is not ready to adopt > numba as part of the ufunc core. But it's been stated by some that, Who are you speaking for? The entire community? Under what mandate? > with so many people running Conda, breaking the ABI is of little > consequence. And then it wouldn't be much of a leap to think that numba > is an acceptable dependency. The current somewhat concrete proposal I am aware of involves funding cleaning up dtypes. Is there another concrete, credible proposal to make Numba a dependency of NumPy that you can refer to? If not, why are we mired in hypotheticals? > There's a broad range of Continuum projects that intersect with what > NumPy does: numba, DyND, dask and Odo to name a few. Integrating them > into NumPy may make a lot more sense for someone from Continuum than for > other members of the community. May? Can you elaborate? More speculation. My own position is that these projects want to integrate with NumPy, not the converse. Regardless of my opinion, can you actually make any specific arguements, one way or the otehr? What if if some integrations actually make more sense for the community? Is this simply a dogmatic ideological position that anything whatsoever that benefits both NumPy and Continuum simultaneously is bad, on principle? That's fine, as such, but let's make that position explicit if that's all it is. Bryan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
