-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Added documentation entry for NumPy ndarray trace() method #7830
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
Conversation
|
Hey @Nischay-loq, please sign the CLA |
Clarified explanation of the .trace() method for NumPy arrays, including details on handling multi-dimensional arrays and optional parameters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for a second review! 🚀 But waiting for CLA
Hey @Nischay-loq, please sign the CLA
Updated the syntax for the numpy trace function to reflect the correct usage with ndarray.
|
Hey @mamtawardhani, I have signed the CLA |
|
@mamtawardhani I request that, if possible, do follow my GitHub account. |
dakshdeepHERE
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
|
👋 @Nischay-loq 🎉 Your contribution(s) can be seen here: https://www.codecademy.com/resources/docs/numpy/ndarray/trace Please note it may take a little while for changes to become visible. |
Issue solved #7828
Type of Change
Adding a new entry
Editing an existing entry (fixing a typo, bug, issues, etc)
Updating the documentation
Checklist
All writings are my own.
My entry follows the Codecademy Docs style guide.
My changes generate no new warnings.
I have performed a self-review of my own writing and code.
I have checked my entry and corrected any misspellings.
I have made corresponding changes to the documentation if needed.
I have confirmed my changes are not being pushed from my forked main branch.
I have confirmed that I'm pushing from a new branch named after the changes I'm making.
I have linked any issues that are relevant to this PR in the Issues Solved section.