GH-43352: [Docs][Python] Add all tensor classes documentation

[ShaiviAgarwal2]

Rationale for this change

We have added the missing documentation for various tensor classes in PyArrow, specifically SparseCOOTensor, SparseCSRMatrix, SparseCSCMatrix, and SparseCSFTensor. This documentation is necessary to provide users with reference information and examples on how to use these classes, as currently, there is no reference documentation or information in the PyArrow user guide regarding these tensor classes.

What changes are included in this PR?

1. Added docstrings to the SparseCSRMatrix, SparseCSCMatrix, and SparseCSFTensor classes and their methods in the tensor.pxi file.
2. Updated the tables.rst file to include documentation for SparseCSFTensor along with examples.

Are these changes tested?

No new tests are included in this PR as the changes are purely documentation updates. The existing tests for the tensor classes should cover the functionality.

Are there any user-facing changes?

Yes, the user-facing change is the addition of documentation for the tensor classes, which will help users understand and utilize these classes more effectively. There are no breaking changes to public APIs.

• GitHub Issue: [Docs][Python] Add all tensor classes documentation #43352

[github-actions]

⚠️ GitHub issue #43352 has been automatically assigned in GitHub to PR creator.

[ShaiviAgarwal2]

@kou @AlenkaF Could you please review the recent updates?

[kou]

@github-actions crossbow submit preview-docs

[github-actions]

Revision: 59e8197

Submitted crossbow builds: ursacomputing/crossbow @ actions-8a25ed4ca3

Task	Status
preview-docs

[AlenkaF]

There are some style corrections needed - I think @kou added all but they are marked as resolved - maybe we are missing a commit?

I also added some comments regarding the code blocks and docstrings.

[ShaiviAgarwal2]

There are some style corrections needed - I think @kou added all but they are marked as resolved - maybe we are missing a commit?

I also added some comments regarding the code blocks and docstrings.

@AlenkaF Yes I marked as resolved but didn't submit the new commit as working on some checks that are failing
Will do the needful soon!!

[ShaiviAgarwal2]

@kou Could you please help me to resolve the conflicts caused!!

[kou]

Hmm. What git commands did you use...? There are needless changes...

It may be better that you create a new branch and open a new PR from it.

[ShaiviAgarwal2]

Hmm. What git commands did you use...? There are needless changes...

It may be better that you create a new branch and open a new PR from it.

I use these commands inorder to resolve the conflicts but they didn't work !!

git checkout master
git pull
git checkout
git merge master
[ ... resolve any conflicts ... ]
git add [files that were conflicted]
git commit
git push

[ShaiviAgarwal2]

Hmm. What git commands did you use...? There are needless changes...

It may be better that you create a new branch and open a new PR from it.

Ok will now create a new branch and submit a new pr from it!

[kou]

git checkout master

Is this correct? It seems that your fork doesn't have master: https://github.com/ShaiviAgarwal2/arrow/branches/all?query=master&lastTab=overview
Did you use main instead?

[ShaiviAgarwal2]

git checkout master

Is this correct? It seems that your fork doesn't have master: https://github.com/ShaiviAgarwal2/arrow/branches/all?query=master&lastTab=overview Did you use main instead?

Yes i used main
Ohh so in-place of git checkout master, I have to use git checkout main ?

[kou]

Yes. If master doesn't exit, git checkout master must be failed.

BTW, it seems that your main https://github.com/ShaiviAgarwal2/arrow is too old:

This branch is 1902 commits behind apache/arrow:main.

[AlenkaF]

@ShaiviAgarwal2 if it would be easier you can also start fresh and create a new PR from latest main in favour of this one?

[ShaiviAgarwal2]

@ShaiviAgarwal2 if it would be easier you can also start fresh and create a new PR from latest main in favour of this one?

Okk