Hi everyone, I've noticed that NumPy currently users separate type stub files for specifying types for both pure Python and native modules. For example the (untyped) implementation of np.core._asarray is in [1], but the types are in [2]. This works fine for type checkers, and if anything, improves type checking performance, because type stubs are much smaller than their pure Python counterparts. It does, however, create problems for IDEs which now have to either work with untyped APIs or manually merge them with type stubs to provide better coding assistance.
Is there a reason for type stubs being separate (other than historical [3])? If not, how should I go about starting a conversation upstream about this? Sergei [1]: https://github.com/numpy/numpy/blob/main/numpy/core/_asarray.py [2]: https://github.com/numpy/numpy/blob/main/numpy/core/_asarray.pyi [3]: https://github.com/numpy/numpy-stubs _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
