papajohn
commented
1 week ago I don't think this behavior was intentional.
On Mon, Oct 28, 2024 at 5:54 PM Edwin Vargas Navarro < @.***> wrote:
Current course staff from Data 8 here,
We were wondering if returning "numpy.str_" was an intentional feature for type(tbl.row(...).item(...)). I bring this up since type(tbl.column(...).item(...)) returns a str. This means that in our test cases for jupyter notebooks, we should consider both of these types, but it would be beneficial to have both return a str for consistency and student readability. Screenshot.2024-10-28.at.5.42.37.PM.png (view on web) https://github.com/user-attachments/assets/4c0218fb-0d06-4471-b8f4-8ac42ee25be3
— Reply to this email directly, view it on GitHub https://github.com/data-8/datascience/issues/618, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACOFEKOZC25HGVJ4FFCILLZ53MF3AVCNFSM6AAAAABQYUFJROVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYTSOBWGU4TKNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Current course staff from Data 8 here,
We were wondering if returning "numpy.str_" was an intentional feature for type(tbl.row(...).item(...)). I bring this up since type(tbl.column(...).item(...)) returns a str. This means that in our test cases for jupyter notebooks, we should consider both of these types, but it would be beneficial to have both return a str for consistency and student readability.