Skip to content
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

[MRG] ENH Return int/float instead of np.int/np.float in classification_report #11657

Closed
wants to merge 1 commit into from
Closed

[MRG] ENH Return int/float instead of np.int/np.float in classification_report #11657

wants to merge 1 commit into from

Conversation

qinhanmin2014
Copy link
Member

See #11160 (comment)
We've decided to return int/float instead of np.int/np.float in classification_report
cc @jnothman

@qinhanmin2014 qinhanmin2014 changed the title ENH Return int/float instead of np.int/np.float in classification_report [MRG] ENH Return int/float instead of np.int/np.float in classification_report Jul 23, 2018
Copy link
Member

@jnothman jnothman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM

@@ -1549,9 +1549,11 @@ class 2 1.00 0.67 0.80 3
report_dict = {label[0]: label[1:] for label in rows}

for label, scores in report_dict.items():
report_dict[label] = dict(zip(headers, scores))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scores.tolist() would have sufficed here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jnothman
scores is a tuple and avg_total is a list, so seems that we can't use tolist() here?

@jnothman
Copy link
Member

jnothman commented Jul 23, 2018 via email

@qinhanmin2014
Copy link
Member Author

Closed in #11679

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants