mv-python
mv-python
The CI is failed because windows build was cancelled after 50 minutes :-(
@da-woods @scoder is there anything pending here? All comments were implemented.
Thank you @da-woods for merging this PR!
I was able to find root cause of this issue. I was able to **fix this issue in Coverage code** but I am not 100% sure if it is the...
> If I understand right, the values :c:expr: assumes that you might have a bunch of definitions of C functions or types, so it'd create a link to the definition...
> I think sphinx :orphan: might hide the warning (https://www.sphinx-doc.org/en/master/usage/restructuredtext/field-lists.html#metadata) I will create separate PR for removing these files so I am not going to add `:orphan:` to them.
My personal feeling is that we should stick with `:c:` statements for C expressions and `:py:` statements for python expressions.
> What is the rule? Should it use :c:type: for any trivial type and :c:expr: for non-trivial types (like pointers)? The rule of thumb is: * `:c:type:` should be used...
Also numpy project is using them: https://github.com/numpy/numpy/blob/623bc1fae1d47df24e7f1e29321d0c0ba2771ce0/numpy/random/_philox.pyx#L14
I think that unittests are still failing. I will have a look.