-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
num_ivy_arrays_on_dev #1451
num_ivy_arrays_on_dev #1451
Conversation
Hi David, Thanks for making a new PR! test-numpy-style-docstrings should be passing, so checkout the 'details' for this. |
Hi Simone, |
Hi Simone, |
Hi David, Could you pull from master? Some fixes have been introduced for some of the tests, thanks! |
Hi Simone, |
Hi David, So currently your examples are failing the docstring tests. Have you tried running this function using the master version of ivy? When I do, I need to write the examples in a different manner to the way you have written them and obtain different results ( the # numbers is what was printed out)
Make sure to follow the Contributer Guide closely, particularly for containers. |
…02/ivy into num_ivy_arrays_on_dev
Hi Simone,
And here below was your code
About the result, I think somewhere was wrong, could you recheck on that? 🙇 ` |
Hi David, The original example was failing the tests too. My code was run on a python script importing the master branch of ivy so it's not wrong. Most likely, there have been changes to the function since the original example was written. You can also run my code by making a new file in your local clone of ivy and running it on the command line/terminal. |
Hi Simone, |
Hi David, It would be best if you could run the code yourself and use this to write the docstring examples. Are you using PyCharm or VSCode to view and edit the ivy source code? |
HI Simone, |
Hi Simone,
|
Hi David,
As I mentioned before, you can create a new .py script under the /ivy directory in PyCharm and Kind Regards, Simone |
…02/ivy into num_ivy_arrays_on_dev
Hi Simone,
The result should be 2, not 3 |
Hi Simone, |
Hi David, There is the warning: Please double check all the outputs to the functions is correct. Also, the format is important. The { } brackets in the last few examples may be causing this warning. Kind Regards, Simone |
Hi Simeone, |
Hello @simonetgordon , |
Hi David, Sorry, I don't follow what you mean. The user warning shouldn't be there. If there is, there is an issue with the docstring example not matching the output of the function when it's run. Could you please try removing the { } brackets in the code and see if that gets the test passing without a warning? |
Hi Simone, |
Hi David, That's great! Ready to merge 😊 Thanks again for the contribution. Simone |
No description provided.